On Wed, Feb 20, 2008 at 10:03 PM, James Carman <[EMAIL PROTECTED]> wrote: > On 2/20/08, Oliver Heger <[EMAIL PROTECTED]> wrote: > > > > > > > You are right, the release instructions seem to be outdated in this area. > > > > It has become common practice to cut release candidates, tag them as > > such in subversion, but set the version numbers to the actual release > > version. (Typically you set the version, e.g. 1.0, in the pom, create > > the distributions and the subversion tag for the rc, and then roll-back > > the version number to the snapshot version, for the case that the vote > > fails.) > > > > So these artifacts look exactly like release artifacts. (To avoid > > confusion, they are not announced in the public, but only on the dev > list.) > > > > Then if the vote passes, these artifacts can directly be deployed to the > > maven repo, and the tag for the rc can be copied to the release tag. > > Otherwise a new iteration is necessary. > > > > So, should we create a JIRA somewhere or somehow capture the fact that > the release directions need to be edited by someone? I would also > recommend we put in there all of the nice mvn commands to get this > working (mvn -Prc site assembly:assembly, for instance).
Yup, sorry about this - we changed process just over a year - I think following this thread: http://commons.markmail.org/message/vw3ckyjakjgbdlbu ...but no-one has go round to updating the docs. The other part of the equation is maven2 - its only recently we started using m2 as the primary build on some components - before that it was pretty much all m1. The few recent m2 component releases have all be manual (rather than using the m2 release plugin - I think JCI used that) - so I'm not sure if we have a set procedure - but should document both options. Niall > > > > Oliver > > > > > > > > > >> Oliver > > >> > > >> > > >> > > > >> > On Feb 19, 2008 11:31 PM, James Carman <[EMAIL PROTECTED]> wrote: > > >> >> All, > > >> >> > > >> >> I have prepared a commons-proxy-1.0-rc2 release candidate. The > > >> >> distribution files can be found at: > > >> >> > > >> >> http://people.apache.org/~jcarman/commons-proxy-1.0-rc2/ > > >> >> > > >> >> and the site can be found at: > > >> >> > > >> >> http://people.apache.org/~jcarman/commons-proxy-1.0-rc2/site > > >> >> > > >> >> The SVN tag used to create the release can be found at: > > >> >> > > >> >> > http://svn.apache.org/repos/asf/commons/proper/proxy/tags/proxy-1.0-rc2 > > >> >> > > >> >> All issues brought up thus far with the first release candidate > have > > >> >> been addressed. Again, this is my first release (including > signing), > > >> >> so please review thoroughly (not that you normally don't). > > >> >> > > >> >> Thank you, > > >> >> > > >> >> James Carman --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
