[OpenStack-I18n] RFC: publishing translated release notes

Ian Y. Choi ianyrchoi at gmail.com
Mon Sep 19 18:18:46 UTC 2016

Hello Doug,

Since translators are now mainly focusing on translating user-facing 
projects (e.g., Horizon),
that I think would be fine to translators.

Andreas said that if reno needs fixes, strings might look different, so 
it is better for translators
not to translate releasenotes before some fixes on reno will be applied.

And it will be so great if you will come at I18n contributors meetup for 
short time
(AFAIK within 14:00-18:00 on Oct 30, during Barcelona Design Summit) to 
discuss this issue and go for further steps.

I remember that we had nice conversion on Austin I18n contributors meetup
(at that time, about releasenotes translation and PTG).

Doug Hellmann wrote on 9/20/2016 2:17 AM:
>> On Sep 19, 2016, at 4:08 AM, Andreas Jaeger <aj at suse.com> wrote:
>> On 2016-09-18 22:02, Andreas Jaeger wrote:
>>> I've done a proof of concept on how we could publish translated release
>>> notes:
>>> https://review.openstack.org/372167
>>> I've added two open questions to the review - please look at it and give
>>> me your suggestions. If anybody comes up with a better solution, this
>>> would be more than welcome,
>>> Note that currently only 19 repos have translations for release notes -
>>> out of 197 repos that have release notes,
>> Somehow the releasenotes itself do not get translated. A few lines have
>> translations but lots is missing.
>> For example, check:
>> http://users.suse.com/~aj/horizon-releasenotes/
>> http://users.suse.com/~aj/trove-dashboard-releasenotes/
>> And compare with openstack-manuals that does not use reno:
>> http://users.suse.com/~aj/openstack-manuals-release-notes/
>> My guess is that the string extraction - or merging back - is not
>> working with reno as we would expect it.
>> Is there anyone that could investigate this, please?
>> The script can be run easily locally.
>> I won't have time this week to work further on this,
> Andreas,
> Thank you for taking the next step in this process. It was on the task list for the release team this cycle, but slipped again, so I really appreciate your work.
I really appreciate Andreas's kind caring of this. Also, thank you very 
much for remembering this as task list.
I would like to happily keep track of this issue and try to find ways to 
address it, as a candidacy for I18n Ocata PTL.

With many thanks,

> Unfortunately, now that we are in the release candidate period, I do not expect to have time to look at the issue myself. We should try to get it working before the Ocata-1 milestone, though. Let me know if that works with your anticipated workload.
> Doug
>> Andreas
>> -- 
>> Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
>>   SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
>>    GF: Felix Imendörffer, Jane Smithard, Graham Norton,
>>        HRB 21284 (AG Nürnberg)
>>     GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
> _______________________________________________
> OpenStack-I18n mailing list
> OpenStack-I18n at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n

More information about the OpenStack-I18n mailing list