From 23a7c6c6b0496acecc185b3d6fed34a520e53808 Mon Sep 17 00:00:00 2001 From: mmdolze Date: Mon, 22 Nov 2010 19:54:05 +0000 Subject: [PATCH] Add the release chapter to Makefile. Note the branch point CVS tag. --- docs/lcdproc-dev/Makefile.am | 1 + docs/lcdproc-dev/releasing.docbook | 21 +++++++++++++++------ 2 files changed, 16 insertions(+), 6 deletions(-) diff --git a/docs/lcdproc-dev/Makefile.am b/docs/lcdproc-dev/Makefile.am index f67252b..b2918cf 100644 --- a/docs/lcdproc-dev/Makefile.am +++ b/docs/lcdproc-dev/Makefile.am @@ -10,6 +10,7 @@ EXTRA_DIST = add-your-driver.docbook \ make-driver.docbook \ programming.docbook \ README.docbook \ + releasing.docbook \ shared-files.docbook diff --git a/docs/lcdproc-dev/releasing.docbook b/docs/lcdproc-dev/releasing.docbook index 31abcec..2f9db92 100644 --- a/docs/lcdproc-dev/releasing.docbook +++ b/docs/lcdproc-dev/releasing.docbook @@ -87,11 +87,24 @@ release. + + + Tag the stable tree to indicate the file revision where the branch was + made. This eases later diffs againt that point. + + + Run: cvs tag LCDPROC_0_5_A_BP + (where A is the version number of the next + release and _BP means branch point). + + + Tag names are all uppercase with underscores to separate elements! + + Create a release branch in CVS. Run: - cvs tag -b lcdproc-0-5-A where - A is the version number of the next release. + cvs tag -b lcdproc-0-5-A Release branch names are all lowercase with hypens to separate @@ -121,10 +134,6 @@ release. Set a CVS tag for the release. Run: cvs tag LCDPROC_0_5_A_RELEASE where A is the version number of the next release. - - Release tag names are all uppercase with underscores to separate - elements! -