From: Yehuda Katz <wycats@...>
Date: 2009-02-14T09:16:34+09:00
Subject: [ruby-core:22056] Re: A short memorandum (Re: 1.8.7 Specifics)

--001636e0a91c7d2ed20462d5e08c
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

On Fri, Feb 13, 2009 at 2:51 AM, Urabe Shyouhei <shyouhei@ruby-lang.org>wrote:

> Let me leave a memo to remember issues I can think of.
>
> Ezra Zygmuntowicz wrote:
> > We will need a little bit of time to coordinate the transfer of
> > stewardship and setup communication channels to you guys for security
> > related issues. Monday is a holiday here and I need to prepare for this
> > a little bit before we can fully take over. But we can start the
> > planning process now.
>
> * When to transfer
>
> Could I ask you a favor?  In fact it is a bit inconvenient for me
> to pass you current 1.8.6 source code right now, because a series
> of backportings are now in practice.
>
> It is technically possible for me to  do all that job in a day or
> two, but last time I did a backport rush rubyspec people screamed
> with the  amount of changes.   So I want  to do that  slowly this
> time.  Current expectation in my mind is to finish backporting in
> this month and to make a new (and possibly last) 1.8.6 release at
> some point in March.


Out of curiosity, which backportings are these?

-- Yehuda


>
>
> I will be really happy if the stewardship transfer can be delayed
> until that.
>
>
> * Where to host 1.8.6 source code
>
> My recommendation  is not to move from  ruby-lang.org.  Thanks to
> massive efforts  made by yugui  we already have  a semi-automatic
> issue tracking on redmine.rubyu-lang.org  in service.  It is much
> easier for you to get used to that than reinvent a wheel.
>
> But I  do not stop you  to move elsewhere.  Above  is my personal
> recommendation.  Feel free to use github or whatever when you are
> motivated.  In that case, we need to think about bug reports:
>
>
> * Report line
>
> People tend not  to know what version they  are using.  Splitting
> 1.8.6  issue tracker  should  not  make us  happy.   You need  an
> account  on  our  ITS, and  act  as  a  release manager  on  some
> projects.
>
> Talking about security issues  our current public window for them
> is security@ruby-lang.org.  You should listen to that channel.
>
>


-- 
Yehuda Katz
Developer | Engine Yard
(ph) 718.877.1325

--001636e0a91c7d2ed20462d5e08c
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<br><br><div class=3D"gmail_quote">On Fri, Feb 13, 2009 at 2:51 AM, Urabe S=
hyouhei <span dir=3D"ltr">&lt;<a href=3D"mailto:shyouhei@ruby-lang.org">shy=
ouhei@ruby-lang.org</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quo=
te" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;=
">
Let me leave a memo to remember issues I can think of.<br>
<br>
Ezra Zygmuntowicz wrote:<br>
&gt; We will need a little bit of time to coordinate the transfer of<br>
&gt; stewardship and setup communication channels to you guys for security<=
br>
&gt; related issues. Monday is a holiday here and I need to prepare for thi=
s<br>
&gt; a little bit before we can fully take over. But we can start the<br>
&gt; planning process now.<br>
<br>
* When to transfer<br>
<br>
Could I ask you a favor? &nbsp;In fact it is a bit inconvenient for me<br>
to pass you current 1.8.6 source code right now, because a series<br>
of backportings are now in practice.<br>
<br>
It is technically possible for me to &nbsp;do all that job in a day or<br>
two, but last time I did a backport rush rubyspec people screamed<br>
with the &nbsp;amount of changes. &nbsp; So I want &nbsp;to do that &nbsp;s=
lowly this<br>
time. &nbsp;Current expectation in my mind is to finish backporting in<br>
this month and to make a new (and possibly last) 1.8.6 release at<br>
some point in March.</blockquote><div><br></div><div>Out of curiosity, whic=
h backportings are these?</div><div><br></div><div>-- Yehuda</div><div>&nbs=
p;</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border=
-left:1px #ccc solid;padding-left:1ex;">
<br>
<br>
I will be really happy if the stewardship transfer can be delayed<br>
until that.<br>
<br>
<br>
* Where to host 1.8.6 source code<br>
<br>
My recommendation &nbsp;is not to move from &nbsp;<a href=3D"http://ruby-la=
ng.org" target=3D"_blank">ruby-lang.org</a>. &nbsp;Thanks to<br>
massive efforts &nbsp;made by yugui &nbsp;we already have &nbsp;a semi-auto=
matic<br>
issue tracking on <a href=3D"http://redmine.rubyu-lang.org" target=3D"_blan=
k">redmine.rubyu-lang.org</a> &nbsp;in service. &nbsp;It is much<br>
easier for you to get used to that than reinvent a wheel.<br>
<br>
But I &nbsp;do not stop you &nbsp;to move elsewhere. &nbsp;Above &nbsp;is m=
y personal<br>
recommendation. &nbsp;Feel free to use github or whatever when you are<br>
motivated. &nbsp;In that case, we need to think about bug reports:<br>
<br>
<br>
* Report line<br>
<br>
People tend not &nbsp;to know what version they &nbsp;are using. &nbsp;Spli=
tting<br>
1.8.6 &nbsp;issue tracker &nbsp;should &nbsp;not &nbsp;make us &nbsp;happy.=
 &nbsp; You need &nbsp;an<br>
account &nbsp;on &nbsp;our &nbsp;ITS, and &nbsp;act &nbsp;as &nbsp;a &nbsp;=
release manager &nbsp;on &nbsp;some<br>
projects.<br>
<br>
Talking about security issues &nbsp;our current public window for them<br>
is <a href=3D"mailto:security@ruby-lang.org">security@ruby-lang.org</a>. &n=
bsp;You should listen to that channel.<br>
<br>
</blockquote></div><br><br clear=3D"all"><br>-- <br>Yehuda Katz<br>Develope=
r | Engine Yard<br>(ph) 718.877.1325<br>

--001636e0a91c7d2ed20462d5e08c--