On 15 April 2016 at 21:08, Gary Gregory <garydgreg...@gmail.com> wrote: > On Fri, Apr 15, 2016 at 12:52 PM, James Carman <ja...@carmanconsulting.com> > wrote: > >> On Fri, Apr 15, 2016 at 1:43 PM sebb <seb...@gmail.com> wrote: >> >> > >> > "the regular process" is what is under discussion. >> > >> > >> I meant the regular process used by the maven release plugin. :) That's >> "regular" to me, because that's what I use all the time. I think we have >> an opportunity to streamline what we do here quite a bit. One of the main >> issues we have here is the assertion that tags must be immutable. We have >> two options that I can see, then (since folks are opposed to "burning" >> version numbers): >> >> 1. Make them mutable. Then we can delete the tags when a release VOTE >> fails and go at it again.
As already explained, this is not possible with Git. Infra have disabled updating of certain tags includig the ones used for releases. We should have the same rules for SVN and Git components. >> 2. Let the maven release plugin create tags called "rc/foo-1.2.3-rc1" or >> whatever while it's staging a release to Nexus for us. Then, when the >> release VOTE passes, we release the staging repository and copy the "rc" >> tag to "releases/foo-1.2.3" and call it a day. OK by me. > > I always copy the RC tag to a release tag when I RM. But what does your POM contain? > Gary > > >> Thoughts? >> > > > > -- > E-Mail: garydgreg...@gmail.com | ggreg...@apache.org > Java Persistence with Hibernate, Second Edition > <http://www.manning.com/bauer3/> > JUnit in Action, Second Edition <http://www.manning.com/tahchiev/> > Spring Batch in Action <http://www.manning.com/templier/> > Blog: http://garygregory.wordpress.com > Home: http://garygregory.com/ > Tweet! http://twitter.com/GaryGregory --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
