[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[FYI] {maint} hacking: release procedure: fix order of some steps
From: |
Stefano Lattarini |
Subject: |
[FYI] {maint} hacking: release procedure: fix order of some steps |
Date: |
Sat, 17 Nov 2012 19:44:40 +0100 |
* HACKING (Release procedure): The manuals should be rebuilt and
uploaded at at www.gnu.org *before* bumping the version number to
the next alpha release.
Signed-off-by: Stefano Lattarini <address@hidden>
---
HACKING | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/HACKING b/HACKING
index e245039..d69c75d 100644
--- a/HACKING
+++ b/HACKING
@@ -258,12 +258,6 @@
locations. In case you need to sign with a non-default key, you can
use "make GNUPLOADFLAGS='--user KEY' git-upload-release".
-* Update version number in configure.ac to next alpha number.
- Re-run ./bootstrap.sh and commit.
-
-* Don't forget to "git push" your changes so they appear in the public
- git tree.
-
* For stable releases, update the manuals at www.gnu.org:
- Generate manuals:
cd doc
@@ -275,6 +269,12 @@
- Check for link errors, fix them, recheck until convergence:
<http://validator.w3.org/checklink>
+* Update version number in configure.ac to next alpha number.
+ Re-run ./bootstrap.sh and commit.
+
+* Don't forget to "git push" your changes so they appear in the public
+ git tree.
+
* Send the announcement at least to <address@hidden> and
<address@hidden>. If the release is a stable one, the announcement
must also go to <address@hidden>; if it is an alpha or beta release,
--
1.8.0.150.gb0b00a3
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [FYI] {maint} hacking: release procedure: fix order of some steps,
Stefano Lattarini <=