Purpose of Ruby 1.9?

On Dec 27, 2007 11:43 PM, Leonard C. [email protected] wrote:

  • perhaps April?)
  • In order to drive development, make intermediate releases regularly
    with short (one month?) intervals with the version fixed at 1.9.0
    (releases every 29th?)

So I guess this means that version 1.9.0 will change at the end of
each month??? until 1.9.1 is released maybe in April.

If this is the case, I’m not sure just what changed when 1.9.0 was
released on the 25th.

I’m a bit confused.


Rick DeNatale

My blog on Ruby
http://talklikeaduck.denhaven2.com/

Leonard C. wrote:

  • In order to drive development, make intermediate releases regularly
    with short (one month?) intervals with the version fixed at 1.9.0
    (releases every 29th?)

This may produce more confusion than help. There are a lot of things to
test and evaluate in Ruby 1.9.0, which takes time.

We now have a baseline for testing, which can be referenced in problem
reports. If there is a report area (http://rubyforge.org/projects/ruby/
???) everybody can see if a problem is already reported, and we can
follow the state of the report.

To plan a much more stable release Ruby 1.9.1 for April or so makes
sense, but to have monthly new Ruby 1.9.0 - what is principal the
difference to nightly snapshots?

Wolfgang Nádasi-Donner

Hi

On Dec 27, 2007 5:50 AM, Rados³aw Bu³at [email protected] wrote:

My question is generally to Matz, Ko1 or other Ruby core maintainers.
We have Ruby 1.9 already released. Matz says that it’s not stable as
he expected, so it requires some work to become stable. But what
intentions are for Ruby 1.9.x?

Here’s a quick translation of the relevant parts of a mail from matz
to ruby-dev that are kind of relevant to this question.

reference:
http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ruby-dev/32794

=begin translation
For now, we’ll focus on improving 1.9. Bugs are certain to be found,
and there is still lots to do. So, I don’t think there is any need to
create a 1.9 branch for now. Even if we do branch, we’ll have to apply
fixes to both (trunk and branch), which is a doubling of required
effort, so just tagging should be sufficient.

Here’s a possible plan for the next step:

  • Release 1.9.1 sometime during the first half of 2008 (decide later
  • perhaps April?)
  • In order to drive development, make intermediate releases regularly
    with short (one month?) intervals with the version fixed at 1.9.0
    (releases every 29th?)
  • Prepare documentation for migrating from 1.8 to 1.9 in parallel

What do you think?

= end

Disclaimer: this is just a translation of part of a single mail from

matz in a thread of discussion. It is not an announcement.

I posted a suggestion to ruby-core that perhaps the Ruby 1.9 tarball
should be set up so that BY DEFAULT, it installs as ruby1.9 instead of
ruby, so that unwitting installers don’t get their Ruby1.8
installation replaced by default.

Given the colossal numbers of clueless posts by Rails newbs that
happen all over the Web, I think that this is an extreeeeeeeeeeemely
good idea.


Giles B.

Podcast: http://hollywoodgrit.blogspot.com
Blog: http://gilesbowkett.blogspot.com
Portfolio: http://www.gilesgoatboy.org
Tumblelog: http://giles.tumblr.com

On Dec 28, 2007 6:46 PM, Yukihiro M. [email protected] wrote:

|So I guess this means that version 1.9.0 will change at the end of
|each month??? until 1.9.1 is released maybe in April.
|
|If this is the case, I’m not sure just what changed when 1.9.0 was
|released on the 25th.
|
|I’m a bit confused.

They will be bug fix versions. The spec will not be changed. If
changed, they were spec bugs.

But will they all be version 1.9.0? What’s the meaning of version if
there are multiple drops with the same version number?


Rick DeNatale

My blog on Ruby
http://talklikeaduck.denhaven2.com/

Hi,

In message “Re: Purpose of Ruby 1.9?”
on Sat, 29 Dec 2007 12:22:19 +0900, “Rick DeNatale”
[email protected] writes:

|> They will be bug fix versions. The spec will not be changed. If
|> changed, they were spec bugs.
|
|But will they all be version 1.9.0? What’s the meaning of version if
|there are multiple drops with the same version number?

Note that the last version was 1.9.0-0. The forthcoming versions will
be versioned 1.9.0-1, 1.9.0-2, and such.

          matz.

Hi,

In message “Re: Purpose of Ruby 1.9?”
on Fri, 28 Dec 2007 23:57:10 +0900, “Rick DeNatale”
[email protected] writes:

|> - perhaps April?)
|> * In order to drive development, make intermediate releases regularly
|> with short (one month?) intervals with the version fixed at 1.9.0
|> (releases every 29th?)
|
|So I guess this means that version 1.9.0 will change at the end of
|each month??? until 1.9.1 is released maybe in April.
|
|If this is the case, I’m not sure just what changed when 1.9.0 was
|released on the 25th.
|
|I’m a bit confused.

They will be bug fix versions. The spec will not be changed. If
changed, they were spec bugs.

          matz.

This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.

| Privacy Policy | Terms of Service | Remote Ruby Jobs