[ANN] Ruby 1.9.0-3 is released

Hi,

Ruby 1.9.0-3 has just been released. This is a snapshot release.

The next release is 1.9.0-4. It will be released at 25 Oct. See
[ruby-core:17644] for more details.

== Location
You can fetch it from:

ftp://ftp.ruby-lang.org/pub/ruby/1.9/ruby-1.9.0-3.tar.bz2
   MD5 = 033ea37e56c48f098f1bbde1467ac6dc
   SHA256 = d5ca832db445e3251113c4027f2528d17e32ed9508d2dd507c469e546ad180db
   SIZE = 5169699

ftp://ftp.ruby-lang.org/pub/ruby/1.9/ruby-1.9.0-3.tar.gz
   MD5 = f0fc07e2ce1fce07e6e23e0e5a1fc4df
   SHA256 = ebf1e5b045972d73dd9c1aa780e3800b77463f4901ee634dd41fe2d6da654e23
   SIZE = 6225372

ftp://ftp.ruby-lang.org/pub/ruby/1.9/ruby-1.9.0-3.zip
   MD5 = 9bea3a0402105d840ea4bc9aa382b609
   SHA256 = 9ee23ed0f4126ce583113ec8381cc1a7853a05197232af7352d4ebdb3e03b742
   SIZE = 7354642

== Platforms
Ruby 1.9 no longer supports the following platforms because they have no
active maintainer.
* BeOS
* WinCE
* OS/2
* Interix
* bcc32
* Classic MacOS
* djgpp
* VMS
* human68k

I will remove platform-specific codes for them from Ruby, unless someone
become a maintainer by 25 Sep.

Regards,

- --
Yugui <yugui@yugui.jp>
http://yugui.jp

