> > I strongly suggest to start a ChangeLog file to document changes
> > in the repository, mainly to avoid reporting the same errors again
> > and again.
>
> I think there's a simpler solution than using a ChangeLog.
>
> One is to use the convention that bugs are removed only directly
> after the official release of a new version. This would mean that
> all reported bugs in 2.2.1 would exist in lily-bugs with date stamp
> of the 2.2.2 release. If you like, I could in addition tag these
> files lilypond_2_2_1 (showing that this is the final list of known
> 2.2.1 bugs).
>
> Would this be satisfactory?
Not for me. What you suggest is far too complicated IMHO; it relies
on CVS access which is not always available. BTW, what exactly do you
mean with `date stamp'?
There is a good reason that GNU projects use ChangeLog files for
bookkeeping. Until now it beats any other logging system.
Werner
_______________________________________________
lilypond-devel mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/lilypond-devel
