[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Bug Reports for 1.6 Release Candidates
From: |
Rob Browning |
Subject: |
Re: Bug Reports for 1.6 Release Candidates |
Date: |
Sun, 17 Mar 2002 21:46:57 -0600 |
User-agent: |
Gnus/5.090006 (Oort Gnus v0.06) Emacs/21.1 (i386-debian-linux-gnu) |
Evan Prodromou <address@hidden> writes:
> Also, the BUGS file as it stands doesn't have a criticality rating
> (wishlist, normal, release-critical, whatever) nor a version number
> that the bug was identified in (1.4, 1.5.x, 1.7.x, etc.), nor a
> version number that the bug _should_ be fixed in (1.5.x, 1.7.x).
Agreed, and it might be nice to have some other way to keep the info
for a bug that applies across more than one tree in one location (see
my reply to your other thread) if we can manage to do it with a
solution that doesn't just over-complicate things. Though bug
tracking seems to me like *exactly* the kind of thing for which you
want a relational DB.
--
Rob Browning
rlb @defaultvalue.org, @linuxdevel.com, and @debian.org
Previously @cs.utexas.edu
GPG=1C58 8B2C FB5E 3F64 EA5C 64AE 78FE E5FE F0CB A0AD