Hi,

How about reconsidering the feature freeze plan.

Yugui (Yuki Sonoda) wrote:
> As announced before, Ruby 1.9.1 features will be frozen on 25 September.
> 
> After the time,
>  * Ruby level APIs must not changed.
>  * C level APIs will must not changed without discussion on
> ruby-core/ruby-dev.
>    * All structures, data types, variables, functions and macros in
> include/ruby/*.h are regarded as public C level APIs.
>    * Move it from include/ruby/*.h anything you want not to publish.
> 
> And I will create the ruby_1_9_1 branch and release 1.9.1 RC1 on 25
> October. After the time,
>  * C level APIs will must not changed.
> 
> Also the C level APIs of 1.9.x must have backward binary-compatibility
> to 1.9.1.

When this plan is decided in July, it was based on the assumption that
most feature of Ruby 1.9 was already fixed and we could spend time to
make ruby stable.

However, Ruby is still changing now and near future.
This is because
* Ruby 1.9 haven't used in large applications yet.
* too radical changes of some libraries
We need more review to Ruby core and libraries.
This gap is enough to break the assumption.

So how about reconsidering the feature freeze plan.
But continual release is important for feedbacks.

My new plan is,
* Ruby 1.9.1 will be released in 2008-12-25.
* Ruby 1.9.1 doesn't assure ABI Compatibility to future Ruby 1.9 series.
* Ruby 1.9.2 may break compatibility to 1.9.1
  if the change is allowed by people and matz and yugui.

-- 
NARUSE, Yui  <naruse / airemix.jp>