First stable/newton branches created
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 -- 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
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? 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].) 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/openstac... [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 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
Hi Ian, 2016-09-16 9:54 GMT+09:00 Ian Y. Choi <ianyrchoi@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) 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).
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/openstac... [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:%255Edelive... [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@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n
On 09/16/2016 04:30 AM, Akihiro Motoki wrote:
Hi Ian,
2016-09-16 9:54 GMT+09:00 Ian Y. Choi <ianyrchoi@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/openstac... [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:%255Edelive... [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@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
Thanks Andreas for the info. Kato-san, could you take care of it? You can do it yourself or delegate it to someone else, but it is better to do it soon. Otherwise master and stable-newton will be diverged.
Syncing to Zanata works automatically if there is a stable-newton (note the "-", Zanata does not allow "/"!) branch.
That's what was unclear to me. Thanks. So, the question now is who creates stable-newton version in Zanata. I think only the limited folks can do that. Perhaps Daisy, Kato-san, Andreas? In addition to the permission, the tips on creating a Zanata version has not been shared. Akihiro 2016-09-16 14:32 GMT+09:00 Andreas Jaeger <aj@suse.com>:
On 09/16/2016 04:30 AM, Akihiro Motoki wrote:
Hi Ian,
2016-09-16 9:54 GMT+09:00 Ian Y. Choi <ianyrchoi@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/openstac... [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:%255Edelive... [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@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
Thanks a lot for kind explanation, Andreas and Akihiro-san.
Please see the inline for my several thoughts:
Akihiro Motoki wrote on 9/16/2016 5:19 PM:
> Thanks Andreas for the info.
>
> Kato-san, could you take care of it?
> You can do it yourself or delegate it to someone else,
> but it is better to do it soon. Otherwise master and stable-newton
> will be diverged.
+1 :)
And according to one previous e-mail:
http://lists.openstack.org/pipermail/openstack-i18n/2016-March/001984.html ,
Horizon and its related projects, and server projects are the main
targets to create "stable-newton" version in Zanata.
>> Syncing to Zanata works automatically if there is a stable-newton (note
>> the "-", Zanata does not allow "/"!) branch.
> That's what was unclear to me. Thanks.
> So, the question now is who creates stable-newton version in Zanata.
> I think only the limited folks can do that. Perhaps Daisy, Kato-san, Andreas?
When I see 'maintainers' part in Zanata, "infra" account is the manager
for all projects,
like: https://translate.openstack.org/project/view/horizon/maintainers .
So it may be Zanata "infra" account? And I think Zanata team members
(Alex, Carlos) might know the privilege.
With many thanks,
/Ian
> In addition to the permission, the tips on creating a Zanata version
> has not been shared.
>
> Akihiro
>
> 2016-09-16 14:32 GMT+09:00 Andreas Jaeger <aj@suse.com>:
>> On 09/16/2016 04:30 AM, Akihiro Motoki wrote:
>>> Hi Ian,
>>>
>>> 2016-09-16 9:54 GMT+09:00 Ian Y. Choi <ianyrchoi@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@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
>>
On 09/16/2016 11:05 AM, Ian Y. Choi wrote:
Thanks a lot for kind explanation, Andreas and Akihiro-san.
Please see the inline for my several thoughts:
Akihiro Motoki wrote on 9/16/2016 5:19 PM:
Thanks Andreas for the info.
Kato-san, could you take care of it? You can do it yourself or delegate it to someone else, but it is better to do it soon. Otherwise master and stable-newton will be diverged. +1 :)
And according to one previous e-mail: http://lists.openstack.org/pipermail/openstack-i18n/2016-March/001984.html , Horizon and its related projects, and server projects are the main targets to create "stable-newton" version in Zanata.
Syncing to Zanata works automatically if there is a stable-newton (note the "-", Zanata does not allow "/"!) branch. That's what was unclear to me. Thanks. So, the question now is who creates stable-newton version in Zanata. I think only the limited folks can do that. Perhaps Daisy, Kato-san, Andreas? When I see 'maintainers' part in Zanata, "infra" account is the manager for all projects, like: https://translate.openstack.org/project/view/horizon/maintainers .
So it may be Zanata "infra" account? And I think Zanata team members (Alex, Carlos) might know the privilege.
Daisy, Kato-san, and myself are admins and have these permissions. I just setup horizon as first project but won't have time to do them all... Andreas -- 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
https://review.openstack.org/371397 is the initial project-config change to import stable/newton from horizon. Once additional projects have their versions in zanata, they should get the same jobs as horizon. Akihiro-san, will you do that? Andreas -- 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
Thanks Andreas for the info.
Kato-san, could you take care of it? You can do it yourself or delegate it to someone else, but it is better to do it soon. Otherwise master and stable-newton will be diverged.
Sorry for late response. I wiil work on it from now. KATO Tomoyuki
Syncing to Zanata works automatically if there is a stable-newton (note the "-", Zanata does not allow "/"!) branch.
That's what was unclear to me. Thanks. So, the question now is who creates stable-newton version in Zanata. I think only the limited folks can do that. Perhaps Daisy, Kato-san, Andreas? In addition to the permission, the tips on creating a Zanata version has not been shared.
Akihiro
2016-09-16 14:32 GMT+09:00 Andreas Jaeger <aj@suse.com>:
On 09/16/2016 04:30 AM, Akihiro Motoki wrote:
Hi Ian,
2016-09-16 9:54 GMT+09:00 Ian Y. Choi <ianyrchoi@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/openstac... [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:%255Edelive... [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@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
2016年9月16日金曜日、Kato, Tomoyuki<kato.tomoyuki@jp.fujitsu.com>さんは書きました:
Thanks Andreas for the info.
Kato-san, could you take care of it? You can do it yourself or delegate it to someone else, but it is better to do it soon. Otherwise master and stable-newton will be diverged.
Sorry for late response. I wiil work on it from now.
No problem. I can help additional prpject branching. We were just discussing what we can, Thanks formyour help.
KATO Tomoyuki
Syncing to Zanata works automatically if there is a stable-newton (note the "-", Zanata does not allow "/"!) branch.
That's what was unclear to me. Thanks. So, the question now is who creates stable-newton version in Zanata. I think only the limited folks can do that. Perhaps Daisy, Kato-san,
In addition to the permission, the tips on creating a Zanata version has not been shared.
Akihiro
2016-09-16 14:32 GMT+09:00 Andreas Jaeger <aj@suse.com <javascript:;>>:
On 09/16/2016 04:30 AM, Akihiro Motoki wrote:
Hi Ian,
2016-09-16 9:54 GMT+09:00 Ian Y. Choi <ianyrchoi@gmail.com <javascript:;>>:
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
even though most of the i18n team focus on horizon related
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+
[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
Andreas? projects, translations. path:%255Edeliverables/newton/.* 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@lists.openstack.org <javascript:;> 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
On 09/16/2016 02:54 AM, Ian Y. Choi wrote:
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?
Master branches of nova and other projects - see all the announcements yesterday on openstack-dev - are now Ocata! So, we have to create them now.
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].) Or should we start gradually the projects merged with "topic:create-[release name]" patches, like [4]?
Yes, those should be enabled (if you want to translate them) - these are the ones I'm talking about. Btw. note that release-notes are generated only on master, do not translate them in stable branches! Andreas
[1] http://eavesdrop.openstack.org/meetings/openstack_i18n_meeting/2016/openstac...
[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
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
-- 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
Job to sync translated projects: https://review.openstack.org/#/c/365872/ Please review - and if I missed some repos, create a new change, Andreas -- 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
On 2016-09-16 17:45, Andreas Jaeger wrote:
Job to sync translated projects:
https://review.openstack.org/#/c/365872/
Please review - and if I missed some repos, create a new change,
I noticed that more projects have stable-newton branches in Zanata then those that I added - and thus far more than are mentioned on the front page. Do you really want to allow translation of all of these - or focus like it's written on the Zanata front page and as Ian states in "To language team coordinators: Let's speed up for Newton translation" on a few Horizon projects? I suggest to focus and remove stable-newton branch from those projects you're not handling. Should that list be the list of repos I enabled in infra? Or only the dashboard ones? So, basically, what I'd like to know: * Which projects should have stable-newton in Zanata? * Which should be synced to git (IMHO the same ones)? * Do you want to point out further repos besides the dashboard ones? If yes, how? 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
Job to sync translated projects:
https://review.openstack.org/#/c/365872/
Please review - and if I missed some repos, create a new change, I noticed that more projects have stable-newton branches in Zanata then
On 2016-09-16 17:45, Andreas Jaeger wrote: those that I added - and thus far more than are mentioned on the front page.
Do you really want to allow translation of all of these - or focus like it's written on the Zanata front page and as Ian states in "To language team coordinators: Let's speed up for Newton translation" on a few Horizon projects?
I suggest to focus and remove stable-newton branch from those projects you're not handling.
Should that list be the list of repos I enabled in infra? Or only the dashboard ones?
So, basically, what I'd like to know: * Which projects should have stable-newton in Zanata? That is why I intended first to check whether there will be more IBM
Hello, Actually I do not know exactly how I see a list of stable/newton versions in Zanata. (Should I click all the projects and check corresponding versions currently?) But yes, there are also many server-side projects, such as nova and neutron. Andreas Jaeger wrote on 9/19/2016 9:07 PM: translations or not, since IBM contributed translations on server-side projects a lot. As http://lists.openstack.org/pipermail/openstack-dev/2015-September/073942.htm... shared about one year ago, and at Austin I18n meetup, server-side projects were not included in our priority. ( Austin I18n meetup Etherpad: https://etherpad.openstack.org/p/austin-i18n-meetup ) Non-prioritizing would mean non-consideration of stable/newton branches for server projects in Zanata? I do not clearly remember it, but if it is okay, currently I am okay to remove those projects which are not handled. But still, I would like to know to IBM's translation contribution plan, and also listen to language coordinators and translators by this mailing list or later I18n IRC meeting. For documentation projects (e.g., openstack-manuals), creating stable versions after release data is needed.
* Which should be synced to git (IMHO the same ones)? IMO same as the 1st * Do you want to point out further repos besides the dashboard ones? If yes, how? I think current decision for Newton is up to Kato-san, since he is now Newton PTL :) Kato-san, do you have idea on that?
And of course, I really want to point out documentation projects for stable/newton branch after the release date during Ocata cycle. With many thanks, /Ian
Andreas
On 09/19/2016 06:15 PM, Ian Y. Choi wrote:
Hello,
Actually I do not know exactly how I see a list of stable/newton versions in Zanata. (Should I click all the projects and check corresponding versions currently?)
Yes, that's the only way ;(
But yes, there are also many server-side projects, such as nova and neutron.
Exactly - and for those I've setup the sync.
Job to sync translated projects:
https://review.openstack.org/#/c/365872/
Please review - and if I missed some repos, create a new change, I noticed that more projects have stable-newton branches in Zanata then
On 2016-09-16 17:45, Andreas Jaeger wrote: those that I added - and thus far more than are mentioned on the front page.
Do you really want to allow translation of all of these - or focus like it's written on the Zanata front page and as Ian states in "To language team coordinators: Let's speed up for Newton translation" on a few Horizon projects?
I suggest to focus and remove stable-newton branch from those projects you're not handling.
Should that list be the list of repos I enabled in infra? Or only the dashboard ones?
So, basically, what I'd like to know: * Which projects should have stable-newton in Zanata? That is why I intended first to check whether there will be more IBM
Andreas Jaeger wrote on 9/19/2016 9:07 PM: translations or not, since IBM contributed translations on server-side projects a lot.
As http://lists.openstack.org/pipermail/openstack-dev/2015-September/073942.htm... shared about one year ago, and at Austin I18n meetup, server-side projects were not included in our priority. ( Austin I18n meetup Etherpad: https://etherpad.openstack.org/p/austin-i18n-meetup )
Those were done in the past and if you change it, you should tell the server side projects and release team. They might expect it. Personally, I would focus on user side content: Dashboards, openstackclient, documentation - and then comes server side projects - but your call. I just ask for proper communication.
Non-prioritizing would mean non-consideration of stable/newton branches for server projects in Zanata?
You could leave them in case somebody wants to translate them - or remove them completely.
I do not clearly remember it, but if it is okay, currently I am okay to remove those projects which are not handled.
But still, I would like to know to IBM's translation contribution plan, and also listen to language coordinators and translators by this mailing list or later I18n IRC meeting.
IBM translated some server projects.
For documentation projects (e.g., openstack-manuals), creating stable versions after release data is needed.
Yes, indeed. openstack-manuals has not branched yet.
* Which should be synced to git (IMHO the same ones)? IMO same as the 1st * Do you want to point out further repos besides the dashboard ones? If yes, how? I think current decision for Newton is up to Kato-san, since he is now Newton PTL :) Kato-san, do you have idea on that?
And of course, I really want to point out documentation projects for stable/newton branch after the release date during Ocata cycle.
Andreas -- 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
participants (4)
-
Akihiro Motoki
-
Andreas Jaeger
-
Ian Y. Choi
-
Kato, Tomoyuki