[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Please start a release branch (was: CVS 1.11.5 Released <strong>(Securit
From: |
Ingolf Steinbach |
Subject: |
Please start a release branch (was: CVS 1.11.5 Released <strong>(Security Update)</strong>) |
Date: |
Tue, 21 Jan 2003 16:16:18 +0100 |
User-agent: |
Mutt/1.3.25i |
* Paul Edwards <kerravon@nosppaam.w3.to> [2003-01-21 15:41]:
> I was wondering if rather than every release replacing one set
> of bugs with another set of bugs, we could have a particular
> version (maybe starting with 1.11.5), which will be continually
> updated, with bug fixes only, even when version 1.14.17 has
> just been released.
Yes, please. Or maybe
1) start a branch (named e.g. cvs-1_12-branch) at the current HEAD
2) continue developing in trunc
3) pull up only bugfixes to cvs-1_12-branch
4) eventually tag the current state of cvs-1_12-branch as CVS-1_12
(i.e. the 1.12 release)
5) bug fixes found after CVS-1_12 are pulled up to cvs-1_12-branch
6) eventually tag the current state of cvs-1_12-branch as CVS-1_12_1
7) repeat 5)/6) as necessary
8) eventually go to 1) but with cvs-1_13-branch
I understand that there might not be enough man power to have all
pull-ups approved by a release engineer. However, even without a
release engineer the above procedure should notably improve stability
and security without too much additional effort (provided that each
developer is careful wrt to commits to the branches).
Kind regards
Ingolf
--
Ingolf Steinbach Jena-Optronik GmbH
ingolf.steinbach@jena-optronik.de ++49 3641 200-147
PGP: 0x7B3B5661 213C 828E 0C92 16B5 05D0 4D5B A324 EC04