On Tue, 10 Sep 2013 21:11:54 +0200, Cor Nouws wrote:
Apart from keeping the number_of_unconfirmed low, I also find it useful
to try to make summaries as clear as possible: looking at the result of
a query, that helps a lot to pick the right issues to look e.g. for
duplicates.
Kind rega
On Fri, 06 Sep 2013 01:07:26 +0200, Tommy wrote:
On Wed, 04 Sep 2013 07:13:51 +0200, Tommy wrote:
since 4.1.1.2 has been subsequently released as final I suggest to
change the label to 4.1.1.2 release as done before in previous versions.
bye, TOMMY
the same applies to 3.6.7.2 and 4.0.5
Hi Joel,
Joel Madero wrote (09-09-13 17:24)
A bug a day (you choose which one ;) ) shouldn't take more than 10ish
minutes. Hopefully despite busy schedules we can make the commitment -
ultimately we still need 25 people making this commitment to keep up
with demand (or a few people able to comm
On Tue, Sep 10, 2013 at 11:37:59AM +0100, Michael Meeks wrote:
> Having said that - I guess investing more cycles into a dashboard /
> homepage for developers that shows where the fires are burning, the new
> MAB's etc. would prolly be a more useful investment of time.
Fully agree there -- t
On Tue, 2013-09-10 at 11:37 +0200, bjoern wrote:
> FWIW, I had a bibisected charting query sometime ago, you find it in
> bugzilla->reports->new charts and then select the
> LibreOffice->LibreOffice->bibsected-unresolved. I just added a
> bibisected-total
> there too, so one can now get these as
Hi,
On Tue, Sep 10, 2013 at 09:56:57AM +0100, Michael Meeks wrote:
> I guess so ;-) or bugzilla changed in some way, or someone went on a
> rampage removing the 'bibisect' keyword (or whatever). The stats are
> generated by:
>
> dev-tools/scripts/esc-bug-stats.pl
Hmm, looks sane to m
On Tue, 2013-09-10 at 00:37 +0200, bjoern wrote:
> > > > * Bibisected bugs open: whiteboard 'bibsected'
> > > > + 35/140 36/167 37/137 41/137 33/128 33/125 34/124 34/123
> > > > 36/122 38/119
> > > > + http://bit.ly/VQfF3Q
> > >
> > > Dumb question:
> > > Whats that secon
