@nagachika will become the maintainer of 2.0.0 branch

Yusuke_E · February 14, 2013, 6:12pm

Hello,

I’m writing with regard to a maintainer of 2.0.0.

I’m a 2.0.0 release manager, and it will be released in ten days.
I think that I’m not good at a maintainer because I don’t have
perseverance and conscientiousness required by the job (and because
I’m not so interested in maintenance

So I decided to hand over the ruby_2_0_0 branch maintenance task to
Tomoyuki C. (@nagachika). He and matz have already consented.

He is a crazy committer who has read all commits of trunk and written
the summary in his (Japanese) blog everyday since 2010. I think of
no one better suited to the task.

I leave the concrete maintenance policy up to @nagachika.

Thanks!

Yusuke_E · February 14, 2013, 6:41pm

+1 Thanks for all of your hard work nagachika-san!

Yusuke_E · February 15, 2013, 7:13pm

On Fri, Feb 15, 2013 at 02:12:01AM +0900, Yusuke E. wrote:

Tomoyuki C. (@nagachika). He and matz have already consented.

He is a crazy committer who has read all commits of trunk and written
the summary in his (Japanese) blog everyday since 2010. I think of
no one better suited to the task.

I leave the concrete maintenance policy up to @nagachika.

Congratulations @nagachika!

よろしくお願いします！

Yusuke_E · February 19, 2013, 5:32pm

Japanese version follows; $BF|K\8l$O$"$H$G(B

Hello Rubyists.

Endoh-san, Thank you for introducing me and refer me as branch
maintainer.

As a 2.0.0 maintainer, I announce maintenance policy of ruby_2_0_0
branch.
There’s nothing new, similar to previous maintenance policies.

emphasize compatibility and stability.
- Any new features will not be backported.
- Bug fix will be backported.
  - Security related fixes have higher priority.

As we see in past days, there’s wide ambiguous cases between “new
feature” and “bug fix”.
I’ll consider about each borderline case with discussions. Please help
me
And I’m not sure about treatment of ‘experimental features’. We’ll
discuss about it in developer’s meeting in the next weekend. Any
comments are welcome.

Ticket driven backport
- If you want some commits to be backported, please file a backport
  ticket in ruby200 project in redmine.
  Overview - Backport200 - Ruby Issue Tracking System
- I’ll also file a ticket for backport commits even if I decide to
  backport by myself.
  However I’ll backport trivial changes such as cosmetic changes and
  fix typos without filing a ticket.

Please note that until Ruby 2.0.0 release, Endoh-san who is the release
manager
makes decision of backport to ruby_2_0_0 branch.

Thanks.

($B$9$_$^$;$s!“(Bruby-dev
$B$K$N$_JV?.$7$F$7$^$C$?$N$G:FEYAw?.$7$^$9!#$$$-$J$j<:GT$7$F$7$^$$$^$7$?(B)
$B$3$s$K$A$o!”$3$NEY(B 2.0.0 $B%V%i%s%A%a%s%F%J$r$9$k$3$H$K$J$C$?(B
nagachika $B$3$H6a1J$H?=$7$^$9!#(B
$B$h$m$7$/$*4j$$$7$^$9!#(B

$B1sF#$5$s!“$4>R2p$H%a%s%F%J?dA&$”$j$,$H$&$4$&$6$$$^$7$?!#(B

ruby_2_0_0 $B%V%i%s%A$N%a%s%F%J%s%9J}?K$K$D$$$F$^$H$a$^$7$?!#(B
$B$H$$$C$F$b$3$l$^$G(B($BFC$K(B
1.9.3)$B$N;~$H$"$^$jJQ$o$j$P$($O$7$J$$$G$9!#(B

$B!&(B $B8_49@-$H0BDj@-$r=E;k$7$^$9(B
$B!&(B $B?75!G=$O<h$j9~$^$l$^$;$s(B
$B!&(B $BIT6q9g=$@5$OH?1G$7$^$9!#FC$K@H<e@-BP:v$OM%@hE*$KBP=h$7$^$9(B
$B$?$@$3$l$^$G$N7P83$+$iL@$i$+$J$h$&$K!“IT6q9g=$@5$H;EMMJQ99$N4V$K$O(B
$B$I$A$i$H$b8@$$$,$?$$%0%l!<%>!<%s$,$”$j$^$9!#(B
$B$=$&$$$C$?%1!<%9$G$O8DJL$K5DO@$N>eBP=h$7$^$9!#(B
$B$^$?!“(B"experimental”
$B$H%^!<%/$5$l$F$$$k5!G=$N07$$$K$D$$$F$OG:$_Cf$G!"(B
$B:#=5Kv$N3+H/<T2q5D$N5DBj$H$7$^$9!#(B

$B!&%A%1%C%H6nF0%P%C%/%]!<%H(B
$B!&%P%C%/%]!<%H$7$?$$JQ99$,$"$l$P(B ruby200
$B%W%m%8%‘%/%H$K%P%C%/%]!<%H%A%1%C%H$r:n@.$7$F$/$@$5$$(B
Overview - Backport200 - Ruby Issue Tracking System
$B!&$o$?$7$,<+H/E*$K%3%_%C%H$r%A%’%C%/$7$FJQ99$r%P%C%/%]!<%H$9$k>l9g$G$b%A%1%C%H$r:n@.$7$F=hM}$7$^$9!#(B
$B$?$@$7%9%?%$%k$N=$@5$d(Btypo$B=$@5$J$I$N:3:Y$JJQ99$O%A%1%C%H2=$;$:$K%P%C%/%]!<%H$7$^$9!#(B

$B$J$*(B 2.0.0
$B$N%j%j!<%9$^$G$O%j%j!<%9%^%M!<%8%c$N1sF#$5$s$K%P%C%/%]!<%H2DH]$N7hDj8"$,$"$j$^$9!#(B

2013/2/15 Yusuke E. [email protected]:

Yusuke_E · February 19, 2013, 5:46pm