From 48e21ffd6e71e1a189bd8da910976990ba0c0f77 Mon Sep 17 00:00:00 2001 From: Thomas Vander Stichele Date: Fri, 13 Jan 2006 19:51:48 +0000 Subject: [PATCH] updates to release doc Original commit message from CVS: updates to release doc --- docs/random/release | 38 ++++++++++++++++++++++++++++++++++++++ 1 file changed, 38 insertions(+) diff --git a/docs/random/release b/docs/random/release index c8f7c75..2c04c8d 100644 --- a/docs/random/release +++ b/docs/random/release @@ -194,3 +194,41 @@ NOTES ON STARTING A NEW STABLE SERIES perl -i -p -e 's@0\.9([^.])@0.10$1@g' (file) changes 0.9 -> 0.10 + +NEW NOTES +--------- +- www/bin/new-release is a release helper script. It automates a lot of the + tedious work. Now releasing looks like this: + +- before release: + - make sure all blocker bugs for that release are fixed or deferred + - make sure you have a local copy of all online files + - bin/new-release (module) (version) (checkoutdir) (release name) + - updates cvs + - allows you to update versioning in configure.ac + - rebuilds + - updates ChangeLog + - adds a new releases/module/version.xml file and lets you edit + --> here you add/fix up the features (from ChangeLog) and check + contributors + - allows you to update NEWS file with snippets from RELEASE + --> copy stuff + - rebuilds docs for plugins + - rolls release tarballs and puts them in the local www/data tree + - uploads docs to website + - commits changes to po files + - shows you a diff for evaluation + + - build packages to test + +- release: + - cvs commit in the tree + - tag tree + for example for 0.6.3 : + cvs tag RELEASE-0_6_3 + - if working in the "stable" release branch, update to this tag to freeze it: + cvs up -r RELEASE-0_6_3 + - sync source and packages to website + - add entry on website; commit additions to website + + -- 2.7.4