<br>
<br>
On Thu, Oct 23, 2014 at 10:17 PM, Tom Fifield <<a href="javascript:;" onclick="_e(event, 'cvml', 'tom@openstack.org')">tom@openstack.org</a>> wrote:<br>
> On 23/10/14 21:07, Akihiro Motoki wrote:<br>
>><br>
>><br>
>> 2014年10月23日木曜日、Ying Chun Guo<<a href="javascript:;" onclick="_e(event, 'cvml', 'guoyingc@cn.ibm.com')">guoyingc@cn.ibm.com</a><br>
>> <mailto:<a href="javascript:;" onclick="_e(event, 'cvml', 'guoyingc@cn.ibm.com')">guoyingc@cn.ibm.com</a>>>さんは書きました:<br>
>><br>
>> Akihiro Motoki <<a href="javascript:;" onclick="_e(event, 'cvml', 'amotoki@gmail.com')">amotoki@gmail.com</a><br>
>> <javascript:_e(%7B%7D,'cvml','<a href="javascript:;" onclick="_e(event, 'cvml', 'amotoki@gmail.com')">amotoki@gmail.com</a>');>> wrote on<br>
>> 2014/10/22 21:09:51:<br>
>><br>
>> > Akihiro Motoki <<a href="javascript:;" onclick="_e(event, 'cvml', 'amotoki@gmail.com')">amotoki@gmail.com</a><br>
>> <javascript:_e(%7B%7D,'cvml','<a href="javascript:;" onclick="_e(event, 'cvml', 'amotoki@gmail.com')">amotoki@gmail.com</a>');>><br>
>> > 2014/10/22 21:09<br>
>> ><br>
>> > To<br>
>> ><br>
>> > "<a href="javascript:;" onclick="_e(event, 'cvml', 'openstack-i18n@lists.openstack.org')">openstack-i18n@lists.openstack.org</a><br>
>> <javascript:_e(%7B%7D,'cvml','<a href="javascript:;" onclick="_e(event, 'cvml', 'openstack-i18n@lists.openstack.org')">openstack-i18n@lists.openstack.org</a>');>" <<a href="javascript:;" onclick="_e(event, 'cvml', 'Openstack-i18n@lists.openstack.org')">Openstack-i18n@lists.openstack.org</a><br>
>> <javascript:_e(%7B%7D,'cvml','<a href="javascript:;" onclick="_e(event, 'cvml', 'Openstack-i18n@lists.openstack.org')">Openstack-i18n@lists.openstack.org</a>');>>,<br>
>> ><br>
>> > cc<br>
>> ><br>
>> > Subject<br>
>> ><br>
>> > Re: [Openstack-i18n] Translation update process for stable branch(es)<br>
>> ><br>
>> > Hi all,<br>
>> ><br>
>> > I can have time to read the meeting log of the I18N team this week<br>
>> [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<br>
>> 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<br>
>> 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<br>
>> 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>
>> ><br>
>> +1<br>
>><br>
>> > (2) When we remove the previous current stable (Icehouse) from<br>
>> 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>
>> ><br>
>><br>
>> How do you think of just marking them as "not accept translation"?<br>
>><br>
>><br>
>> What is a merit of keeping old translations with "not accept translation"?<br>
><br>
><br>
> This is my understanding (could be 100% wrong) of how the translation<br>
> dictionary works...<br>
><br>
> Scenario 1 "Keep old translations":<br>
> * String from old version appears as suggestion in new version<br>
><br>
> Scenario 2 "Delete old translations":<br>
> * No suggestion strings based on old versions appear when translating<br>
> new versions<br>
><br>
><br>
> So, potentially, removing the old translations destroys some useful<br>
> translation dictionary entries. I could be completely wrong here, so it<br>
> is worth confirming this, if such translation dictionary entries are<br>
> deemed useful :)<br>
<br>
Yes. this is a very important point.<div>We need to check if the translation memory is kept after deleting some resources.<br>
IIRC Daisy said she will check it.<br>I just would like to clarify the reason of decisions. If we need more time to check it, it is also a good reason to keep resources.</div><div><br>Thanks</div><div>Akihiro<br>
><br>
><br>
>> When we mark them so? When will they be deleted?<br>
>><br>
>> I am okay with either option as long as there is a concrete proposal.<br>
>> Honestly just an question does not help me.<br>
>> I am tired from coordinating various dates.<br>
>><br>
>> Personally I don't like the progress percentage is displayed with higher<br>
>> value<br>
>> due to old translation?<br>
>><br>
>><br>
>><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/" target="_blank">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 <<a href="javascript:;" onclick="_e(event, 'cvml', 'amotoki@gmail.com')">amotoki@gmail.com</a><br>
>> <javascript:_e(%7B%7D,'cvml','<a href="javascript:;" onclick="_e(event, 'cvml', 'amotoki@gmail.com')">amotoki@gmail.com</a>');>> 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<br>
>> 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<br>
>> translation update.<br>
>> > ><br>
>> > > Questions are:<br>
>> > ><br>
>> > > - What release(s) we accept translations?<br>
>> > > Note that "Accept translations" means translations will be<br>
>> 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<br>
>> release.<br>
>> > ><br>
>> > > - When should we import translations to a stable branch?<br>
>> > > Systematically (as a team)? Occasionally (up to someone's<br>
>> 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)<br>
>> 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<br>
>> 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 <<a href="javascript:;" onclick="_e(event, 'cvml', 'amotoki@gmail.com')">amotoki@gmail.com</a><br>
>> <javascript:_e(%7B%7D,'cvml','<a href="javascript:;" onclick="_e(event, 'cvml', 'amotoki@gmail.com')">amotoki@gmail.com</a>');>><br>
>> ><br>
>> ><br>
>> ><br>
>> > --<br>
>> > Akihiro Motoki <<a href="javascript:;" onclick="_e(event, 'cvml', 'amotoki@gmail.com')">amotoki@gmail.com</a><br>
>> <javascript:_e(%7B%7D,'cvml','<a href="javascript:;" onclick="_e(event, 'cvml', 'amotoki@gmail.com')">amotoki@gmail.com</a>');>><br>
>> ><br>
>> > _______________________________________________<br>
>> > Openstack-i18n mailing list<br>
>> > <a href="javascript:;" onclick="_e(event, 'cvml', 'Openstack-i18n@lists.openstack.org')">Openstack-i18n@lists.openstack.org</a><br>
>> <javascript:_e(%7B%7D,'cvml','<a href="javascript:;" onclick="_e(event, 'cvml', 'Openstack-i18n@lists.openstack.org')">Openstack-i18n@lists.openstack.org</a>');><br>
>> > <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n</a><br>
>> ><br>
>><br>
>><br>
>><br>
>> --<br>
>> Akihiro Motoki <<a href="javascript:;" onclick="_e(event, 'cvml', 'amotoki@gmail.com')">amotoki@gmail.com</a> <mailto:<a href="javascript:;" onclick="_e(event, 'cvml', 'amotoki@gmail.com')">amotoki@gmail.com</a>>><br>
>><br>
>><br>
>> _______________________________________________<br>
>> Openstack-i18n mailing list<br>
>> <a href="javascript:;" onclick="_e(event, 'cvml', 'Openstack-i18n@lists.openstack.org')">Openstack-i18n@lists.openstack.org</a><br>
>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n</a><br>
>><br>
><br>
><br>
> _______________________________________________<br>
> Openstack-i18n mailing list<br>
> <a href="javascript:;" onclick="_e(event, 'cvml', 'Openstack-i18n@lists.openstack.org')">Openstack-i18n@lists.openstack.org</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n</a><br>
<br>
<br>
<br>
--<br>
Akihiro Motoki <<a href="javascript:;" onclick="_e(event, 'cvml', 'amotoki@gmail.com')">amotoki@gmail.com</a>><br>
</div><br><br>-- <br>Akihiro Motoki <<a href="mailto:amotoki@gmail.com" target="_blank">amotoki@gmail.com</a>><br>