weblate/docs/contributing/release.rst
Michal Čihař 218b49d8c8 scripts: remove release publishing from create-release
This is now done by GitHub action.
2024-02-12 15:31:31 +01:00

49 lines
1.7 KiB
ReStructuredText

Releasing Weblate
=================
Releasing schedule
------------------
Weblate has two month release cycle for releases (x.y). These are usually
followed by a bunch of bugfix releases to fix issues which slip into them
(x.y.z).
The change in the major version indicates that the upgrade process can not skip
this version - you always have to upgrade to x.0 before upgrading to higher x.y
releases.
.. seealso::
:doc:`../admin/upgrade`
Release planning
----------------
The features for upcoming releases are collected using GitHub milestones, you
can see our roadmap at <https://github.com/WeblateOrg/weblate/milestones>.
Release process
---------------
Things to check prior to release:
1. Check newly translated languages by :command:`./scripts/list-translated-languages`.
2. Set final version by :command:`./scripts/prepare-release`.
3. Make sure screenshots are up to date :command:`make -j 12 -C docs update-screenshots`.
4. Merge any possibly pending translations :command:`wlc push; git remote update; git merge origin/weblate`
Perform the release:
5. Create a release :command:`./scripts/create-release --tag` (see below for requirements).
Post release manual steps:
6. Close GitHub milestone.
7. Once the Docker image is tested, add a tag and push it.
8. Include new version in :file:`.github/workflows/migrations.yml` to cover it in migration testing.
9. Increase version in the repository by :command:`./scripts/set-version`.
10. Check that readthedocs.org did build all translations of the documentation using :command:`./scripts/rtd-projects`.
To create tags using the :command:`./scripts/create-release` script you will need following:
* Push access to Weblate git repositories (it pushes tags)