Let's step back here. Do you want to release an Alpha or Beta? As opposed to a telling people to try out what is in the HEAD of trunk?
If you do release 2.0, the implications are strict as to what API changes are allowed WRT binary compatibility. If so you can do that if the JCS community agrees. Instead of releasing 2.0, you would release a version 2.0-Beta1, for which you'd have a first tag of 2.0-Beta1-RC1 to VOTE on. Gary On Mon, Nov 17, 2014 at 12:09 PM, Romain Manni-Bucau <rmannibu...@gmail.com> wrote: > basically that's not what we (I maybe?) wanted to do. this was really > a RC (I even wanted to call it beta). So version is correct from this > point of view. I sadly didn't notice it was "conflicting" with commons > habits. > > > Romain Manni-Bucau > @rmannibucau > http://www.tomitribe.com > http://rmannibucau.wordpress.com > https://github.com/rmannibucau > > > 2014-11-17 18:05 GMT+01:00 Gary Gregory <garydgreg...@gmail.com>: > > No, the release candidate tag and project version should not match > exactly. > > The tag is a release candidate. What we are voting to produce is version > > 2.0, so whatever the tag points to should build version 2.0, not 2.0-RC1, > > not a snapshot, just 2.0. We can have any number of tags 2.0-RC1, 2, 3 > and > > so on, but they all should attempt to build 2.0. The next tag will be > > 2.0-RC2. > > > > The links I provided show the steps more or less clearly. Yes, I know our > > release process is complicated but that's all we've got... :-( You do get > > the hang of it after a while, but I still make mistakes all the time if > > that makes you feel better! ;-) > > > > Gary > > > > On Mon, Nov 17, 2014 at 11:49 AM, Romain Manni-Bucau < > rmannibu...@gmail.com> > > wrote: > > > >> @Gary: wdym? rc version is RC1 so it matches project version finally. > >> > >> > >> Romain Manni-Bucau > >> @rmannibucau > >> http://www.tomitribe.com > >> http://rmannibucau.wordpress.com > >> https://github.com/rmannibucau > >> > >> > >> 2014-11-17 17:38 GMT+01:00 Gary Gregory <garydgreg...@gmail.com>: > >> > -1 > >> > > >> > The files at the tag are incorrect, least the POM is wrong: > >> > > >> > > >> > https://svn.apache.org/repos/asf/commons/proper/jcs/tags/commons-jcs-2.0-RC1/pom.xml > >> > > >> > because the project version is 2.0-RC1 instead of 2.0. > >> > > >> > I've not found one cannonical receipt for releasing out of commons > >> sadly, I > >> > use both > >> > - https://wiki.apache.org/commons/UsingNexus and > >> > - https://commons.apache.org/releases/index.html > >> > > >> > Gary > >> > > >> > On Wed, Nov 12, 2014 at 4:23 AM, Romain Manni-Bucau < > >> rmannibu...@gmail.com> > >> > wrote: > >> > > >> >> Hi > >> >> > >> >> I'm trying to align on commons standards this time. > >> >> > >> >> - here is the maven repo: > >> >> > >> > https://repository.apache.org/content/repositories/orgapachecommons-1061/ > >> >> - assemblies can be found here > >> >> > >> >> > >> > https://repository.apache.org/content/repositories/orgapachecommons-1061/org/apache/commons/commons-jcs-dist/2.0-RC1/ > >> >> (I didn't copy them in another place since I guess it is ok to use > >> >> nexus for it) > >> >> - tag is here: > >> >> > svn.apache.org/repos/asf/commons/proper/jcs/tags/commons-jcs-2.0-RC1/ > >> >> - Site staging is: > >> >> http://people.apache.org/~rmannibucau/commons-jcs-2.0-RC1/ > >> >> - rat report is: > >> >> > >> > http://people.apache.org/~rmannibucau/commons-jcs-2.0-RC1/rat-report.html > >> >> - KEYS: https://www.apache.org/dist/commons/KEYS > >> >> > >> >> > >> >> Please review the release candidate and vote. > >> >> This vote will close no sooner that 72 hours from now or until we get > >> >> 3 PMC votes. > >> >> > >> >> [ ] +1 Release these artifacts > >> >> [ ] +-0 OK, but... > >> >> [ ] -1 I oppose this release because... > >> >> > >> >> Thanks guys and sorry for all my learning steps, > >> >> Romain Manni-Bucau > >> >> @rmannibucau > >> >> http://www.tomitribe.com > >> >> http://rmannibucau.wordpress.com > >> >> https://github.com/rmannibucau > >> >> > >> >> --------------------------------------------------------------------- > >> >> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > >> >> For additional commands, e-mail: dev-h...@commons.apache.org > >> >> > >> >> > >> > > >> > > >> > -- > >> > 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 > >> > >> > > > > > > -- > > 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 > > -- 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
