From: Akinori MUSHA <knu@...>
Date: 2009-02-11T02:07:03+09:00
Subject: [ruby-core:21956] Re: New hash : syntax for the 1.8 series?

--pgp-sign-Multipart_Wed_Feb_11_02:08:14_2009-1
Content-Type: text/plain; charset=US-ASCII

At Tue, 10 Feb 2009 22:26:50 +0900,
Kornelius Kalnbach wrote:
> on the topic: colon hash notation is a great thing, backporting it in
> 1.8.8 seems to be logical considering the complete change of meaning of
> the teeny version since 1.8.7. approaching complete syntactic

I may have redefined the meaning of teeny, but I think that the
major.minor.teeny labels are confusing in the first place.  It sounds
weird that 1.9 is incompatible with 1.8 when they have the same
"major" version number.  I would rather label them epoch.major.minor.

Putting it aside, sharing a major version number generally means
backward compatibility, and it certainly is the case for the 1.8
series.  There is no discrepancy/violation here even if the second
number were labeled "major" as I said above.

> compatibility with 1.9 would be nice. but, with most of the new core
> methods already backported, 1.8.8 starts to feel like another 1.9.1 to
> me - just without YARV, Oniguruma, and memory diet.

M17N is another main feature that will never get backported.  1.8 only
provides awkward ways to handle multiple string encodings.

> by the way, you mention the "plan for Ruby 1.8.8" - can it be seen anywhere?

I'm sorry but no at the moment.  Individual tasks will be added to
Redmine as they come up:

	http://redmine.ruby-lang.org/projects/ruby-18/issues

Of course anyone can add a feature request via the tracker.

While backport as well as fixing bugs and misfeatures goes on, I
always consider the backward compatibility very important.  So, there
is no question that the branch policy remains in effect:

	http://redmine.ruby-lang.org/wiki/ruby-18/BranchPolicy


I know there was unfortunate method name clash with ActiveSupport in
1.8.7, and I had learned from that.  I wasn't using Rails or popular
gems so much at the time, but now I do, so you can expect that I will
coordinate with the developers of those major products through the
release engineering process.

Regards,

--
Akinori MUSHA / http://akinori.org/

--pgp-sign-Multipart_Wed_Feb_11_02:08:14_2009-1
Content-Type: application/pgp-signature
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (FreeBSD)

iEYEABECAAYFAkmRtH8ACgkQkgvvx5/Z4e5PQQCg3qAy8N9LTWw74izXd3b1A2GL
OxcAoIhMLvj9iXtNY/pppB6htFnu+LMy
=b0ZY
-----END PGP SIGNATURE-----

--pgp-sign-Multipart_Wed_Feb_11_02:08:14_2009-1--