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 resol
is must
> be some policy that I'm 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
>
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 cons
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 appr
On Mon, Aug 13, 2012 at 3:37 PM, Alan W. Irwin
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), and this was just s
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 actually
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 o
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 discussion
I certainly did not mean to offend anyone with my en masse move of
issues to 'backlog' -- thanks for speaking up.
I would like to make sure that you guys can continue to use CMake for
ReactOS. I've got to run right now, but I will reply again tomorrow
when I have some more time. Do you have time f
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 p
10 matches
Mail list logo
