[OpenStack-I18n] translated release note: import criteria and publishing

Ian Y. Choi ianyrchoi at gmail.com
Sun Oct 9 05:50:44 UTC 2016

Thank you Akihiro and Doug!

Please see my comment inline.

Doug Hellmann wrote on 10/8/2016 11:35 PM:
>> On Oct 8, 2016, at 5:55 AM, Akihiro Motoki <amotoki at gmail.com 
>> <mailto:amotoki at gmail.com>> wrote:
>> Hi i18n team,
>> CC: Doug from the release team.
>> We are now preparing translated version of release notes.
>> I would like to discuss the import criteria of release notes translation.
>> If there is a better way, it would be great.
>> == Problem ==
>> Release notes translation is imported when 75% of a PO file is 
>> translated.
>> 75% is calculated as a whole.
>> If a language team wants to translate release notes of a specific 
>> release,
>> the team needs to translate release notes of other releases.
>> This comes from the fact that the translation percentage is 
>> calculated as a whole.
>> The development teams started to use reno for translation at the 
>> beginning of Mitaka cycle
>> and Liberty release notes are converted into reno-based release notes.
>> This mean if we want to publish Newton release notes translation, we 
>> need to translate
>> release notes for Liberty and Mitaka at the same time.
>> == Proposal ==
>> I hope we can publish translated release notes per release.
>> If Newton release notes translation completes, I want to publish 
>> Newton release notes.
>> My proposal is to change the import criteria for release notes 
>> translation
>> to 75% at least for a specific release.
> I agree that it makes sense to translate by release, if we can make 
> the tool changes needed. I don’t have an opinion about what percent of 
> the text needs to be translated for it to be useful — I’m sure all of 
> you have more insight into that than I do.
I just thought that we needed to take care of all releases since Zanata 
has 'only' master branch for releasenotes,
and so I have not thought 'translate by release' concept.
It will be great for translation by release.

Thank you Akihiro-san for 'translate by release' idea with 
implementation commit request.

IMO upper percent value is fine, since the values are the same in 
common_translate_update.sh [3].


>> If translation progress of release notes are less than 40% for all 
>> releases,
>> a corresponding PO file will be removed from the repo.
>> I proposed an infra scirpt change to implement the above.
>> https://review.openstack.org/#/c/383622/
>> Proposed threshold 75% and 40% might need to be revisited.
By the way, I think we need to discuss the value minimum: 40%, since the 
value has been changed from previous 20% (actually 8% in script).

I have updated [4] about several months ago. At that time I just 
referred Wiki documentation [5].
On March, the value was still 20% [6].

IMO Andreas temporally changed the value from 20% to 30% [7] and 40% [8] 
for cleaning up purposes.
So which minimum percent value would be appropriate for I18n team?

[4] http://docs.openstack.org/developer/i18n/infra.html#translation-jobs
[7] https://review.openstack.org/#/c/372141/
[8] https://review.openstack.org/#/c/375285/
>> == Open question ==
>> Do we publish translated release notes for a release with <75% progress?
>> This is about publishing rendered release notes.
>> For example, assume my lang team have translated release notes
>> 90% for Newton, 10% for Mitaka and Liberty. In this case, which is better
>> not to publish Mitaka and Liberty release notes translation or to 
>> publish all?
>> My vote is not to publish less-translated version of release notes.

Also I have a question.
So the criteria "for release notes translation to 75% at least for a 
specific release" means
for all the project repositories, or for one project repository?

For example, if one language team is interested mainly in Nova Newton 
release, the team
translated only releasenotes strings for Newton release in 
openstack/nova repository, then would it be published?

I am not currently sure how translated releasenotes landing page will be 
built and/or organized,
but I think it is not a good idea to add just a link to Newton horizon 
releasenotes page in docs.o.o/[language]/index.html page.

>> == Note ==
>> Question from Ian on the gerrit review.
>> By the way, is it possible to see only Newton release note strings in 
>> Zanata?
>> Answer: The current Zanata version we use does not support filtering 
>> by an original filename.
>> You need to check English release notes like [1] or [2] and search 
>> strings on Zanata.
>> [1] https://releases.openstack.org/newton/index.html
>> [2] http://docs.openstack.org/releasenotes/horizon/
Oh I have not thought such methods: using two web browser windows, one 
is for English release notes and and the other is for string search in 
Zanata :)

With many thanks,

>> Akihiro
> _______________________________________________
> OpenStack-I18n mailing list
> OpenStack-I18n at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-i18n/attachments/20161009/42f05d07/attachment-0001.html>

More information about the OpenStack-I18n mailing list