The expiration of old (stale) bug reports happened right now.
Stats:
# of bug reports before expiration: 826
# of expired bug reports: 188
# of bug reports after expiration: 638
That affected ~22% of our overall open bug reports and ~36% of bug
reports which are not in prog
On 21.06.2016 18:24, Adam Young wrote:
> On 06/21/2016 08:43 AM, Markus Zoeller wrote:
>> A reminder that this will happen in ~2 weeks.
>>
>> Please note that you can spare bug reports if you leave a comment there
>> which says one of these (case-sensitive flags):
>> * CONFIRMED FOR: NEWTON
>> * CO
On 06/21/2016 08:43 AM, Markus Zoeller wrote:
A reminder that this will happen in ~2 weeks.
Please note that you can spare bug reports if you leave a comment there
which says one of these (case-sensitive flags):
* CONFIRMED FOR: NEWTON
* CONFIRMED FOR: MITAKA
* CONFIRMED FOR: LIBERTY
On 23.05.2
A reminder that this will happen in ~2 weeks.
Please note that you can spare bug reports if you leave a comment there
which says one of these (case-sensitive flags):
* CONFIRMED FOR: NEWTON
* CONFIRMED FOR: MITAKA
* CONFIRMED FOR: LIBERTY
On 23.05.2016 13:02, Markus Zoeller wrote:
> TL;DR: Automa
On 5/31/2016 7:35 AM, Sean Dague wrote:
On 05/30/2016 04:02 PM, Shoham Peller wrote:
I support Clint's comment, and as an example, only today I was able to
search a bug and to see it was reported 2 years ago and wasn't solved since.
I've commented on the bug saying it happened to me in an up-to-
On 05/30/2016 04:02 PM, Shoham Peller wrote:
> I support Clint's comment, and as an example, only today I was able to
> search a bug and to see it was reported 2 years ago and wasn't solved since.
> I've commented on the bug saying it happened to me in an up-to-date nova.
> I'm talking about a bug
On 05/30/2016 02:37 PM, Clint Byrum wrote:
> (Top posting as a general reply to the thread)
>
> Bugs are precious data. As much as it feels like the bug list is full of
> cruft that won't ever get touched, one thing that we might be missing in
> doing this is that the user who encounters the bug a
Clint Byrum wrote:
I 100% support those who are managing bugs doing whatever they need
to do to make sure users' issues are being addressed as well as can be
done with the resources available. However, I would also urge everyone
to remember that the bug tracker is not only a way for developers to
On 24 May 2016 at 18:05, Doug Hellmann wrote:
> Excerpts from Markus Zoeller's message of 2016-05-24 11:00:35 +0200:
> > On 24.05.2016 09:34, Duncan Thomas wrote:
> > > Cinder bugs list was far more manageable once this had been done.
> > >
> > > It is worth sharing the tool for this? I realise i
I support Clint's comment, and as an example, only today I was able to
search a bug and to see it was reported 2 years ago and wasn't solved since.
I've commented on the bug saying it happened to me in an up-to-date nova.
I'm talking about a bug which is on your list -
https://bugs.launchpad.net/no
(Top posting as a general reply to the thread)
Bugs are precious data. As much as it feels like the bug list is full of
cruft that won't ever get touched, one thing that we might be missing in
doing this is that the user who encounters the bug and takes the time
to actually find the bug tracker an
On 24.05.2016 19:05, Doug Hellmann wrote:
> Excerpts from Markus Zoeller's message of 2016-05-24 11:00:35 +0200:
>> On 24.05.2016 09:34, Duncan Thomas wrote:
>>> Cinder bugs list was far more manageable once this had been done.
>>>
>>> It is worth sharing the tool for this? I realise it's fairly tr
Excerpts from Markus Zoeller's message of 2016-05-24 11:00:35 +0200:
> On 24.05.2016 09:34, Duncan Thomas wrote:
> > Cinder bugs list was far more manageable once this had been done.
> >
> > It is worth sharing the tool for this? I realise it's fairly trivial to
> > write one, but some standardisa
On Tue, May 24, 2016 at 1:34 AM, Duncan Thomas
wrote:
> Cinder bugs list was far more manageable once this had been done.
>
> It is worth sharing the tool for this? I realise it's fairly trivial to
> write one, but some standardisation on the comment format etc seems
> valuable, particularly for
On Tue, May 24, 2016 at 11:00:35AM +0200, Markus Zoeller wrote:
> On 24.05.2016 09:34, Duncan Thomas wrote:
> > Cinder bugs list was far more manageable once this had been done.
> >
> > It is worth sharing the tool for this? I realise it's fairly trivial to
> > write one, but some standardisation
On 24.05.2016 09:34, Duncan Thomas wrote:
> Cinder bugs list was far more manageable once this had been done.
>
> It is worth sharing the tool for this? I realise it's fairly trivial to
> write one, but some standardisation on the comment format etc seems
> valuable, particularly for Q/A folks who
Cinder bugs list was far more manageable once this had been done.
It is worth sharing the tool for this? I realise it's fairly trivial to
write one, but some standardisation on the comment format etc seems
valuable, particularly for Q/A folks who work between different projects.
On 23 May 2016 at
On Mon, May 23, 2016 at 01:02:29PM +0200, Markus Zoeller wrote:
> TL;DR: Automatic closing of 185 bug reports which are older than 18
> months in the week R-13. Skipping specific bug reports is possible. A
> bug report comment explains the reasons.
FWIW, I did the same thing in Cinder a while back
TL;DR: Automatic closing of 185 bug reports which are older than 18
months in the week R-13. Skipping specific bug reports is possible. A
bug report comment explains the reasons.
I'd like to get rid of more clutter in our bug list to make it more
comprehensible by a human being. For this, I'm tar
19 matches
Mail list logo