On 2/20/08, Niall Pemberton <[EMAIL PROTECTED]> wrote: > 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.
Well, does anyone have explicit m2 instructions for doing these releases (using the profiles in commons-parent, I'd think)? I'm pretty familiar with m2 as far as day-to-day stuff (clean, test, install, etc.), but not for doing releases. > > > 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] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
