[
https://issues.apache.org/jira/browse/ZOOKEEPER-224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12650636#action_12650636
]
Doug Cutting commented on ZOOKEEPER-224:
----------------------------------------
Shouldn't the pom & metadata files be either included in svn or generated by
the build? We shouldn't be publishing artifacts without a documented process
in place so that any committer can build the next release. So the creation of
this needs to be part of http://wiki.apache.org/hadoop/ZooKeeper/HowToRelease.
We shouldn't generate new release artifacts after the release vote. Maybe, if
the process is documented, and Pat's willing to create & publish these
artifacts after the fact, an exception can be made for a few past releases, but
going forward, this is not a good process.
> Deploy ZooKeeper 3.0.0 to a Maven Repository
> --------------------------------------------
>
> Key: ZOOKEEPER-224
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-224
> Project: Zookeeper
> Issue Type: Task
> Components: build
> Affects Versions: 3.0.0
> Reporter: Hiram Chirino
> Assignee: Patrick Hunt
> Priority: Critical
>
> I've created the maven poms needed for the 3.0.0 release.
> The directory structure and artifacts located at:
> http://people.apache.org/~chirino/zk-repo/
> aka
> people.apache.org:/x1/users/chirino/public_html/zk-repo
> Just need sto get GPG signed by the project KEY and deployed to:
> people.apache.org:/www/people.apache.org/repo/m2-ibiblio-rsync-repository
> Who's the current ZooKeeper release manager?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.