Romain, I believe it is a good idea to stick to well-known Maven qualifiers which already exist. *RELEASE* is not in this list and I'd prefer to avoid surprises, if this will be changed later. Also our release cycle is different from Eclipse and Spring (instead of milestones we have betas, but RC has absolutely another meaning for us). Thus I don't see any reasons to reflect their versioning in our product.
Sergi 2015-12-03 18:21 GMT+03:00 Romain Gilles <romain.gil...@gmail.com>: > Hi Igniter, > Just to be a pain ... > I like the Spring (I think derive from Eclipse) version numbering approach. > And it works like a charm with OSGi and maven. > > For the sprint they deliver milestone : 1.6.0.M1, 1.6.0.M2... > MX imply no guaranty of stable model / classes. > > When they enter into release process with release branch they use: > 1.6.0.RC1 ... > RC imply stable model only bug fix > > And finally when the big day comes they use the RELEASE qualifier => > 1.6.0.RELEASE. > > Not sure it help but I just like it and want to let you know. > > Romain > > Le mer. 2 déc. 2015 à 04:37, Alexey Kuznetsov <akuznet...@gridgain.com> a > écrit : > > > Guys, > > > > We are introduced new version naming strategy, but do not added > > corresponding tests to GridProductVersionSelfTest. > > > > I created issue for this: > https://issues.apache.org/jira/browse/IGNITE-2049 > > Please fix before ignite-1.5 goes final. > > > > -- > > Alexey Kuznetsov > > GridGain Systems > > www.gridgain.com > > >
