On Sat, May 23, 2009 at 3:41 PM, Phil Steitz <phil.ste...@gmail.com> wrote: > 1) Release process. I am NOT planning on using the maven release plugin. I > will get working assemblies to create tarballs, make tags, named RC1, 2 (NOT > "mutable" release tags) and push the tarballs and jar artifacts manually to > the mirror/repo locations. For the RCs, I will keep RC* names in the > artifact and jar names. Once an RC passes inspection, I will tag and roll a > "final" RC with RC tag name, but final release-named artifacts and kick off > a release VOTE. If the VOTE passes, I will deploy the voted-on artifacts > and copy the tag. Pls scream now if this is not acceptable. I prefer > this method because I know exactly what is going on at each stage and it > keeps tags and RCs immutable.
At work, we don't use release:perform at all. We use release:prepare, though, since that's what creates the tags, etc. Just a thought. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
