Commit 3a6f9ea4 authored by intrigeri's avatar intrigeri
Browse files

Release process: clarify when (and why) to update our bundled packages.

It would really be sad to ignore the translation work done between the RC and
the final release, after we've specifically asked translators to do it
at RC time.
parent 7ddf4fa9
...@@ -176,11 +176,18 @@ The patterns+settings file is stored as a SQLite text dump in ...@@ -176,11 +176,18 @@ The patterns+settings file is stored as a SQLite text dump in
Upgrade bundled binary Debian packages Upgrade bundled binary Debian packages
-------------------------------------- --------------------------------------
Skip this section unless we are at freeze time for a major release Skip this section if you are preparing a point-release.
(i.e. we are about to prepare a release candidate).
The goal here is to make sure the bundled binary Debian packages contain
That is: make sure the bundled binary Debian packages contain up-to-date localization files, so:
up-to-date localization files.
- If you are preparing a release candidate, build at least the packages
that change user-visible strings, so that translators can use the RC
to check the status of their work and identify what's left to do.
- If you are preparing a major release, build at least the packages
that got translation updates since the RC: we've sent a call for
translation while releasing the RC so the least we can do is to
incorporate the work that ensued into our final release :)
For each bundled Debian package, `cd` into the package's root For each bundled Debian package, `cd` into the package's root
directory (e.g. a checkout of the `whisperback` repository), directory (e.g. a checkout of the `whisperback` repository),
......
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment