Open Stack

On 09/16/2016 04:30 AM, Akihiro Motoki wrote:
> Hi Ian,
> 
> 2016-09-16 9:54 GMT+09:00 Ian Y. Choi <ianyrchoi at gmail.com>:
>> Hello Andreas and i18n team members,
>>
>> Yesterday (according to UTC), Kato-san and me discussed this topic in IRC
>> meeting [1],
>>     but we are not sure when we will have stable-newton branch.
>> I think it is time to create stable-newton branch now and Kato-san will deal
>> with,
>> but I would like to ask some details to clarify the best timing of creating
>> a stable branch.
>>
>> When should i18n team create a stable branch (e.g., stable-newton) in
>> Zanata?
> 
> Although I am not familiar with Zanata operations, I think the i18n
> team needs to
> create 'stable-newton' version by branching 'master' version in Zanata
> to inherit
> translation works made in the master version so far.
> 
> In my understanding, what we need to do are:
> (a) create stable-newton version in Zanata from master version -> i18n team
> (b) release RC1 deliverables and create stable/newton branch in git
> repositories -> each project team and release team
> (c) set up project-config to sync repositories and translations for
> stable/newton -> infra team (I can as well)

Syncing to Zanata works automatically if there is a stable-newton (note
the "-", Zanata does not allow "/"!) branch. Importing into
stable/newton needs project-config changes. If you would do that, it
would be great!


> There is no strict relationship between (a) and (b), and either of
> them can happen first.
> If the timing of (a) and (b) are closer, most translation work in
> 'master' in Zanata are copied into 'stable-newton' version.
> (c) needs to be done after both (a) and (b).

Indeed,

Andreas

>> I thought just after from "Hard StringFreeze" in [2] would be the right
>> time,
>> or checking at least Horizon development status (since the focus of i18n
>> team now is Horizon related projects)
>> would be needed. (Previously we had I18n cross project liaisons [3].)
> 
> To be honest, RC1 release means 'Hard String Freeze'. That's all.
> We can know RC1 release notices by various ways:
> - checking release announcements,
> - checking openstack/releases reviews [5],
> - checking releases.openstack.org [6]
> 
> I think we should prepare stable-newton version in Zanata for all projects,
> even though most of the i18n team focus on horizon related translations.
> 
> I am not sure i18n liaisons for horizon related projects work in this cycle.
> We have sent no reminder for i18n liaisons...
> In the previous release, I took care of horizon related projects but
> it is beyond
> the role of horizon-i18n liaison and I am not taking care of them
> (except horizon itself).
> 
> Horizon RC1 will be shipped in several hours. The team is preparing
> the release now.
> 
>> Or should we start gradually the projects merged with "topic:create-[release
>> name]" patches, like [4]?
>>
>> [1]
>> http://eavesdrop.openstack.org/meetings/openstack_i18n_meeting/2016/openstack_i18n_meeting.2016-09-15-13.03.html
>> [2] https://releases.openstack.org/newton/schedule.html
>> [3] https://wiki.openstack.org/wiki/CrossProjectLiaisons#I18n
>> [4] https://review.openstack.org/#/q/topic:create-newton
> 
> [5] https://review.openstack.org/#/q/project:openstack/releases+path:%255Edeliverables/newton/.*
> [6] https://releases.openstack.org/newton/index.html
> 
> Thanks,
> Akihiro
> 
>>
>>
>> With many thanks,
>>
>> /Ian
>>
>> Andreas Jaeger wrote on 9/16/2016 3:35 AM:
>>>
>>> Could somebody please set up stable-newton branches for those projects
>>> that should get translations of them, please?
>>>
>>> With RC1 today, projects are creating stable/newton branches now,
>>>
>>> Andreas
>>
>>
>>
>>
>> _______________________________________________
>> 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/Identica: 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