Open Stack

Thanks Kato and Andreas for clarification.

In my local testing, POT file generation and translated document generation work
though some minor improvements are needed. I don't see blocking issues so far.
So I think what we need to do are:
* Automatic generation of POT files (granularity of POT files needs to
be discussed. In my understanding, all release notes are generated
from the master branch.)
* How and where to publish translated release notes
* Where to have locale files in each project tree
* Infra script improvements of translation imports
  (As a project core reviewer, we don't want to have two zanata
translation imports
   for normal translations and release note translations)
Others?

Akihiro


2016-03-21 22:40 GMT+09:00 Andreas Jaeger <aj at suse.com>:
> On 2016-03-21 14:07, Akihiro Motoki wrote:
>> The release management team has changed the process of generating
>> releases notes for Mitaka.
>> Release notes are generated from YAML files in individual repos by using reno.
>>
>> My understanding is that we don't have translation support for Mitaka
>> release notes.
>> Is it correct?
>
> Yes.
>
>> After checking the meeting minutes, I found Kato has an action item
>> to talk about it with the relmgt team. is there any feedback?
>
> There was an email by Doug Hellmann that translation of release notes is
> one of his goals for the Newton release cycle. I quickly found his
> statement as PTL:
>
> https://review.openstack.org/#/c/291778/1/candidates/newton/Release_Management/Doug_Hellmann.txt
>
>> Personally I am okay with it. I am always using English release notes :-)
>> I am translating release notes only for reading them carefully and
>> better understanding of the release.
>
> 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
>