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.
The features for upcoming releases are collected using GitHub milestones, you can see our roadmap at <https://github.com/WeblateOrg/weblate/milestones>.
Things to check prior to release:
Check newly translated languages by ./scripts/list-translated-languages.
Set final version by ./scripts/prepare-release.
Make sure screenshots are up to date make -j 12 -C docs update-screenshots.
Merge any possibly pending translations wlc push; git remote update; git merge origin/weblate
Create a release ./scripts/create-release --tag (see below for requirements).
Ręczne kroki po wydaniu:
Zamknij kamień milowy GitHub.
Once the Docker image is tested, add a tag and push it.
Include new version in
.github/workflows/migrations.ymlto cover it in migration testing.
Increase version in the repository by ./scripts/set-version.
Check that readthedocs.org did build all translations of the documentation using ./scripts/rtd-projects.
To create tags using the ./scripts/create-release script you will need following:
Push access to Weblate git repositories (it pushes tags)