Richard Braakman writes:
> Dennis L. Clark wrote:
> > Can anyone think of an automated way to weed out bug reports on versions
> > which haven't been released into hamm from the release-critical list? A
> > quick fix would be to modify the priority of the bug report, but that
> > would be The Wrong Thing.
>
> Automating this would be wrong, I think. The "Version" header in the
> bug report says what version the bug was found in, not necessarily
> what version first had the bug.
Sure, but it would be nice to have some sort of a mechanism to help us
to deal with bugs and dists.
I think that we should keep the state of each bug-report regarding
each dist (stable/frozen/unstable/experimental).
Maybe we could do that with additionnal attributes associated with
each report, eg. "{bo,hamm,slink}-status", which could take their
values in the set current of severities. The still missing "Fixed"
severity would be used to tell a dist is clear wrt this report.
A bug will then be allowed to be closed only when all dists list
"Fixed".
Any comments ?
--
Yann Dirson <[EMAIL PROTECTED]> | Stop making M$-Bill richer & richer,
isp-email: <[EMAIL PROTECTED]> | support Debian GNU/Linux:
debian-email: <[EMAIL PROTECTED]> | more powerful, more stable !
http://www.mygale.org/~ydirson/ | Check <http://www.debian.org/>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
