Forum: Ruby-core [IMPORTANT] 2.0.0 release plan

ALL COMMITTERS SHOULD READ THIS MAIL! $B%3%_%C%?$O$3$N%a!<%kFI$s$G!*(B
ALL COMMITTERS SHOULD READ THIS MAIL! $B%3%_%C%?$O$3$N%a!<%kFI$s$G!*(B
ALL COMMITTERS SHOULD READ THIS MAIL! $B%3%_%C%?$O$3$N%a!<%kFI$s$G!*(B

Japanese follows; $BF|K\8l$O8e$G(B

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 $B%j%j!<%9$NM=Dj$r$*EA$($7$^$9!#(B
$B$3$NM=Dj$K4X$7$F2?$+0U8+$,$"$l$P(B ($BFC$KLdBj$,$"$k$H;W$&>l9g$O(B) 
$B$<$R(B
$B65$($F$/$@$5$$!#(B

## $B%$%Y%s%H(B

  - showstopper $B$NF1Dj(B: $B$J$k$Y$/Aa$a$K(B
  - $B%3!<%I%U%j!<%:(B: 12/23
  - 2.0.0-rc1 $B%j%j!<%9(B: 1 $B7nBh0l=5L\I8(B
  - 2.0.0-rc2 $B%j%j!<%9(B: 2 $B7nBh0l=5L\I8(B
  - 2.0.0-p0 $B%j%j!<%9(B: 2/24


## showstopper $B$NF1Dj(B: $B$J$k$Y$/Aa$a$K(B

300 $B7o$"$^$j$"$k%P%0%A%1%C%H$+$i(B showstopper $B$rF1Dj$7$^$9(B 
($BM%@hEY$r(B
Immediate $B$K$7$^$9(B) $B!#(Bshowstopper $B$H$O0J2<$r;X$7$^$9!#(B

  * $B:F8=@-$N$"$k(B SEGV
  * $B<B@$3&$N!"$^$?$O4{B8$N%W%m%0%i%`$K=EBg$J1F6A$rM?$($kLdBj(B
  * $B2sHr:v$,$J$$=EBg$JLdBj(B

$B$=$N8eJs9p$5$l$?%P%0%A%1%C%H$O?o;~H=CG$7$^$9!#(B


## $B%3!<%I%U%j!<%:(B: 12/23

$B?75!G=<BAuDy$a@Z$j$G$9!#$3$NDy$a@Z$j$^$G$K<BAu$5$l$J$+$C$??75!G=$O(B
($B$?$H$((B accept $B$5$l$F$$$k$b$N$G$b(B) 2.0.0 $B$K4^$^$l$^$;$s!#(B


## 2.0.0-rc1 $B%j%j!<%9(B: 1 $B7nBh0l=5L\I8(B

$B$9$Y$F$N(B showstopper $B$,2r>C$5$l$?$i!"(B2.0.0-rc1 $B$r=P$7$^$9!#(B
($B?JD=<!Bh$GCY$l$k$+$b$7$l$^$;$s(B)

rc1 $B$NF0:n<B@S$r85$K(B platform support level 
$B$r7h$a$h$&$H;W$$$^$9!#(B
2.0.0-rc1 $B$N8e$O!"(Bshowstopper $B$G$J$$%P%0%A%1%C%H$r=PMh$k$@$12r7h(B
$B$9$k$h$&EXNO$7$^$9!#(B


## 2.0.0-rc2 $B%j%j!<%9(B: 2 $B7nBh0l=5L\I8(B

rc1 $B$N8e$GJs9p$5$l$?(B showstopper $B$r2r7h$7$?8e$G!"(B2.0.0-rc2 
$B$r(B
$B%j%j!<%9$7$^$9!#(B

$B$3$N;~$K(B ruby_2_0 $B$N%V%i%s%A$r:n$j$?$$$H;W$$$^$9!#(B

2.0.0-rc2 $B$N8e$G$O!"(Brc2 $B8e$KJs9p$5$l$?(B showstopper 
$B$N$_2r7h$7$^$9!#(B
regression $B$rHr$1$k$?$a!"86B'$H$7$F!"(Bshowstopper 
$B$G$J$$LdBj$N=$@5$O(B
$B9T$$$^$;$s!#(B


## 2.0.0-p0 release: 2/24

$B%Q!<%F%#!<!*(B

Endo-san

Every events are scheduled on JST, right?

2012/12/03 1:00$B!"(BYusuke Endoh <mame@tsg.ne.jp> $B$N%a%C%;!<%8(B:

Aizawa-san

Maybe.  But, please do your work well in advance so that
such a little difference will not matter ;-)


2012/12/03 Ayumu Aizawa <ayumu.aizawa@gmail.com>:

$B31$H$$$$$^$9!#(B

> ## $B%3!<%I%U%j!<%:(B: 12/23
>
> $B?75!G=<BAuDy$a@Z$j$G$9!#$3$NDy$a@Z$j$^$G$K<BAu$5$l$J$+$C$??75!G=$O(B
> ($B$?$H$((B accept $B$5$l$F$$$k$b$N$G$b(B) 2.0.0 $B$K4^$^$l$^$;$s!#(B

$B?75!G=$8$c$J$$$s$G$9$,(Berb.rb$B$r$A$g$C$H$@$1%j%U%!%/%?%j%s%0$7$F(B
hook$B$G$-$kItJ,$rA}$d$7$?$$$s$G$9$,!"$+$^$o$J$$$G$7$g$&$+!)(B

$B$$$^$,%A%c%s%9!)(B

Hi all,

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


We are working on brushing up Ruby 2.0.0 to release it. Now, the status
of Ruby 2.0.0 is "code freeze" and no newer features will be introduced.

We are identifying *critical* showstoppers in Ruby 2.0.0.
If you have spare time, please try Ruby 2.0.0 trunk with your
applications. If you find any trouble on it, please tell us.

Reference: Unresolved bugs
https://bugs.ruby-lang.org/projects/ruby-trunk/iss...
If your issues are registered as tickets and it should be solved until
2.0.0 release, please tell us. We will make them high priority.

Thank you for your help.

----
$BF|K\8l!'(B

Ruby 2.0.0 $B$N%j%j!<%9$K8~$1$F:n6H$r?J$a$F$$$^$9!%8=:_!$(B2.0.0 $B$O(B 
Code
freeze $B$H$$$&>uBV$H$J$C$F$*$j!$?7$7$$5!G=$OF~$i$J$$M=Dj$G$9!%(B

$B$=$3$G!$2f!9$O(B 2.0.0 
$B%j%j!<%9$r=P$9A0$K6[5^$K2r7h$9$k$Y$-LdBj$N@v$$=P$7(B
$B$r$7$F$*$j$^$9!%$b$7!$$*;~4V$,$"$j$^$7$?$i!$$4<+J,$N%"%W%j%1!<%7%g%s$r(B
ruby 2.0.0 trunk 
$B$GMxMQ$7$FD:$-!$LdBj$,$"$C$?$i$4Js9pD:$1$^$9$H=u$+$j$^$9!%(B

$B$4;29M!'$^$@2r7h$7$F$$$J$$%P%0!%(B
https://bugs.ruby-lang.org/projects/ruby-trunk/iss...
$B$9$G$KLdBj$,EPO?$5$l$F$*$j!$(B2.0.0 
$B$G$O2r7h$7$F$*$/$Y$-LdBj$H;W$o$l$?$i!$(B
$B$=$N;]$4O"Mm2<$5$$!%M%@hEY$r9b$/$7$F2r7h$7$^$9!%(B

$B$46(NO$K46<U$7$^$9!%(B


-------- Original Message --------
Subject: [ruby-dev:46689] [IMPORTANT] 2.0.0 release plan
Date: Mon, 3 Dec 2012 01:00:38 +0900
From: Yusuke Endoh <mame@tsg.ne.jp>
Reply-To: ruby-dev@ruby-lang.org
To: ruby-dev@ruby-lang.org (ruby developers list) 
,ruby-core@ruby-lang.org

ALL COMMITTERS SHOULD READ THIS MAIL! $B%3%_%C%?$O$3$N%a!<%kFI$s$G!*(B
ALL COMMITTERS SHOULD READ THIS MAIL! $B%3%_%C%?$O$3$N%a!<%kFI$s$G!*(B
ALL COMMITTERS SHOULD READ THIS MAIL! $B%3%_%C%?$O$3$N%a!<%kFI$s$G!*(B

Japanese follows; $BF|K\8l$O8e$G(B

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 $B%j%j!<%9$NM=Dj$r$*EA$($7$^$9!#(B
$B$3$NM=Dj$K4X$7$F2?$+0U8+$,$"$l$P(B ($BFC$KLdBj$,$"$k$H;W$&>l9g$O(B) 
$B$<$R(B
$B65$($F$/$@$5$$!#(B

## $B%$%Y%s%H(B

  - showstopper $B$NF1Dj(B: $B$J$k$Y$/Aa$a$K(B
  - $B%3!<%I%U%j!<%:(B: 12/23
  - 2.0.0-rc1 $B%j%j!<%9(B: 1 $B7nBh0l=5L\I8(B
  - 2.0.0-rc2 $B%j%j!<%9(B: 2 $B7nBh0l=5L\I8(B
  - 2.0.0-p0 $B%j%j!<%9(B: 2/24


## showstopper $B$NF1Dj(B: $B$J$k$Y$/Aa$a$K(B

300 $B7o$"$^$j$"$k%P%0%A%1%C%H$+$i(B showstopper $B$rF1Dj$7$^$9(B 
($BM%@hEY$r(B
Immediate $B$K$7$^$9(B) $B!#(Bshowstopper $B$H$O0J2<$r;X$7$^$9!#(B

  * $B:F8=@-$N$"$k(B SEGV
  * $B<B@$3&$N!"$^$?$O4{B8$N%W%m%0%i%`$K=EBg$J1F6A$rM?$($kLdBj(B
  * $B2sHr:v$,$J$$=EBg$JLdBj(B

$B$=$N8eJs9p$5$l$?%P%0%A%1%C%H$O?o;~H=CG$7$^$9!#(B


## $B%3!<%I%U%j!<%:(B: 12/23

$B?75!G=<BAuDy$a@Z$j$G$9!#$3$NDy$a@Z$j$^$G$K<BAu$5$l$J$+$C$??75!G=$O(B
($B$?$H$((B accept $B$5$l$F$$$k$b$N$G$b(B) 2.0.0 $B$K4^$^$l$^$;$s!#(B


## 2.0.0-rc1 $B%j%j!<%9(B: 1 $B7nBh0l=5L\I8(B

$B$9$Y$F$N(B showstopper $B$,2r>C$5$l$?$i!"(B2.0.0-rc1 $B$r=P$7$^$9!#(B
($B?JD=<!Bh$GCY$l$k$+$b$7$l$^$;$s(B)

rc1 $B$NF0:n<B@S$r85$K(B platform support level 
$B$r7h$a$h$&$H;W$$$^$9!#(B
2.0.0-rc1 $B$N8e$O!"(Bshowstopper $B$G$J$$%P%0%A%1%C%H$r=PMh$k$@$12r7h(B
$B$9$k$h$&EXNO$7$^$9!#(B


## 2.0.0-rc2 $B%j%j!<%9(B: 2 $B7nBh0l=5L\I8(B

rc1 $B$N8e$GJs9p$5$l$?(B showstopper $B$r2r7h$7$?8e$G!"(B2.0.0-rc2 
$B$r(B
$B%j%j!<%9$7$^$9!#(B

$B$3$N;~$K(B ruby_2_0 $B$N%V%i%s%A$r:n$j$?$$$H;W$$$^$9!#(B

2.0.0-rc2 $B$N8e$G$O!"(Brc2 $B8e$KJs9p$5$l$?(B showstopper 
$B$N$_2r7h$7$^$9!#(B
regression $B$rHr$1$k$?$a!"86B'$H$7$F!"(Bshowstopper 
$B$G$J$$LdBj$N=$@5$O(B
$B9T$$$^$;$s!#(B


## 2.0.0-p0 release: 2/24

$B%Q!<%F%#!<!*(B

(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

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


Thank you.

ALL COMMITTERS SHOULD READ THIS MAIL! $B%3%_%C%?$O$3$N%a!<%kFI$s$G!*(B
ALL COMMITTERS SHOULD READ THIS MAIL! $B%3%_%C%?$O$3$N%a!<%kFI$s$G!*(B
ALL COMMITTERS SHOULD READ THIS MAIL! $B%3%_%C%?$O$3$N%a!<%kFI$s$G!*(B

Japanese follows; $BF|K\8l$O8e$G(B


Sorry for my absence!  I tell you about the release plan of 2.0.0.

# 2.0.0-rc1 (in a few days)

I plan to release 2.0.0-rc1 as soon as there is no "showstopper" issue.
Please report to me any showstopper if you know.
I consider the following type of issue as a showstopper.

   * a build failure (in major platforms),
   * a reproducible segfault (in normal use case),
   * a problem that significantly affects real/existing programs, or
   * a serious problem that has no workaround.

I'd like to release rc1 tomorrow night in JST if all showstoppers are
fixed (or if there is no report).


# 2.0.0-rc2 (in early Feb.)

You can freely commit any bug fixes (including non-showstopper issues)
until 2.0.0-rc2.

Note that I plan to prohibit any non-showstopper bug fixes after rc2
(to prevent regression).
In other words, you will be able to commit only showstopper fixes after 
rc2.
So, if you have any non-showstopper issue that you want to fix, you
must do it in this month.


# 2.0.0-p0 (at 24th Feb.)

Thanks!


$B$7$P$i$/IT:_$K$7$F$9$_$^$;$s!#(B2.0.0 
$B$N%j%j!<%9%W%i%s$r$4O"Mm$7$^$9!#(B

# 2.0.0-rc1 ($B?tF|0JFb(B)

"showstopper" $B$JLdBj$,$J$/$J$j<!Bh(B 2.0.0-rc1 
$B$r%j%j!<%9$9$kM=Dj$G$9!#(B
showstopper $B$r$4B8CN$G$"$l$P?=9p$7$F$/$@$5$$!#(B
$B0J2<$N$h$&$JLdBj$r(B showstopper $B$H$_$J$7$^$9!#(B

   * ($B%a%8%c!<$J4D6-$G(B) $B%S%k%I$G$-$J$$LdBj(B
   * ($BDL>o$N%f!<%9%1!<%9$G$N(B) $B:F8=2DG=$J(B SEGV
   * $B8=<B$N!&4{B8$N%W%m%0%i%`$K=EBg$J1F6A$rM?$($kLdBj(B
   * $B2sHr:v$N$J$$=EBg$JLdBj(B

showstopper $B$,$9$Y$F=$@5$5$l$?$i(B ($B$^$?$OFC$K?=9p$,$J$1$l$P(B) 
$BF|K\;~4V$NL@F|$NLk$K(B
rc1 $B$r%j%j!<%9$7$?$$$H;W$$$^$9!#(B


# 2.0.0-rc2 (2 $B7n>e=\(B)

2.0.0-rc2 $B$^$G$OG$0U$N%P%0=$@5$r<+M3$K%3%_%C%H$7$F$/$@$5$$(B 
(showstopper $B0J30$b(B OK) $B!#(B

regression $B$rKI$0$?$a!"(Brc2 $B0J9_$O(B showstopper 
$B0J30$N%P%0=$@5$r6X;_$9$kM=Dj$G$9!#(B
$B$D$^$j!"(Brc2 $B0J9_$O(B showstopper 
$B$N=$@5$N$_$,%3%_%C%H2DG=$G$9!#(B
$B$h$C$F!"(Bshowstopper 
$B0J30$G=$@5$7$?$$LdBj$,$"$l$P!":#7nCf$K$d$C$F$/$@$5$$!#(B


# 2.0.0-p0 (2/24)

$B$h$m$7$/$*4j$$$7$^$9!*(B


2012/12/27 SASADA Koichi <ko1@atdot.net>: