I just thought that we needed to take care of all releases since Zanata has 'only' master branch for releasenotes,
On Oct 8, 2016, at 5:55 AM, Akihiro Motoki <amotoki@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 cycleand Liberty release notes are converted into reno-based release notes.This mean if we want to publish Newton release notes translation, we need to translaterelease 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 translationto 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.
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).
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.
Proposed threshold 75% and 40% might need to be revisited.
+1
== 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 betternot to publish Mitaka and Liberty release notes translation or to publish all?
My vote is not to publish less-translated version of release notes.
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 :)
== 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.
Akihiro
_______________________________________________ OpenStack-I18n mailing list OpenStack-I18n@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n