<html><body>
<p><tt><font size="2">Akihiro Motoki <amotoki@gmail.com> wrote on 2014/10/22 21:09:51:<br>
<br>
> Akihiro Motoki <amotoki@gmail.com> </font></tt><br>
<tt><font size="2">> 2014/10/22 21:09</font></tt><br>
<tt><font size="2">> <br>
> To</font></tt><br>
<tt><font size="2">> <br>
> "openstack-i18n@lists.openstack.org" <Openstack-i18n@lists.openstack.org>, </font></tt><br>
<tt><font size="2">> <br>
> cc</font></tt><br>
<tt><font size="2">> <br>
> Subject</font></tt><br>
<tt><font size="2">> <br>
> Re: [Openstack-i18n] Translation update process for stable branch(es)</font></tt><br>
<tt><font size="2">> <br>
> Hi all,<br>
> <br>
> I can have time to read the meeting log of the I18N team this week [1].<br>
> <br>
> According to the log, the team agreed that we maintain two resources<br>
> (1 stable + current)<br>
> for accepting translations. Now Juno is released, so we maintain<br>
> resources for Juno and current,<br>
> and we no longer accepts translations for Icehouse. I think it is reasonable.<br>
> <br>
> According to this policy, we will delete havana and Icehouse<br>
> translations from Transifex. Right?<br>
> <br>
> Now it raise me a couple of questions on how to handle Icehouse translations.<br>
> <br>
> (1) Until when we accept Icehouse (previous current stable)?<br>
> <br>
> My idea is we accept translations until the first stable update for Icehouse<br>
> after the new stable (Juno) is released, i.e, until Icehouse 2014.1.4.<br>
> By doing so, we don't lose Icehouse translations before Juno release.<br>
> I see Russian translation made a great progress after the last import<br>
> for Icehouse (2014.1.2)<br>
> and it is worth imported.<br>
> </font></tt><br>
<tt><font size="2">+1</font></tt><br>
<tt><font size="2"><br>
> (2) When we remove the previous current stable (Icehouse) from Transifex?<br>
> <br>
> My idea is just after the timing of (1), i.e., just after Icehouse<br>
> udpate 2014.1.4 is released.<br>
> </font></tt><br>
<br>
<tt><font size="2">How do you think of just marking them as "not accept translation"?</font></tt><br>
<tt><font size="2"><br>
> Thought?<br>
> <br>
> Note that the above proposal does not necessarily mean I can work for<br>
> importing them.<br>
> <br>
> [1] <a href="http://eavesdrop.openstack.org/meetings/openstack_i18n_meeting/">http://eavesdrop.openstack.org/meetings/openstack_i18n_meeting/</a><br>
> 2014/openstack_i18n_meeting.2014-10-16-08.00.log.html<br>
> <br>
> On Fri, Oct 3, 2014 at 6:41 PM, Akihiro Motoki <amotoki@gmail.com> wrote:<br>
> > Hi all,<br>
> ><br>
> > In this mail I would like to discuss what releases do we accept <br>
> translations.<br>
> ><br>
> > At now there is no systematic process when we import translations<br>
> > after the initial release of some version (Juno, Icehouse, ...).<br>
> > Importing translations to stable update is done occasionally so far.<br>
> > It is almost up to me. When I noticed some need for translation update<br>
> > (mainly in Japanese :-)), I propose a patch to import translations.<br>
> > It is really not systematic. If I am busy, I don't check it.<br>
> > This is the reason the first Icehouse update didn't have translation update.<br>
> ><br>
> > Questions are:<br>
> ><br>
> > - What release(s) we accept translations?<br>
> > Note that "Accept translations" means translations will be imported<br>
> > into a stable branch and releases as a part of the stable update<br>
> > release.<br>
> ><br>
> > My idea is to accept translations only for the latest stable release.<br>
> ><br>
> > - When should we import translations to a stable branch?<br>
> > Systematically (as a team)? Occasionally (up to someone's interest)?<br>
> ><br>
> > My vote is to import translations for each stable update of the<br>
> > latest stable branch.<br>
> > At least the first and second stable update (201X.Y.1 or .2) need to<br>
> > be considered.<br>
> ><br>
> ><br>
> > If we decide to do import as a stable release process as a team,<br>
> > we should assign someone to work on for each stable update<br>
> > (because I can't always take care of it).<br>
> > Assigned person(s) should check the date of a next stable update,<br>
> > check if there are new translations to be imported, and then propose<br>
> > a patch to import translations to a corresponding stable branch.<br>
> ><br>
> > I already have a consensus with the stable maintenance team that<br>
> > the deadline of translations import proposal is 3 day after the freeze date.<br>
> > The freeze date of a stable maintenance release is usually announced<br>
> > in stable-maint list.<br>
> ><br>
> > Thought? Any volunteer?<br>
> ><br>
> > --<br>
> > Akihiro Motoki <amotoki@gmail.com><br>
> <br>
> <br>
> <br>
> -- <br>
> Akihiro Motoki <amotoki@gmail.com><br>
> <br>
> _______________________________________________<br>
> Openstack-i18n mailing list<br>
> Openstack-i18n@lists.openstack.org<br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n</a><br>
> <br>
</font></tt></body></html>