[#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,

[ruby-core:62230] Re: Candidacy to 2.1 branch maintainer.

From: "NARUSE, Yui" <naruse@...>
Date: 2014-04-30 02:53:10 UTC
List: ruby-core #62230
I agree with the scheme.

2014-04-29 0:58 GMT+09:00 Tomoyuki Chikanaga <nagachika00@gmail.com>:
> Hi,
>
>> I agree with the scheme.
>>
>>                                                        matz.
> Thank you for your reply.
>
> naruse-san, how do you think?
>
>
>
> 2014-04-26 17:25 GMT+09:00 Yukihiro Matsumoto <matz@ruby.or.jp>:
>> Hi,
>>
>> I agree with the scheme.
>>
>>                                                         matz.
>>
>>
>> In message "Re: [ruby-core:62119] Re: Candidacy to 2.1 branch maintainer."
>>     on Tue, 22 Apr 2014 01:22:28 +0900, Tomoyuki Chikanaga <nagachika00@gmail.com> writes:
>> |
>> |Hi,
>> |
>> |> I hope to support you. Can I commit for 2.1 branch?
>> |Supports for release engineering are welcome.
>> |But I think backport management have some complexities.
>> |The maintainers should have cooperate closely if they have equal authority.
>> |My proposal is as below.
>> |
>> |1. Co-maintainer can request permission for individual backport/release.
>> |2. Maintainer approve it (or do it by myself)
>> |3. Co-maintainer can commit maintenance branch or release package.
>> |
>> |How about this scheme?
>> |
>> |Anyway I appreciate to your proposal :)
>> |
>> |Regards,



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

In This Thread

Prev Next