[#46807] [ruby-trunk - Bug #7625][Open] Arrayを継承したオブジェクトのcompactがArrayを返す — "mogya@... (Daisuke Furukawa)" <mogya@...>

19 messages 2012/12/26

[#46822] [ruby-trunk - Feature #7639][Open] More freedom for location of comments — "sawa (Tsuyoshi Sawada)" <sawadatsuyoshi@...>

14 messages 2012/12/30

[ruby-dev:46811] Re: [IMPORTANT] 2.0.0 release plan

From: SASADA Koichi <ko1@...>
Date: 2012-12-27 11:09:19 UTC
List: ruby-dev #46811
(English only)

(I post this message as a substitute of Endo-san, release manager of
Ruby 2.0.0. He is very busy now)

Thank you for your help.
Now, Ruby 2.0.0 (trunk) is "code freeze" status.

We want to emphasize the following two things.

(1) Bug fix only

Only bug fixes are acceptable before RC2 (beginning of Feb).

Do *not* add any new features.
If you need to add new features or spec changes to solve an issue,
please get my (Endo-san's) approval.


(2) Identify showstoppers

> ## Identifying showstoppers: ASAP
>
> I will identify "showstoppers" among 300+ bug tickets.  They will be
> marked by the immediate priority.  A "showstopper" means:
>
>   * a reproducible segfault,
>   * a problem that significantly affects real/existing programs, or
>   * a serious problem that has no workaround.
>
> We will identify bug tickets that are reported after the identifying,
> as needed.

If you find any *critical* issues as showstoppers, please tell us ASAP.


Thank you.


(2012/12/03 1:00), Yusuke Endoh wrote:
> ALL COMMITTERS SHOULD READ THIS MAIL! コミッタはこのメール読んで!
> ALL COMMITTERS SHOULD READ THIS MAIL! コミッタはこのメール読んで!
> ALL COMMITTERS SHOULD READ THIS MAIL! コミッタはこのメール読んで!
> 
> Japanese follows; 日本語は後で
> 
> I tell you the plan for 2.0.0 release.
> Please let me know if you have any idea about the plan, especially,
> if you think that there is a problem in the plan.
> 
> ## Milestones
> 
>   - Identifying showstoppers: ASAP
>   - code freeze: 23 Dec.
>   - 2.0.0-rc1 release: the first week of Jan. (expected)
>   - 2.0.0-rc2 release: the first week of Feb. (expected)
>   - 2.0.0-p0 release: 24 Feb.
> 
> 
> ## Identifying showstoppers: ASAP
> 
> I will identify "showstoppers" among 300+ bug tickets.  They will be
> marked by the immediate priority.  A "showstopper" means:
> 
>   * a reproducible segfault,
>   * a problem that significantly affects real/existing programs, or
>   * a serious problem that has no workaround.
> 
> We will identify bug tickets that are reported after the identifying,
> as needed.
> 
> 
> ## Code freeze: 23 Dec.
> 
> Or, feature implementation deadline.  2.0.0 will NOT include the
> (even accepted) new features that are not implemented by this
> deadline.
> 
> 
> ## 2.0.0-rc1 release: the first week of Jan. (expected)
> 
> After all showstoppers are resolved, we will release 2.0.0-rc1.
> (It may be late depending on the status.)
> 
> I'll determine "platform support level" based on whether rc1 works
> properly on the platform or not.
> After 2.0.0-rc1, we will try to resolve non-showstopper bug tickets
> as many as possible.
> 
> 
> ## 2.0.0-rc2 release: the first week of Feb. (expected)
> 
> After we resolve showstoppers that are reported after rc1, we
> will release 2.0.0-rc2.
> 
> I'd like to create a new branch ruby_2_0 at this time.
> 
> After 2.0.0-rc2, we will try to resolve only showstoppers reported
> after rc2.  In principle, we will NOT resolve non-showstoppers to
> avoid a regression.
> 
> 
> ## 2.0.0-p0 release: 24 Feb.
> 
> PARTY!
> 
> 
> 
> 2.0.0 リリースの予定をお伝えします。
> この予定に関して何か意見があれば (特に問題があると思う場合は) ぜひ
> 教えてください。
> 
> ## イベント
> 
>   - showstopper の同定: なるべく早めに
>   - コードフリーズ: 12/23
>   - 2.0.0-rc1 リリース: 1 月第一週目標
>   - 2.0.0-rc2 リリース: 2 月第一週目標
>   - 2.0.0-p0 リリース: 2/24
> 
> 
> ## showstopper の同定: なるべく早めに
> 
> 300 件あまりあるバグチケットから showstopper を同定します (優先度を
> Immediate にします) 。showstopper とは以下を指します。
> 
>   * 再現性のある SEGV
>   * 実世界の、または既存のプログラムに重大な影響を与える問題
>   * 回避策がない重大な問題
> 
> その後報告されたバグチケットは随時判断します。
> 
> 
> ## コードフリーズ: 12/23
> 
> 新機能実装締め切りです。この締め切りまでに実装されなかった新機能は
> (たとえ accept されているものでも) 2.0.0 に含まれません。
> 
> 
> ## 2.0.0-rc1 リリース: 1 月第一週目標
> 
> すべての showstopper が解消されたら、2.0.0-rc1 を出します。
> (進捗次第で遅れるかもしれません)
> 
> rc1 の動作実績を元に platform support level を決めようと思います。
> 2.0.0-rc1 の後は、showstopper でないバグチケットを出来るだけ解決
> するよう努力します。
> 
> 
> ## 2.0.0-rc2 リリース: 2 月第一週目標
> 
> rc1 の後で報告された showstopper を解決した後で、2.0.0-rc2 を
> リリースします。
> 
> この時に ruby_2_0 のブランチを作りたいと思います。
> 
> 2.0.0-rc2 の後では、rc2 後に報告された showstopper のみ解決します。
> regression を避けるため、原則として、showstopper でない問題の修正は
> 行いません。
> 
> 
> ## 2.0.0-p0 release: 2/24
> 
> パーティー!
> 


-- 
// SASADA Koichi at atdot dot net

In This Thread