Em 08-06-2011 21:39, Joseph Athman escreveu:
With JRuby all releases are stable, there's no such thing as an
unstable release (though I suppose you could consider release
candidates as unstable). If you wanted to see unstable/unreleased
code you would just need to follow the head of the codebase on github.
In my experience the head is very stable as well. JRuby currently
uses a three part version e.g. 1.6.2. The 2 is a minor version which
seems to generally include bugfixes or performance regressions. The 6
is the major version which seems to normally include more substantial
changes (for example I'm guessing something like all the InvokeDynamic
work that Charlie is doing would only show up in a major version
release). As for the 1, I'm not sure if that will ever bump up?
Possibly once JRuby enables peace in the middle east? Maybe the core
maintainers have an idea of what would be needed for JRuby to turn 2.
I guess this will happen when MRI Ruby becomes 2...
Joe
On Tue, Jun 7, 2011 at 12:39 AM, Atsushi SAKAI <sak...@jp.fujitsu.com
<mailto:sak...@jp.fujitsu.com>> wrote:
Hello.I am newbies on this mailing list.
I have a question about JRuby versioning method.
Which versioning method is taken on JRuby?
In my understanding, method 2) is current versiong method on JRuby.
1)As you know, Linux and Xen has a versioning like w.x.y.z or x.y.z
and .z means stable version.
So x.y and .z meaning is different in these packages.
In these packages, stable tree and unstable tree maintained
with parallel
2)And for libvirt, versioning method is different.
the versioning is composed of x.y.z. and .z means minor version up
and x.y means major version up.
In this package, code tree is maintained as one tree,
not two or more.
Thanks
Atsushi SAKAI
