From 0d7e9134d828d5aee8c83960bb706a726cdc2ec4 Mon Sep 17 00:00:00 2001 From: gdt Date: Wed, 23 Feb 2005 16:20:07 +0000 Subject: add release procedure, noting redhat spec oddness --- HACKING | 20 +++++++++++++++++++- 1 file changed, 19 insertions(+), 1 deletion(-) diff --git a/HACKING b/HACKING index 8c76f7ad..8aa0d979 100644 --- a/HACKING +++ b/HACKING @@ -1,5 +1,5 @@ -*- mode: text; -*- -$Id: HACKING,v 1.15 2005/02/23 11:54:12 hasso Exp $ +$Id: HACKING,v 1.16 2005/02/23 16:20:07 gdt Exp $ GUIDELINES FOR HACKING ON QUAGGA @@ -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 + [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. -- cgit v1.2.1