On 10 June 2011 06:47, Magnus Holm <judo...@gmail.com> wrote:
> application/library/something and be sure that it will work on any
> JRuby 1.6.x. It means that JRuby can push out security and bug fixes
> to the 1.6-branch even after 1.7 is released.
None of what you described changes with date based major releases.
You can still do maintenance branches and maintenance releases (e.g.
11.08.1, 11.08.2).
The problem that needs to be avoided, is that people attribute too
much significance to the numbers in a version (i.e. 2.0 == big
change), when in reality with JRuby, releases are kind-of time based,
is a distilling of whatever people were working on during that time
period, and the version number chosen is simply the next one in a
sequence.
That semantic versioning proposal on the other hand, is not just a
versioning scheme, but also a development methodology (somewhat
resembling waterfall). Whilst that is suited to some forms of
projects - i.e. libraries where you have a big design/stablization
period pre-1.0.0, then change is very limited thereafter (or it makes
it painful to do), it does not fit the reality of how JRuby is
currently developed.
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
