Upcoming Code Freeze

[Matthias Andree]

On Mon, 16 Sep 2002, Adrian Otto wrote:

> That's an excellent suggestion. Can you please share instructions with the
> group so that everyone can understand how this is done?

> I assume that I would create a branch, use it as a release candidate, and
> then release the branch, right? Example commands would help me, since it's
> been over five years since I've done configuration management work, and I
> used different tools.

Yes, you go branch BRANCH_0_7_4 (cvs tag -c -b) or whatever you call it.

Then you cvs update -r BRANCH_0_7_4 (the branch tag again) -- or check
bogofilter out into a separate directory --, and CVS shall remember that
branch tag ("sticky tag") until you explicitly clear it with cvs update
-A.

If your current working copy bears a sticky tag, then the commits only
go into the BRANCH_0_7_4 branch. At some time, when you think it's
ready, you do "make distcheck", grab the tarball it created and release
that, and for completeness, at the same time, you tag this as regular
release (plain: cvs tag BOGOFILTER_0_7_4_RELEASE or something).

-- 
Matthias Andree