On 3/22/08, Phil Steitz <[EMAIL PROTECTED]> wrote: > On Sat, Mar 22, 2008 at 6:16 PM, Wendy Smoak <[EMAIL PROTECTED]> wrote: > > On Sat, Mar 22, 2008 at 3:10 PM, Phil Steitz <[EMAIL PROTECTED]> wrote: > > > > > 3) Announce availability of RC, publish RC-labeled jar to snapshot > > > repo and tarballs to ~psteitz > > > > In order for (5) to be automated with the stage plugin, you would need > > to stage each release in a separate repository. I think that's > > already taken care of with the proposed changes to the parent pom > > using space under people.a.o/builds/. > > > > (Non-snapshot artifacts shouldn't go in the snapshot repository, > > though I'm probably responsible for starting that practice over at > > Struts a long time ago.) > > > > I don't see why it should be "illegal" to publish an RC to the > snapshot repo. We do not distinguish "stable", "ga", "beta" etc here > in Commons. We have releases and things that are not yet released. I > don't see why we need yet another repo for RCs. We - at least I - > like for people to test with our RCs *before* we vote on them. So > maybe its just semantics and I am calling the RCs (with "RC" in the > artifact name) "snapshots." I don't see the need to ask people to > configure yet another special repo to test our RCs. > <snip/>
For the style of RCs you've described, there is nothing against putting them in the m2-snap-repo. But the final RC that you describe is best not placed there, because: * Fundamentally, its a (soon-to-be) release, not a snap * Wendy is alluding to a limitation of the stage plugin that requires the staging repo to be clean (it will currently copy all versions that exist in the staging repo over to the rsync repo! -- obviously that means you don't want the m2-snap-repo to also be the staging repo ATM). And for folks like me who won't be correcting metadata files by hand (tedious, open to operator error), the stage plugin is needed. IMO, its not a bad idea to get folks to use an alternate repo for testing RCs, it causes an increased level of awareness :-) -Rahul --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
