From: Kirk Haines on 5 Feb 2010 10:13 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. It can be found here: ftp://ftp.ruby-lang.org/pub/ruby/ruby-1.8.6-p399.tar.bz2 ftp://ftp.ruby-lang.org/pub/ruby/ruby-1.8.6-p399.tar.gz ftp://ftp.ruby-lang.org/pub/ruby/ruby-1.8.6-p399.tar.zip MD5(ruby-1.8.6-p399.tar.bz2)= f77c307cb72fb8808b0e85af5d05cefc SHA256(ruby-1.8.6-p399.tar.bz2)= 20ca08aeefa21ca2581a9791f8f9ace3addc92bd978cf36f2f95c109085a50a7 SIZE(ruby-1.8.6-p399.tar.bz2)= 3972399 MD5(ruby-1.8.6-p399.tar.gz)= c3d16cdd3c1ee8f3b7d1c399d4884e33 SHA256(ruby-1.8.6-p399.tar.gz)= 04efd2a260116c2f4efdb9f2408da086c33ac81146bb030c50a1378951a581e3 SIZE(ruby-1.8.6-p399.tar.gz)= 4580988 MD5(ruby-1.8.6-p399.zip)= 75c4e8926586475962fcacee1a2fc947 SHA256(ruby-1.8.6-p399.zip)= 6db16f10fdb87fdba73ca0260875a6092b83549ec772b23685dbe6adcc58fd50 SIZE(ruby-1.8.6-p399.zip)= 5627074 As always, if you encounter any unexpected behavior, please contact me. Kirk Haines khaines(a)engineyard.com
From: Wayne E. Seguin on 5 Feb 2010 10:57 [Note: parts of this message were removed to make it a legal post.] Awesome turnaround time Kirk! For anyone using rvm, the latest git head (rvm update --head) now has p399 as default for 1.8.6. It will be default for release 0.1.8. ~Wayne
From: dan on 5 Feb 2010 12:07 Kirk Haines <wyhaines(a)gmail.com> writes: > 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. -dan
From: Wayne E. Seguin on 5 Feb 2010 12:34 [Note: parts of this message were removed to make it a legal post.] Dan, 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. ~Wayne
From: Roger Pack on 19 Feb 2010 14:43 > 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 http://www.ruby-lang.org/en/ ? Thanks. -r -- Posted via http://www.ruby-forum.com/.
|
Next
|
Last
Pages: 1 2 Prev: Problems with RubyGems on a Debian machine Next: JRuby rake not working! |