bogofilter version numbers

[David Relson]

At 07:09 AM 10/18/02, Matthias Andree wrote:
>[Resend, I sent it to the cvs list instead on my first try.]
>
>On Thu, 17 Oct 2002, relson at users.sourceforge.net wrote:
>
> > Update of /cvsroot/bogofilter/bogofilter
> > In directory usw-pr-cvs1:/tmp/cvs-serv18524
> >
> > Modified Files:
> >       configure.in
> > Log Message:
> > Change version to 0.7.5.1 to distinguish cvs from release.
>
>We might want to instead call this 0.7.5.0.cvs (not for this version,
>but for future versions).

Matthias,

I've been thinking that we _do_ need to change the version number more 
frequently.  Last weekend, I was emailing back and forth with a 0.7.4 user 
and we got all tangled up with switches.  The released version was still 
using -h, -s, -H, and -S.  I knew that cvs had -n, -s, -S, -N as well as 
new switches -h, -u, -l, and -e.  He swore he had 0.7.4 with -n, -s, -N, 
and -S.  There was some confusion until we realized that he had the debian 
cvs snapshot.  Changing version numbers more often would be very useful.

One idea is to change the version number after _every_ code change.  A 
second idea is to change it after any change that would be user visible - 
new switch, algorithm change that might change the spamicity of a message, 
etc.  Part of my thought is that changes that are strictly internal (for 
example function name changes, changing from an if statement to a switch 
statement, etc) might not need a version number change.

Certainly, something that distinguishes the (experimental) cvs versions 
from released versions would be very useful.

David