Re: linux-kernel-digest V1 #1015

Jeff Garzik (jeff.garzik@spinne.com)
Sun, 20 Jul 1997 18:33:46 -0400


> From: Marcus B[SMTP:marcus@cwi.net.au]
> Sent: Sonntag, 20. Juli 1997 12:04
> To: Linux-Kernel Mail-list
> Subject: Linux Kernel Bug-list Website

> 1. After a bug has been fixed and published on the site, Where does it
> go then?

In the section for closed bug reports. Never erase a bug report, a
comment added to a bug report, or a bug resolution. Somebody's patch
may not work in all cases, and the bug could be re-opened.

In this manner we can see when bugs actually are fixed, not when someone
posts a fix...

> 2. Who will notify me if the bug-fix is official enough to take the bug
> report off the site?

Let users close bug reports themselves, and just keep track of the site
so someone doesn't abuse this privelege.

> 3. Bug-fixes will stay on the site for apron. 7 days, is this long
> enough? or can it be shorter?

Keep them until the next major release of Linux, or until they are
superceded by a future patch. ie. a fix to 2.1.x would stay in until
2.3.0, a fix to 2.0.x would stay in until 2.2, etc.

> 4. Should the fixes be kept on the site?

Doesn't really matter, as long as the site provides links to easily link
users to the fixes.

> 5. Should the fixes be published somewhere else as well?

Mirrors are a good thing.

-- 
Jeff Garzik					   Quality news feeds
News Administrator		       INN Technical info, Consulting
Spinne, Inc.				http://www.spinne.com/usenet/