not aware of). Here goes:
Original Message
Subject: Re: [cmake-developers] ReactOS: Important filed bug reports
went to backlog en masse
Date: Mon, 13 Aug 2012 15:30:34 +0100
From: Amine Khaldi amine.kha...@reactos.org
To: David Cole david.c...@kitware.com
Hi
An update and clarification of one of my simple facts: :-)
- There are presently 1,207 open issues in the CMake bug tracker,
but open in this number also includes already resolved bugs, of which
there are presently 193.
So, really, there are 1,014 open issues that require work to resolve
This was actually my exact intent (to re-involve the original
reporters via the notification system, since nobody else has picked up
on the bugs enough to assign them), and this was just step 1.
The bug tracker's roadmap page and what bugs are actually assigned to
active CMake developers are two
On 2012-08-13 06:54-0400 David Cole wrote:
This was actually my exact intent (to re-involve the original
reporters via the notification system, since nobody else has picked up
on the bugs enough to assign them), and this was just step 1.
The bug tracker's roadmap page and what bugs are
On Mon, Aug 13, 2012 at 3:37 PM, Alan W. Irwin
ir...@beluga.phys.uvic.ca wrote:
On 2012-08-13 06:54-0400 David Cole wrote:
This was actually my exact intent (to re-involve the original
reporters via the notification system, since nobody else has picked up
on the bugs enough to assign them),
Here are some simple facts:
- There are presently 1,204 open issues in the CMake bug tracker.
- We averaged 111 days per release from CMake 2.8.1 to CMake 2.8.9.
- Each release contained an average of 79 bug fixes from 2.8.3 to 2.8.9.
Hence.. I have a strong desire to focus in on
On 2012-08-13 17:23-0400 David Cole wrote:
I realize that this is a touchy subject, and tried very hard to word
my messages that went along with this action to make it very clear
that putting a bug into the 'backlog' is not in the least bit
permanent.
I think the politics of this could be
Just idly, I wonder how practical it would be to automatically close
bugs older than XXX time that haven't been touched or assigned.
If nothing else it'd generate a notification to the submitter of the
bug that either the bug was over looked or not considered important
and deserves some
Hello folks,
I would like to mention that many (if not all) the bugs coming from us
(ReactOS) got into backlog.
We're an operating system project, we try to file bug report only for
issues that block us, so we do not tend to file trivial bugs.
It would be great if the CMake folks tried to
