[#61822] Plan Developers Meeting Japan April 2014 — Zachary Scott <e@...>
I would like to request developers meeting around April 17 or 18 in this mo=
14 messages
2014/04/03
[#61825] Re: Plan Developers Meeting Japan April 2014
— Urabe Shyouhei <shyouhei@...>
2014/04/03
It's good if we have a meeting then.
[#61826] Re: Plan Developers Meeting Japan April 2014
— Zachary Scott <e@...>
2014/04/03
Regarding openssl issues, I=E2=80=99ve discussed possible meeting time with=
[#61833] Re: Plan Developers Meeting Japan April 2014
— Martin Bo煬et <martin.bosslet@...>
2014/04/03
Hi,
[#61847] Re: Plan Developers Meeting Japan April 2014
— Eric Wong <normalperson@...>
2014/04/03
Martin Boテ殕et <martin.bosslet@gmail.com> wrote:
[#61849] Re: Plan Developers Meeting Japan April 2014
— Zachary Scott <e@...>
2014/04/04
I will post summary of meeting on Google docs after the meeting.
[#61852] Re: Plan Developers Meeting Japan April 2014
— Eric Wong <normalperson@...>
2014/04/04
Zachary Scott <e@zzak.io> wrote:
[#61860] Re: Plan Developers Meeting Japan April 2014
— Zachary Scott <e@...>
2014/04/04
I=E2=80=99m ok with redmine, thanks for bringing up your concern!
[#62076] Candidacy to 2.1 branch maintainer. — Tomoyuki Chikanaga <nagachika00@...>
Hello,
7 messages
2014/04/17
[#62078] Re: Candidacy to 2.1 branch maintainer.
— SHIBATA Hiroshi <shibata.hiroshi@...>
2014/04/17
> And does anyone have counter proposal for 2.1 maintenance?
[ruby-core:62051] new Ruby 2.0.0 maintainer
From:
"U.Nakamura" <usa@...>
Date:
2014-04-16 08:23:49 UTC
List:
ruby-core #62051
Hi, all Based on "Ruby stable version maintenance commission project" of the Ruby Association, I become the maintainer of ruby 2.0.0. The span of the maintenance by me is scheduled from April, 2014 to March, 2015. About the policy of the maintenance, it is not different from Chikanaga-san's. That is: * In principle, only bug fixes will be backported. Feature changes will not be so. * As much as possible, compatibility are maintained. * When a big security issue is discovered, it releases promptly. * If there is no special situation, new patchlevel package will be released at intervals of about three months. Please use ruby redmine (https://bugs.ruby-lang.org) to report the bug of 2.0.0. If you already know that the bug doesn't exist in other version, create a ticket directly on backport20. If not, create a ticket on ruby-trunk and describe so. You can also use "backport" column to note that there is the problem in 2.0.0. When you create ticket in ruby-trunk, it is not necessary to create a backport ticket separately. I say deep gratitude to efforts of Chikanaga-san. Thank you! Regards, -- U.Nakamura <usa@garbagecollect.jp>