From d7f3ce12178e72b985c16ce25e12ecbf98744132 Mon Sep 17 00:00:00 2001 From: Allan McRae Date: Mon, 4 Mar 2024 13:32:14 +1000 Subject: [PATCH] Manage releases through gitlab Also provide an example for how to check for errors in translations Signed-off-by: Allan McRae --- RELEASE | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/RELEASE b/RELEASE index c3fe63b0..48be61a1 100644 --- a/RELEASE +++ b/RELEASE @@ -11,12 +11,14 @@ The following checklist should be used for making a pacman release. - Update doc/index.asciidoc - Create a signed git tag (git tag -s vX.Y.Z -m "commit message") - Create and sign release tarballs (generate with "ninja dist") +- Create release on gitlab project page +- Upload release tarball and signature to gitlab ("glab release upload ...") - Update pacman website Transifex updates are handled using the transifex client. The basic process is: - Pull updates from transifex ("tx pull -f --minimum-perc 75") - Update po files ("./build-aux/update-po") -- Fix all translation errors found +- Fix all translation errors found (e.g. using "mint-check-translations") - Add any new locales to the relevant LINGUAS file - Optional: Make any manual changes needed (e.g. fixing spacing in a string) and update po files again