Matt Zimmerman <[EMAIL PROTECTED]> writes:
> Since testing is changing all the time, it would probably not be
> worthwhile to try to keep such a document up-to-date. Once woody
> cools and solidifies, someone could read through the complete set of
> Debian changelogs and try to pick out the most significant changes.
I guess this is too much work for a single person. This means that the
most significant changes are probably whipped up from memory. The
package selection is also highly subjective (e.g. a significant
advance in boa may not be considered that important for the majority
of Debian users who have apache).
Hmm, something I read aeons ago recommend that you mark significant
changes in your ChangeLog (e.g. by putting a # in the first column),
so that you have an easier time when the next release is due, and you
want to list all those.
If we had a similar convention, the release manager could grep the
most important packages' changelogs for these marks. And (even more
important IMO) interested users could do the grepping themselves, on
the packages /they/ consider important. I could write a script that
does this for all installed packages quite easily.
--
Robbe
signature.ng
