On Mar 17, 2009, at 11:28 AM, David Jencks wrote:
On Mar 17, 2009, at 10:39 AM, David Sean Taylor wrote:
On Mar 17, 2009, at 9:59 AM, Carsten Ziegeler wrote:
I'm -1 as well and agree with David J.
The proper release process (even for a pom) is to first cut the
candidate on which is voted. Instead of first voting and then
cutting
the candidate.
May I suggest that we work as a community here... what I mean is
instead of statements like "the proper release process is...."
without pointing anyone at the process, could we simply try to help
Vivek? This is the first release he is trying to cut. Perhaps
sending some links to release procedure documentation for creating
a "proper release" would be more constructive, or even volunteering
to help.
Both Carsten and DJ are experienced, respected and knowledgeable
Apache members. I believe its your role to help the less
experienced of us out with the "Apache way"
Could someone point us at a document where these procedures are
written out?
DJ suggested using a Nexus repository. DJ, could you help Vivek and
I with the pom and the nexus staging procedures?
OK, although asking on maven irc will get you advice from people who
have actually used it :-) There's nexus staging info here: http://www.sonatype.com/books/nexus-book/reference/staging.html
I think it would be a good idea to also include a release profile
that makes sure the source, javadoc, gpg and ianal plugins are run
(the last checks all artifacts for apache required legal files).
Should I just edit the poms or supply suggestions or patches?
Yes, please do. It would be great to see an example... thanks!
Are you trying to get this out before apachecon eu?
its in one of those as soon as possible states. but yes, it would be
good to have it in so we can base other releases off of it
