Hi,
I think that not only should bugs be marked by the
distributions they exist in, they should also be classified by
architecture; since it is quite possible for a bug to only exist in a
specific arch. This opens to dor for arch specific maintainers; which
is not a bad idea since the
Rob Browning writes:
Yann Dirson [EMAIL PROTECTED] writes:
[Note: I don't know much about the internals of the BTS; I hope this
will be accurate enough, though]
* These fields would be named by the codename of the dist
(eg. `hamm_status') - can this be achieved easily ?
Previously Manoj Srivastava wrote:
I think that not only should bugs be marked by the
distributions they exist in, they should also be classified by
architecture;
Actually, I think we can do the same way more efficent. Each bug already
has a Version-number. Now we if we add a field
On Tue, Jun 23, 1998 at 12:38:19PM +0200, Wichert Akkerman wrote:
Previously Manoj Srivastava wrote:
I think that not only should bugs be marked by the
distributions they exist in, they should also be classified by
architecture;
Actually, I think we can do the same way more
Wichert Akkerman writes:
Previously Manoj Srivastava wrote:
I think that not only should bugs be marked by the
distributions they exist in, they should also be classified by
architecture;
Actually, I think we can do the same way more efficent. Each bug already
has a
Santiago Vila writes:
As I see it, the `Status' of a bug-report (I suggest at least: clear,
reported, identified, known-workaround, known-fix, fixed) is an issue
that is othogonal to the `Severity' (as used for now: wishlist,
normal, important, grave, critical) - eg. the fact that a
Yann Dirson [EMAIL PROTECTED] writes:
[Note: I don't know much about the internals of the BTS; I hope this
will be accurate enough, though]
* These fields would be named by the codename of the dist
(eg. `hamm_status') - can this be achieved easily ?
Why not just go with something more
Yann Dirson writes:
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).
Thinking backward, I don't like my last proposal
8 matches
Mail list logo
