Send patches - preferably formatted by git format-patch - to patches at archlinux32 dot org.
summaryrefslogtreecommitdiff
path: root/RELEASE
diff options
context:
space:
mode:
authorAllan McRae <allan@archlinux.org>2018-05-28 09:38:29 +1000
committerAllan McRae <allan@archlinux.org>2018-05-28 09:38:29 +1000
commitbe4c491ceb34f04c3352ddd1d3c4672560e7ea8c (patch)
treef0024bbb10d64da32154c9775c7c7fd7ae3f8cb4 /RELEASE
parentca128f2efff05449c4c6888fcb15136bd518cae5 (diff)
Release v.5.1.0v5.1.0
Signed-off-by: Allan McRae <allan@archlinux.org>
Diffstat (limited to 'RELEASE')
-rw-r--r--RELEASE4
1 files changed, 2 insertions, 2 deletions
diff --git a/RELEASE b/RELEASE
index 7a0ec3ae..c9949253 100644
--- a/RELEASE
+++ b/RELEASE
@@ -8,8 +8,8 @@ The following checklist should be used for making a pacman release.
- 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")
+- 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")
- Update pacman website