On Mon, 8 May 2006, Jeff Trawick wrote:
We should do better than leaving the users to rediscover and deal with
regressions themselves, once we know there's a problem. Can I suggest
an Errata page, to list *all* known regressions in current/recent versions,
linked from the main page alongside "Download/New Features/Changelog"?
+1
[REGRESSION] in the changelog might be good too for permanent tracking.
Most useful would be to ship a new version within a small amount of
time that corrects only regressions and has no other changes (if at
all practical; desire is to limit testing concern to speed up
delivery).
The same goes for security issues. For apache 2.2.0 there was only a
note that "the following issues are fixed in the development version"
or something similar, not exactly what you want as an end user when
you're affected by that particilar issue.
Either provide a patch, or provide a new version. Neither should be
too difficult if you limit the scope to only fix the specific issue.
/Nikke
--
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Niklas Edmundsson, Admin @ {acc,hpc2n}.umu.se | [EMAIL PROTECTED]
---------------------------------------------------------------------------
I didn't do it nobody saw me you can't prove anything
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
