This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Regression information in Bugzilla

From: Daniel Berlin <dberlin at dberlin dot org>
To: "Zack Weinberg" <zack at codesourcery dot com>
Cc: "Giovanni Bajo" <giovannibajo at libero dot it>,"Mark Mitchell" <mark at codesourcery dot com>,"Gabriel Dos Reis" <gdr at integrable-solutions dot net>, <gcc at gcc dot gnu dot org>
Date: Sun, 21 Dec 2003 14:57:11 -0500
Subject: Re: Regression information in Bugzilla
References: <199701c3c7f0$220cf9a0$b7b92997@bagio> <87llp6vwkn.fsf@egil.codesourcery.com>

On Dec 21, 2003, at 1:45 PM, Zack Weinberg wrote:

"Giovanni Bajo" <giovannibajo@libero.it> writes:

I understand that this system is far from being optimal. We are
discussing this issue in these days on the bugzilla-master list, and
trying to come up to a decent solution to handle this. A first
stopgap would be to be able to set multiple target milestones for
each gap, as suggested by Daniel Berlin. A more efficient solution
(solving also other problems with version tracking) is at study.


Other projects that use bugzilla seem to use X.Y-regression tags
instead of putting this information into the bug title.


Right.
I have no idea why we don't use keywords to track this.

References:
- Regression information in Bugzilla
  - From: Giovanni Bajo
- Re: Regression information in Bugzilla
  - From: Zack Weinberg

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]