Re: Better documenting what does not work in Etch.

[Javier Fernández-Sanguino Peña] Actually, the website has errata pages for each release work at the wiki could be a basis for an updated page at the website. Yes. I suggest using URL:http://wiki.debian.org/DebianEtch for this purpose. Happy hacking, -- Petter Reinholdtsen -- To

Re: Better documenting what does not work in Etch.

[Charles Plessy] Under the current policy, not all fixes to these problems would make it in a point release, but since the list is likely to grow longer and longer with time, I am really wondering if there is a better way to inform the users of that kind of issues, if possible a priori. Among

Re: Better documenting what does not work in Etch.

On Wed, May 30, 2007 at 04:33:59PM +0200, Petter Reinholdtsen wrote: Very good points, and I believe you have a good point. What about making an errata wiki page for the etch release on URL:http://wiki.debian.org/, and add links to the etch bugs in BTS? It migth form the basis for updating

Better documenting what does not work in Etch.

Dear developpers, Since the release, I am using only Etch, and there something frustrating in the fact that discovering and reporting minor problems is not very helpful. What could be the other obvious points of information ? For example, here are the kind of issues I experienced: - Japanese