openstack
/
i18n
Code Issues Proposed changes

[Docs] Update release management part 

- Reflects that now stable versions are created after release
  without early creation of the versions and merging to master
- cycle-with-milestones has been replaced by cycle-with-rc model
- Horizon is now following cycle-with-intermediary.
  Let's follow the same description as project-team-guide/release-management.
- Replace a term: from Forum/Design Summit to PTG

Change-Id: Id0ca964786a4a9cf2287b008d845f4c3a1a22e77
This commit is contained in:
Ian Y. Choi 2023-09-03 01:45:52 +09:00
parent 5a846dbd43
commit 990d2bbe9d
1 changed files with 14 additions and 25 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

39
doc/source/release_management.rst
View File

@ -16,19 +16,23 @@ with a release schedule.
.. note::
I18n team sets target projects to be translated and prioritizes
during around the Forum (renamed from the Design Summit).
during around the `PTG <https://openinfra.dev/ptg/>`_.
Current translation plan and priority are available on
`translation dashboard <https://translate.openstack.org/>`_.
.. note::
The terms in this page follow release schedule pages.
You can see how OpenStack project teams product artifacts with release
management on `Release Management <https://docs.openstack.org/project-team-guide/release-management.html>`_
document.
Projects affecting StringFreezes
--------------------------------
Horizon and Horizon plugins are the main targets which affect StringFreezes.
Note that StringFreezes are applied to ``cycle-with-milestone`` release model.
Note that StringFreezes are applied to I18n team target projects and with
``cycle-with-rc`` or ``cycle-with-intermediary`` release model.
#. [Project] Release milestone-3. ``Soft StringFreeze`` is in effect.
#. [Translator] Start translations for the release.
@ -43,38 +47,23 @@ Note that StringFreezes are applied to ``cycle-with-milestone`` release model.
#. [Project] Release RC1 and create a stable branch.
``Hard StringFreeze`` is in effect.
#. [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
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``
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.
* It is encouraged to share translation progress with I18n team and/or
corresponding project team(s) to make sure shipping the translation.
#. [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!
#. [Zanata admin] Merge a stable version back into the master version.
#. [Zanata admin] Create a stable version after release.
* This usually happens within a week after the release.
* The stable version is well reviewed, so it makes sense to merge
translations into the master version on Zanata to avoid translating the
same strings again.
#. [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.
#. After the official release, translating master version is welcome
for upstream translation contribution, but the original strings may be