summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorgdt <gdt>2005-02-23 16:20:07 +0000
committergdt <gdt>2005-02-23 16:20:07 +0000
commit6648e445259a4f4dc4a2a1019a8bc11e28110cdd (patch)
treed0efbfbc219d755d44dc6f473e13446ca6a395c5
parentb9a4e3cd9b01d9318465ae1f8087cda381020153 (diff)
downloadquagga-6648e445259a4f4dc4a2a1019a8bc11e28110cdd.tar.bz2
quagga-6648e445259a4f4dc4a2a1019a8bc11e28110cdd.tar.xz
add release procedure, noting redhat spec oddness
-rw-r--r--HACKING18
1 files changed, 18 insertions, 0 deletions
diff --git a/HACKING b/HACKING
index 8923d32f..47af12bd 100644
--- a/HACKING
+++ b/HACKING
@@ -62,6 +62,24 @@ maintainer who usually maintains that meta-data). Also, CVS meta-data such
as cvsignore files do not require ChangeLog updates, just a sane commit
message.
+RELEASE PROCEDURE
+
+ Tag the repository with release tag (follow existing conventions).
+ [This enables recreating the release, and is just good CM practice.]
+
+ Check out the tag, and do a test build.
+
+ In an empty directory, do a fresh checkout with -r <release-tag>
+ [This makes the dates in the tarball be the modified dates in CVS.]
+
+ {Manually patch redhat/quagga.spec.in to remove @CONFDATE@}
+ ./configure
+ make dist
+
+If any errors occur, move tags as needed and start over from the fresh
+checkouts. Do not append to tarballs, as this has produced
+non-standards-conforming tarballs in the past.
+
TOOL VERSIONS
Require versions of support tools are listed in INSTALL.quagga.txt.