Open Stack

On 2016-03-22 09:22, Akihiro Motoki wrote:
> 2016-03-22 14:01 GMT+09:00 Ian Y. Choi <ianyrchoi at gmail.com>:
>> Hello,
>>
>> IMO translations for release notes are helpful for local group people, so
>> I subscribed 'Release notes translation' on i18n launchpad a few months ago
>> :)
>> :
>> https://blueprints.launchpad.net/openstack-i18n/+spec/release-notes-translation
>>
>> I have a question on http://releases.openstack.org/<lang> ,
>> which may be used later after translating all release notes on many
>> OpenStack projects.
>> After translating releasenotes on each project (e.g., nova, horizon),
>> a new commit will be made including a commit like 'Import Zanata
>> translation'.
>>
>> Then, do we need to also change the commit hash values on releases
>> repository,
>> like
>> http://git.openstack.org/cgit/openstack/releases/tree/deliverables/mitaka/horizon.yaml
>> ,
>> every time Zanata imports?

No, I don't think so. We just publish from that branch.

BUT I think this whole approach needs a good design so that we're all on
the same page.

That one can then be the basis for a spec,either an infra spec - if this
is mainly infra changes - or a cross-project spec.

I suggest to have a session in Austin about this together with the
release management team, let me CC Doug for this.

> All reno release notes are generated from the head of the master branch.
> We may need to make some change to reno, but generally speaking
> you don't need to update release hashes you quoted above.

Agreed,

Andreas

>>
>> I think translations on releases.openstack.org would be the next procedures,
>> but frequent change on commit hash values for translated release notes would
>> not be good idea.
>> So I think, for release notes, higher threshold (e.g., =100%, <95%) would be
>> nice idea I think.
> 
> I think >=90% (per release) is fair enough.
> I assume mitaka.po, liberty.po and so on.
> 
> Akihiro
> 
>>
>>
>> With many thanks,
>>
>> /Ian
>>
>>
>>
>> KATO Tomoyuki wrote on 3/22/2016 1:28 PM:
>>>
>>> Hi Akihiro,
>>>
>>> Just a my "current" consideration inline.
>>>
>>>> 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.)
>>>
>>> +1
>>>
>>>> * How and where to publish translated release notes
>>>
>>> publish as regular translation jobs, like docs.
>>> http://docs.openstack.org/releasenotes/<project>/<lang>
>>>
>>>> * Where to have locale files in each project tree
>>>
>>> /releasenotes/source/locale/<lang>
>>>
>>>> * 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)
>>>
>>> include current translation import job.
>>>
>>> Thanks,
>>> Kato
>>>
>>>> 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
>>>>>
>>>> _______________________________________________
>>>> Openstack-i18n mailing list
>>>> Openstack-i18n at lists.openstack.org
>>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> Openstack-i18n mailing list
>>>> Openstack-i18n at lists.openstack.org
>>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n
>>
>>
>>
>> _______________________________________________
>> Openstack-i18n mailing list
>> Openstack-i18n at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n
> 
> _______________________________________________
> Openstack-i18n mailing list
> Openstack-i18n at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n
> 


-- 
 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