On Wed, Oct 27, 2004 at 05:41:42PM +0400, Nikita V. Youshchenko wrote:
Could the script that generates the RC bug list be modified to show two
additional numbers for each bug: first, how old it is (in days), and
second, how old (in days) is the last message posted to the bug?
This will
On Tue, Oct 26, 2004 at 11:20:39PM +0200, Javier Fernández-Sanguino Peña wrote:
On Tue, Oct 26, 2004 at 09:51:45AM -0700, Joe Buck wrote:
For people who care about getting sarge out, it's not useful to put out
a report listing 726 bugs, only 150 of which matter, in a form that
makes it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello.
Could the script that generates the RC bug list be modified to show two
additional numbers for each bug: first, how old it is (in days), and
second, how old (in days) is the last message posted to the bug?
This will allow to see easilly
On Fri, Oct 22, 2004 at 06:30:02AM -0700, BugScan reporter wrote:
Bug stamp-out list for Oct 22 06:02 (CST)
Total number of release-critical bugs: 726
...
Number that are being ignored: 45
Number on packages not in testing: 420
Number concerning the next release (excluding ignored and
On Tue, Oct 26, 2004 at 09:51:45AM -0700, Joe Buck wrote:
For people who care about getting sarge out, it's not useful to put out
a report listing 726 bugs, only 150 of which matter, in a form that
makes it rather difficult to cleanly extract only the 150 that matter.
How about putting out a
Bug stamp-out list for Oct 22 06:02 (CST)
Total number of release-critical bugs: 726
Number that will disappear after removing packages marked [REMOVE]: 1
Number that have a patch: 83
Number that have a fix prepared and waiting to upload: 24
Number that are being ignored: 45
Number on packages
6 matches
Mail list logo
