On Sun, Aug 24, 2014 at 12:22:42PM +0000, Everett Toews wrote: > You’ve completely lost me at this point. You’ve even introduced new jargon. > What’s a micro release? > > And I have no idea what "major" means to you. To the majority of people in > the software industry a major release means incrementing the first number in > the version. It seems you’ve overloaded the term major as its already > commonly used in semver. But semver aside, what does “major” mean to you in > this context? > > Can you please provide an example of the version numbers for the next 6 > months?
Please familiarize yourself with existing jclouds versioning scheme, which I will summarize. We have released jclouds major versions branched from master as 1.6, 1.7, and 1.8. We have also released jclouds minor versions from release branches as 1.7.1, 1.7.2, and 1.7.3. Major versions introduce breaking changes while minor versions do not. We have not incremented the leading version number in almost four years[1][2] but despite this we refer to 1.7 as a major release and 1.7.1 as a minor release. Whatever you believe about the "majority of software engineers" does not apply to our practices and no one has expressed confusion on this matter, other than that which you have introduced in this thread. To plan future releases, look back at the existing releases. I have summarized all the ASF releases with a few pre-ASF releases for context. Consider both the major and minor releases, including cadence: 1.6.0/ 27-Apr-2013 1.6.1-incubating/ 20-Jun-2013 7 weeks 1.6.2-incubating/ 27-Aug-2013 9 weeks 1.6.3/ 30-Nov-2013 12 weeks 1.7.0/ 23-Dec-2013 4 weeks 1.7.1/ 11-Feb-2014 7 weeks 1.7.2/ 15-Apr-2014 8 weeks 1.7.3/ 30-May-2014 6 weeks 1.8.0/ 05-Aug-2014 9 weeks Also consider only the major releases, including cadence: 1.5.0/ 17-Sep-2012 1.6.0/ 27-Apr-2013 7 months 1.7.0/ 23-Dec-2013 6 months 1.8.0/ 05-Aug-2014 8 months Following the existing 6 weeks minor release cadence and including the 6 month major release cadence we agreed to earlier in this thread, we can plan the following major and minor releases: 1.8.1/ 15-Sep-2014 6 weeks 1.8.2/ 01-Nov-2014 6 weeks 1.8.3/ 15-Dec-2014 6 weeks 2.0.0/ 01-Feb-2014 6 weeks Note that we only deviated in increasing the leading version number in 2.0 to address your suggestion for the new Java 7 dependency. Had we not followed this suggestion, we would have released jclouds 1.9 instead, avoiding your confusion about "major" version numbers entirely. [1] http://repo1.maven.org/maven2/org/jclouds/jclouds-project/ [2] http://repo1.maven.org/maven2/org/apache/jclouds/jclouds-project/ -- Andrew Gaul http://gaul.org/
