[spambayes-dev] RE: Spambayes 1.0a4

[Meyer, Tony]

[I've cc'd this back to the list for the changelog discussion]

> > [T]hanks for moving the tag as well (didn't realise that 
> > you could do that).
> No problem.  "cvs tag -F" is what you're looking for, or the 
> equivalent in WinCVS which is something like Modify / Create 
> a tag / Overwrite existing tags.

I use TortoiseCVS, but it's probably there somewhere.

> Incidentally, I didn't try this but I think you can create a 
> unix-line-ending tar.gz distribution on Windows: if you check 
> out with Unix line endings (in WinCVS, Create / Checkout 
> module / Globals / Unix LF) and then do "python setup.py 
> sdist --formats=gztar" then I think that will work.

That's a good idea.  I'll try and remember it :)

> I notice there's now a ChangeLog in the repository - should I 
> be updating that whenever I make a user-visible edit, or is 
> it only updated for each release?

I created it just before a3 was intended to be released (some weeks
before it was ;) since there were so many changes, a2 being quite some
time before.  I update it every now and then, but yeah, if people wanted
to update it themselves when they do a check-in worth including, that
would be great.

> Updating it on the fly 
> would make life easier for whoever builds the release.

Indeed :)

> At 
> work we have a rule that any user-visible change must be 
> documented in the global ChangeLog (along with a bug number 
> if it has one), and that works very well - if someone claims 
> that some bugfix or new feature doesn't work for them, you 
> just get them to look in their copy of the global ChangeLog 
> to see whether they really do have that edit.

When deciding what to include I just went with instinct since I didn't
have a plan - most particularly I ignored doc fixes and typo fixes.  I
suppose what I ended up with is pretty close to 'user-visible' though,
although there are some that are probably more developer-visible.
Doesn't bother me what rule it is, although we should really specify
one, I guess.

Note that I also made a "What's New" file (but called it WHAT_IS_NEW to
avoid the apostrophe).  This should be easier to read and only has those
changes that might interest a user.  This could also be updated
change-by-change, although it's a lot simpler to do than the changelog.

=Tony Meyer