Stop Sent from my iPad
On 17 Sep 2016, at 13:00, openstack-i18n-request@lists.openstack.org wrote:
Send OpenStack-I18n mailing list submissions to openstack-i18n@lists.openstack.org
To subscribe or unsubscribe via the World Wide Web, visit http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n or, via email, send a message with subject or body 'help' to openstack-i18n-request@lists.openstack.org
You can reach the person managing the list at openstack-i18n-owner@lists.openstack.org
When replying, please edit your Subject line so it is more specific than "Re: Contents of OpenStack-I18n digest..."
Today's Topics:
1. Re: First stable/newton branches created (Akihiro Motoki) 2. Re: First stable/newton branches created (Andreas Jaeger) 3. [String freeze exception] Horizon https://review.openstack.org/#/c/371907/ (Akihiro Motoki)
----------------------------------------------------------------------
Message: 1 Date: Fri, 16 Sep 2016 23:42:32 +0900 From: Akihiro Motoki <amotoki@gmail.com> To: "Kato, Tomoyuki" <kato.tomoyuki@jp.fujitsu.com> Cc: Andreas Jaeger <aj@suse.com>, "openstack-i18n@lists.openstack.org" <openstack-i18n@lists.openstack.org> Subject: Re: [OpenStack-I18n] First stable/newton branches created Message-ID: <CALhU9tk1OnDZ7H+HTqrFG=CJh4EZ2_nvX5iadEMgzQWpzbJ+5A@mail.gmail.com> Content-Type: text/plain; charset="utf-8"
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