index : pacman | |
Archlinux32 fork of pacman | gitolite user |
summaryrefslogtreecommitdiff |
author | Allan McRae <allan@archlinux.org> | 2020-05-11 12:59:51 +1000 |
---|---|---|
committer | Allan McRae <allan@archlinux.org> | 2020-06-01 10:59:08 +1000 |
commit | 454ea024383eab60295e4c4fdf2c329475887b2c (patch) | |
tree | 5f3397782b3bb7e061770a63da5b7e34877f8193 /RELEASE | |
parent | 8ce142a2552418f64a74e773f659d92b065d6209 (diff) |
-rw-r--r-- | RELEASE | 9 |
@@ -1,22 +1,21 @@ The following checklist should be used for making a pacman release. -- Ensure "make distcheck" succeeds +- Ensure "ninja dist" succeeds - Call a freeze to development. - Send translation updates to Transifex at least two weeks before a major release (see below). At this stage, strings can only be changed for a major issue. - Update NEWS and README files - Pull translation updates from Transifex -- Update version in configure.ac as described in file +- Update version in meson.build as described in file - 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 "make distcheck") - - In addition to the standard autotools toolchain, autoconf-archive is needed +- Create and sign release tarballs (generate with "ninja dist") - Update pacman website Transifex updates are handled using the transifex client. The basic process is: - Pull updates from transifex ("tx pull -a -f --minimum-perc 75") -- Update po files ("make update-po") +- Update po files ("./build-aux/update-po") - Fix all translation errors found - Add any new locales to the relevant LINGUAS file - Optional: Make any manual changes needed (e.g. fixing spacing in a string) |