bogofilter-0_7_6 branch tagged.

[Matthias Andree]

Dear fellow hackers,

I have just branched bogofilter, the new branch is named
bogofilter-0_7_6. I suggest that we consider this branch feature frozen,
only bug, build and portability fixes and documentation changes should
be committed. I also bumped the version to 0.7.6.0 (yes, ugly, but I
want to avoid having two different tarballs with the same code around as
we had for "early 0.7.5" and "0.7.5 with HP-UX compile fix".

This should become bogofilter 0.7.6 soon, to fix the non-transparent
transport in bogofilter -p, notably the NUL and CR characters should now
be left intact.

Because no-one has objected, some others agreed, I branched the source.

To turn your current work directory in one of the bogofilter 0.7.6
branch, type:

cvs update -d -P -r bogofilter-0_7_6

Note that all subsequent commits will then be on the bogofilter-0_7_6
branch, (CVS calls this "sticky tag" -- it happens automatically,
without your doing anything except adding the -r switch to cvs update or
cvs checkout once); until you type:

cvs update -d -P -rHEAD -A

which will switch the work directory back to the head version.

Alternatively, you can check out the bogofilter-0_7_6 branch into a
separate working directory. It's no problem to have to different
branches checked out at the same time, but in different directories.


We should now negotiate how we proceed.

Does anyone have a test suite beyond what is in the source now? For how
long should we offer this CVS version? When should we do a "beta" or
"release candidate" release, and how many days after that should we
promote that version to a "full" release?

Maybe someone could write up a release check list.

Here's a start:

1. make sure "make distcheck" is fine
2. branch the tree (cvs tag -b bogofilter_A_B_C) and switch to the new tree.
   Name: bogofilter_A_B_C.
3. bump version in configure.in to A.B.C.0 and commit to the tree.
4. make distcheck and release beta, and cvs tag the same versions, NOT AS A
   BRANCH: cvs tag bogofilter-beta-A_B_C_0 (or _1, _2, ...)
5. if bug reports or documentation come in, fix, commit, bump version to
   A.B.C.1 (A.B.C.2, ...), then go back to #4
6. if the tree has proven stable, make distcheck and release full
   version, cvs tag bogofilter-A_B_C_0
7. release the sticky tags, swtich the HEAD, merge fixes and commit.

For discussion: Should we add "beta" in 3.?

Should we add any tests to run so the "make check" or "make distcheck"
get more thorough and check if bogofilter can learn, how good it is in
respect to false positives/negatives?

-- 
Matthias Andree