From 1d9dcc59e755310a5067a80b5327179eb098a766 Mon Sep 17 00:00:00 2001 From: "Ian Y. Choi" Date: Sat, 14 Jan 2017 14:09:33 +0000 Subject: [PATCH] Refines with details on activities with releases - Changes the title, since the title "Release Management" might infer Release Management team and their activities - Adds detail introduction why the activities in this document is important with releases - Light style adjustment for better rendering into HTML Change-Id: I4ea05bbf0033e5f7e22c7537c908a05a84bc412e --- doc/source/release_management.rst | 58 ++++++++++++++++++++----------- 1 file changed, 38 insertions(+), 20 deletions(-) diff --git a/doc/source/release_management.rst b/doc/source/release_management.rst index 5e6f442..de5f755 100644 --- a/doc/source/release_management.rst +++ b/doc/source/release_management.rst @@ -1,51 +1,69 @@ -================== -Release management -================== +============================ +Team activities with release +============================ -This page documents what the i18n team and teams concerned needs to do around -OpenStack releases. +This page documents what I18n team concerns and which things are needed +to do with OpenStack releases. Each OpenStack release has around 6-month cycle +and the corresponding schedule is available on https://releases.openstack.org/ +(e.g., https://releases.openstack.org/ocata/schedule.html describes Ocata +release schedule). -#. (Project) Release milestone-3. "Soft StringFreeze" is in effect. -#. (Translator) Start translations for the release. +One of main goals in I18n team is to incorporate translated strings into a new +release so that more global users experience translated version of OpenStack. +To accomplish this goal, some of team activities need to be aligned +with a release schedule. + +.. note:: + + I18n team sets target projects to be translated and prioritizes + during around the Forum (renamed from the Design Summit). + Current translation plan and priority are available on + `translation dashboard `_. + +.. note:: + + The terms in this page follows release schedule pages. + +#. [Project] Release milestone-3. ``Soft StringFreeze`` is in effect. +#. [Translator] Start translations for the release. * Translate **master** version on Zanata. -#. (I18n PTL) Call for translation +#. [I18n PTL] Call for translation -#. (I18n PTL) Coordinate release and translation import schedule of individual +#. [I18n PTL] Coordinate release and translation import schedule of individual projects with PTL or I18n liaison. -#. (Project) Release RC1 and create a stable branch. - "Hard StringFreeze" is in effect. +#. [Project] Release RC1 and create a stable branch. + ``Hard StringFreeze`` is in effect. -#. (Zanata admin) Create a stable version such as ``stable-newton`` +#. [Zanata admin] Create a stable version such as ``stable-newton`` * The stable version is created from the master version on Zanata once RC1 is cut and a stable branch is created in a git repository. * Once a stable version corresponding to a project stable branch is created on Zanata, the infra script will push strings automatically. -#. (Translator) Translate **stable-XXXX** version instead of master version +#. [Translator] Translate **stable-XXXX** version instead of master version on Zanata. * At this stage, the master version on Zanata is still open for translations, but it is strongly suggested to work on a stable version. -#. (Infra) Setup translation jobs such as ``translation-jobs-newton`` +#. [Infra] Setup translation jobs such as ``translation-jobs-newton`` to import translations for stable branches. * This should be done after a stable version on Zanata is created. -#. (Translator) It is suggested to complete translation work by Monday or - Tuesday of the Final RC week. For more detail schedule, - check http://releases.openstack.org/ . +#. [Translator] It is suggested to complete translation work by Monday or + Tuesday of the Final RC week. -#. (Project) RC2 or RC3 release will be shipped with latest translations. +#. [Project] RC2 or RC3 release will be shipped with latest translations. Final RC release will happen one week before the official release week. -#. (Project) Official release! +#. [Project] Official release! -#. (Zanata admin) Merge a stable version back into the master version. +#. [Zanata admin] Merge a stable version back into the master version. * This usually happens within a week after the release. * The stable version is well reviewed, so it makes sense to merge