bryson/pacman
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Manage releases through gitlab

Browse source 
Also provide an example for how to check for errors in translations

Signed-off-by: Allan McRae <allan@archlinux.org>
This commit is contained in:
Allan McRae 2024-03-04 13:32:14 +10:00
parent 6bb95c8856
commit d7f3ce1217
1 changed files with 3 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
RELEASE
View file

@ -11,12 +11,14 @@ The following checklist should be used for making a pacman release.
- Update doc/index.asciidoc - Update doc/index.asciidoc
- Create a signed git tag (git tag -s vX.Y.Z -m "commit message") - Create a signed git tag (git tag -s vX.Y.Z -m "commit message")
- Create and sign release tarballs (generate with "ninja dist") - 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 - Update pacman website
Transifex updates are handled using the transifex client. The basic process is: Transifex updates are handled using the transifex client. The basic process is:
- Pull updates from transifex ("tx pull -f --minimum-perc 75") - Pull updates from transifex ("tx pull -f --minimum-perc 75")
- Update po files ("./build-aux/update-po") - 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 - Add any new locales to the relevant LINGUAS file
- Optional: Make any manual changes needed (e.g. fixing spacing in a string) - Optional: Make any manual changes needed (e.g. fixing spacing in a string)
and update po files again and update po files again