diff options
| author | Allan McRae <allan@archlinux.org> | 2024-04-22 14:43:08 +1000 |
|---|---|---|
| committer | Allan McRae <allan@archlinux.org> | 2024-05-04 11:21:26 +0000 |
| commit | 9f78628f6ccd691552397e7480aeedb1ff5f2387 (patch) | |
| tree | d558f595b41e8dbdc84007eb6ec5815a0c8c9df7 /RELEASE | |
| parent | 60d517107beccb3d6f7759be2aaa9bc84a342e1d (diff) | |
Update RELEASE documentation for website deployment via gitlab CI
Signed-off-by: Allan McRae <allan@archlinux.org>
Diffstat (limited to 'RELEASE')
| -rw-r--r-- | RELEASE | 4 |
1 files changed, 2 insertions, 2 deletions
@@ -13,7 +13,8 @@ The following checklist should be used for making a pacman release. - 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 +- Create branch release/?.?.x (with ?.? replaced by major version number) +- Update .gitlab-ci.yml to point the website pages run at release branch Transifex updates are handled using the transifex client. The basic process is: - Pull updates from transifex ("tx pull -f --minimum-perc 75") @@ -25,7 +26,6 @@ Transifex updates are handled using the transifex client. The basic process is: - Push updated po files to transifex ("tx push -s -t --skip") Point releases: -- create branch release/?.?.x (with ?.? replaced by major version number) - all bugs fixes slated for the release branch must first land on master (unless no longer relevant) - following the initial post-release period when the release and master |