Merilis Weblate

Siklus rilis

Weblate uses calendar versioning with monthly releases. The version format is <YEAR>.<MONTH>.<PATCH> with a numeric, non-zero-padded month. The <PATCH> part is omitted for the first release in a month when it would be 0, for example 2026.5. Patch releases use the full version number, for example 2026.5.1.

Monthly releases are usually published at the beginning of the month. Patch releases include bug fixes, security fixes, and dependency updates which should not wait for the next monthly release.

Direct upgrades are supported from releases in the current or previous calendar year. The first release in a new year drops direct upgrade support for releases from the year before the previous year.

The Docker container includes an additional version component to track changes in the container itself, such as dependencies. Fixed Docker image tags include the patch component together with this build component, even when the Weblate version omits a 0 patch component. These updates may include security updates.

Lihat juga

Perencanaan rilis

Fitur untuk rilis mendatang dikumpulkan menggunakan tonggak GitHub, Anda dapat melihat peta jalan kami di <https://github.com/WeblateOrg/weblate/milestones>.

Proses rilis

Hal yang perlu diperiksa sebelum rilis:

  1. Periksa bahasa yang baru diterjemahkan dengan ./scripts/list-translated-languages.py.

  2. Atur versi final dengan ./scripts/prepare-release.

  3. Pastikan tangkapan layar sudah diperbarui make -j 12 -C docs update-screenshots.

  4. Gabungkan semua terjemahan yang mungkin tertunda wlc push; git remote update; git merge origin/weblate

When building distribution packages locally, start from a clean checkout or remove ignored packaging artifacts such as build/, dist/, weblate.egg-info/, and generated weblate/locale/**/*.mo files.

Lakukan perilisan:

  1. Buat rilis ./scripts/create-release --tag (lihat di bawah untuk persyaratannya).

Langkah manual pasca rilis:

  1. Tutup tonggak GitHub.

  2. Setelah gambar Docker diuji, tambahkan tag dan dorong.

  3. Sertakan versi baru dalam .github/workflows/migrations.yml untuk mencakupnya dalam pengujian migrasi.

  4. Tingkatkan versi dalam repositori dengan ./scripts/set-version.py.

  5. Periksa apakah readthedocs.org telah membuat semua terjemahan dokumentasi menggunakan ./scripts/rtd-projects.py.

Untuk membuat tag menggunakan skrip ./scripts/create-release Anda memerlukan hal berikut:

  • Akses dorong ke repositori git Weblate (mendorong tag)