From cfd919ffa8e5090208670476f8b47b2a9d8a5b7a Mon Sep 17 00:00:00 2001 From: Ngo Quoc Dat Date: Wed, 18 Nov 2026 01:04:34 +0700 Subject: [PATCH] docs(linux): check translations before a release PR and tag a commit from the release date --- linux/docs/releasing.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/linux/docs/releasing.md b/linux/docs/releasing.md index 4935b6a467..c491893ffd 100644 --- a/linux/docs/releasing.md +++ b/linux/docs/releasing.md @@ -103,8 +103,8 @@ The tag publishes what this run built and tested, and builds none of it again ([ - A release only: the version's section in `CHANGELOG.md`, from the fragments in `changelog.d/`. From the repository root, with the towncrier venv of the root `RELEASING.md`, Notes: `.venv/bin/towncrier build --dir linux --version X.Y.Z --date YYYY-MM-DD --yes`. It deletes the fragments and stages `CHANGELOG.md`. An X.Y.0 types its lead under the heading, at most 6 plain lines naming what a reader would change their behavior over. A beta adds no section and keeps the fragments, so the release lists them; its notes are a towncrier draft of the fragments at the tag. - The `.TH` line of `data/tablepro.1`: the date and `TablePro` with the version as `meson.build` has it. - The pull request changes only these files and `changelog.d/`. The `release-metadata` Meson test checks that they agree from the commit that sets a beta's version, or adds a release's changelog heading, so the pull request fails before the tag does. -2. **The tag**: `linux-vX.Y.Z` or `linux-vX.Y.Z-beta.N` on the merged commit, after its green dry run, pushed the same UTC day. The workflow compares the metainfo date with the commit date. Tags run one at a time, and a tag pushed while another waits cancels that one, so push a tag when no other release run is waiting. + The pull request changes only these files and `changelog.d/`. The `release-metadata` Meson test checks that they agree from the commit that sets a beta's version, or adds a release's changelog heading, so the pull request fails before the tag does. Pull request CI does not block an untranslated string, while the dry run's Translation template job does: check the shipped catalogues against the template before opening the pull request. Merge it on the date it sets, in UTC; the dry run takes about four and a half hours, so a date of tomorrow means merging after midnight UTC. +2. **The tag**: `linux-vX.Y.Z` or `linux-vX.Y.Z-beta.N` on the merged commit, after its green dry run, pushed the same UTC day. The workflow compares the metainfo date with the committer date of the tagged commit; when the release commit landed a day early, tag a later commit on `main` from the right day instead, after its own dry run. Tags run one at a time, and a tag pushed while another waits cancels that one, so push a tag when no other release run is waiting. 3. **The workflow** checks the tag and takes the tarballs, template, source packages, packages and unsigned Flatpak repositories from the [dry run](#a-dry-run) of its commit, or fails before it publishes anything when there is none. It pulls the published Flatpak repository from R2, signs the new commits into it and bundles them, and checks that every file but the bundles matches the dry run's `SHA256SUMS`. It attests every file, publishes the packages and bundles on GitHub with the tarballs, the translation template `tablepro.pot`, `SHA256SUMS`, and the version's changelog section as notes, a beta as a pre-release, and checks what the release then serves against `SHA256SUMS`. Then it uploads the Flatpak repository to R2, the signed source package to the PPA, and posts the tag to the COPR project: the stable ones for a release, the beta ones for a beta. A reviewer approves each step that uses the environment. 4. **Afterwards**: watch the Launchpad build page of each series and the COPR build the workflow prints. A failed build there does not fail the workflow. `flatpak remote-info` on the TablePro remote shows the new Flatpak commit.