It's a GREAT pity that WinCE won't be supported...
Is there anyone to becoma a maintainer?
(For some reasons I can't :-((

Yugui (Yuki Sonoda) wrote:

···

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

Ruby 1.9.0-3 has just been released. This is a snapshot release.

The next release is 1.9.0-4. It will be released at 25 Oct. See
[ruby-core:17644] for more details.

== Location
You can fetch it from:

ftp://ftp.ruby-lang.org/pub/ruby/1.9/ruby-1.9.0-3.tar.bz2
   MD5 = 033ea37e56c48f098f1bbde1467ac6dc
   SHA256 = d5ca832db445e3251113c4027f2528d17e32ed9508d2dd507c469e546ad180db
   SIZE = 5169699

ftp://ftp.ruby-lang.org/pub/ruby/1.9/ruby-1.9.0-3.tar.gz
   MD5 = f0fc07e2ce1fce07e6e23e0e5a1fc4df
   SHA256 = ebf1e5b045972d73dd9c1aa780e3800b77463f4901ee634dd41fe2d6da654e23
   SIZE = 6225372

ftp://ftp.ruby-lang.org/pub/ruby/1.9/ruby-1.9.0-3.zip
   MD5 = 9bea3a0402105d840ea4bc9aa382b609
   SHA256 = 9ee23ed0f4126ce583113ec8381cc1a7853a05197232af7352d4ebdb3e03b742
   SIZE = 7354642

== Platforms
Ruby 1.9 no longer supports the following platforms because they have no
active maintainer.
* BeOS
* WinCE
* OS/2
* Interix
* bcc32
* Classic MacOS
* djgpp
* VMS
* human68k

I will remove platform-specific codes for them from Ruby, unless someone
become a maintainer by 25 Sep.

Regards,

- --
Yugui <yugui@yugui.jp>
http://yugui.jp
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkiJ6rQACgkQOXzH5JLb/AUEdQCeNx1oS3WOmhR78PCqbo87dqla
UnEAmwTyIDZPS4TZbgYpRzm0PsavMz1a
=952x
-----END PGP SIGNATURE-----

In article <4889EAB4.9030302@yugui.jp>,

Ruby 1.9.0-3 has just been released. This is a snapshot release.

The next release is 1.9.0-4. It will be released at 25 Oct. See
[ruby-core:17644] for more details.
[....]
== Platforms
Ruby 1.9 no longer supports the following platforms because they have no
active maintainer.
* BeOS
* [.....]

I will remove platform-specific codes for them from Ruby, unless someone
become a maintainer by 25 Sep.

Well, Ruby is definitely not dead on BeOS (nor is BeOS itself...!)
I have v1.8.4 fully functional on my BeOS system, and use it extensively.
(Also available on BeBits -- the software distribution site for the OS.)

I never pursued any later version, because 1.8.4 matches the Pickaxe book,
and that was my main desire -- to have corresponding software and docs.

However, it would be a shame to have BeOS support disappear from the
next version, so I guess I should volunteer myself as a maintainer!
(The BeOS hooks in 1.8.4 BTW were not quite sufficient. I had to further
modify a few of the sources -- unfortunately long enough ago that I don't
remember all the twists and turns. I will proceed to dig back...)

[For those unfamiliar with BeOS -- or its current status -- I should note
that it is currently being redeveloped (and renamed) as the open-source OS
'Haiku'.]

          -- Pete Goodeve --

···

Yugui (Yuki Sonoda) <yugui@yugui.jp> wrote:

--
The above email is a spam bin. If you want to contact directly, use
pete
<at>
goodeveca
<full-stop>
net

Yugui (Yuki Sonoda) wrote:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

Ruby 1.9.0-3 has just been released. This is a snapshot release.

The next release is 1.9.0-4. It will be released at 25 Oct. See
[ruby-core:17644] for more details.

== Location
You can fetch it from:

ftp://ftp.ruby-lang.org/pub/ruby/1.9/ruby-1.9.0-3.tar.bz2
   MD5 = 033ea37e56c48f098f1bbde1467ac6dc
   SHA256 = d5ca832db445e3251113c4027f2528d17e32ed9508d2dd507c469e546ad180db
   SIZE = 5169699

ftp://ftp.ruby-lang.org/pub/ruby/1.9/ruby-1.9.0-3.tar.gz
   MD5 = f0fc07e2ce1fce07e6e23e0e5a1fc4df
   SHA256 = ebf1e5b045972d73dd9c1aa780e3800b77463f4901ee634dd41fe2d6da654e23
   SIZE = 6225372

ftp://ftp.ruby-lang.org/pub/ruby/1.9/ruby-1.9.0-3.zip
   MD5 = 9bea3a0402105d840ea4bc9aa382b609
   SHA256 = 9ee23ed0f4126ce583113ec8381cc1a7853a05197232af7352d4ebdb3e03b742
   SIZE = 7354642

== Platforms
Ruby 1.9 no longer supports the following platforms because they have no
active maintainer.
* BeOS
* WinCE
* OS/2
* Interix
* bcc32
* Classic MacOS
* djgpp
* VMS
* human68k

I will remove platform-specific codes for them from Ruby, unless someone
become a maintainer by 25 Sep.

Regards,

Yugui

Is there a lot of work required for maintaining? I would hate to see the
bcc32 version go away at a time when it looks like Borland/ CodeGear
seems to finally be getting it together. I'm sorry I've never maintained
anything this big, but would be interested to know a bit more if it's
possible.

Thanks
Mohit.

Mike Shock wrote:

It's a GREAT pity that WinCE won't be supported...
Is there anyone to becoma a maintainer?
(For some reasons I can't :-((

Hi
    wats a main advantage of ruby-1.9 with older versions like
ruby-1.8.6

···

--
Posted via http://www.ruby-forum.com/\.

you should subscribe to and write ruby-core@ just to make sure they get this.

···

On Jul 31, 2008, at 14:14 , Pete wrote:

However, it would be a shame to have BeOS support disappear from the
next version, so I guess I should volunteer myself as a maintainer!