Open Stack

I will prepare patches to add locale_dirs for major server projects.

Regarding the script by Andreas (https://review.openstack.org/#/c/372167/),
I think it is better to check if releasenotes/source/conf.py has
locale_dirs definition.
Otherwise generated release notes are completely meaningless.
We can also propose a change to add 'locale_dir' to individual projects
gradually and as we need.


2016-10-07 0:59 GMT+09:00 Akihiro Motoki <amotoki at gmail.com>:

> Some update on release note translations.
>
> It is a good news.
> I found releasenotes/source/conf.py files in most projects do not define
> locale_dirs.
> After I added locale_dirs = ['locale/'] to horizon
> releasenotes/source/conf.py,
> I succeeded to generate translated version of release notes :)
> I manually followed the proposed script by Andreas.
>
> I checked most core service projects and openstack-manuals and
> it turns out openstack-manuals is the only project which defines
> locale_dirs in releasenotes/source/conf.py.
>
> I believe this is the reason we failed to get translated release notes
> when we tried before.
>
> Akihiro
>
>
>
> 2016-09-20 2:17 GMT+09:00 Doug Hellmann <doug at doughellmann.com>:
>
>>
>> > 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.
>>
>> 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
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-i18n/attachments/20161007/d41a1fcc/attachment.html>