diff options
| author | Allan McRae <allan@archlinux.org> | 2016-02-23 14:42:35 +1000 |
|---|---|---|
| committer | Allan McRae <allan@archlinux.org> | 2016-02-26 15:20:02 +1000 |
| commit | 1a94c00e363081594bd6940d98117289b03692d6 (patch) | |
| tree | dc48a29a404b5691ed88d5bf965c7a4046e259aa | |
| parent | f363cf78575cc4c54dee5801274e55d07e0971b1 (diff) | |
Add release instructions
This serves as a release checklist for anyone making a pacman release.
Signed-off-by: Allan McRae <allan@archlinux.org>
| -rw-r--r-- | RELEASE | 23 |
1 files changed, 23 insertions, 0 deletions
diff --git a/RELEASE b/RELEASE new file mode 100644 index 00000000..3aca2ae9 --- /dev/null +++ b/RELEASE @@ -0,0 +1,23 @@ +The following checklist should be used for making a pacman release. + +- Ensure "make distcheck" 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 doc/index.txt +- Create a signed git tag (git tag -x vX.Y.Z -m "commit message") +- Create and sign release tarballs (generate with "make distcheck") +- Update pacman website + +Transifex updates are handled using the transifex client. The basic process is: +- Pull updates from transifex ("tx pull -a -f") +- Update po files ("make 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) + and update po files again +- Push updated po files to transifex ("tx push -s -t --skip") |