Ruby 1.8.6 pl399 has been released. This release fixes a problem that
was encountered yesterday with builds on some platforms. The only
difference between pl399 and pl398 is that pl399 required a minor
syntax change in one macro, and purged some dead code left behind by
earlier changes.
Ruby 1.8.6 pl399 has been released. This release fixes a problem that
was encountered yesterday with builds on some platforms. The only
difference between pl399 and pl398 is that pl399 required a minor
syntax change in one macro, and purged some dead code left behind by
earlier changes.
Forgive my ignorance, but why would one want to use this instead of
1.8.7? Is 1.8.7 closer to the bleeding edge than I believed it was, or
is the 1.8.6 line maintained purely for existing applications that
really really don't need *any* API changes?
I'm sure there's a perfectly sensible reason for apparently having three
MRI versions (1,8.6, 1.8.7, 1.9.x) on the go at once, but I don't know
what that reason is or where the boundaries are.
Ruby 1.8.6 pl399 has been released. This release fixes a problem that
was encountered yesterday with builds on some platforms. The only
difference between pl399 and pl398 is that pl399 required a minor
syntax change in one macro, and purged some dead code left behind by
earlier changes.
Any chance you could email James Gray with the news so he can post a
blog about the update to Ruby Programming Language
?
Thanks.
-r
Many people have production applications running on 1.8.6 and upgrades would
happen at a cost that the company might not want to foot just yet.
Kirk maintains the 1.8.6 branch for such people back porting security
patches, bug fixes and enhancements from 1.8.7 so that such people can still
get the benefits & stability.
The upgrade path for some companies is excruciatingly slow
IMHO if you are new to ruby you should be using 1.9.X and don't look back.
Dan, Wayne basically covered it. It's support. Where one has an
option, one should at _least_ be using Ruby 1.8.7, and should probably
be evaluating 1.9.1 as well as other implementations such a Rubinius
or JRuby. But a lot of people are still on 1.8.6, maybe because they
are comfortable with it. Maybe because that's what their app uses and
changing it isn't as easy for them as just swapping, or maybe for
other reasons.
So, for the foreseeable future I'll continue backporting important
changes and bug fixes into 1.8.6, probably at a more aggressive pace
than in prior months, until I run out of issues to fix.
Kirk Haines
···
On Fri, Feb 5, 2010 at 10:15 AM, <dan@telent.net> wrote:
Kirk Haines <wyhaines@gmail.com
Forgive my ignorance, but why would one want to use this instead of
1.8.7? Is 1.8.7 closer to the bleeding edge than I believed it was, or
is the 1.8.6 line maintained purely for existing applications that
really really don't need *any* API changes?
I'm sure there's a perfectly sensible reason for apparently having three
MRI versions (1,8.6, 1.8.7, 1.9.x) on the go at once, but I don't know
what that reason is or where the boundaries are.
