[cmake-developers] ReactOS: Important filed bug reports went to backlog en masse

David Cole david.cole at kitware.com
Mon Aug 13 06:54:27 EDT 2012


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 of the most important pieces of
information we can get from the bug tracker.

Having a bunch of bugs in there that nobody has ever looked at is just
as useless as allowing emails on the list to fall through the cracks
without any responses.

I intend to do the same thing with bugs that are actually assigned to
developers that have not been updated in the last 3 or 4 months. (If
it hasn't been updated, then it's not really "active"...) If you care
about a bug that's assigned to you, and want to get it fixed in CMake
2.8.10, please update it by adding a note by setting the Target
Version field and putting it on the roadmap page.

The ones that people really care about will be brought back. If nobody
cares about an issue, then it's not really an issue. The bug tracker
is an imperfect measurement of "care", but it's one of the closest
proxies that we have.


Thanks for your comments,
David


On Sun, Aug 12, 2012 at 9:36 PM, Doug <douglas.linder at gmail.com> wrote:
> 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 if they want it fixed.
>
> I've read a few articles online about doing this sort of thing to
> clear the 'fog' of irrelevant issues that clogs up bug trackers, esp.
> public ones.
>
> ~
> Doug.
>
> On Sun, Aug 12, 2012 at 8:10 PM, David Cole <david.cole at kitware.com> wrote:
>> 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 for a quick phone call or
>> Google+ hangout this week sometime, so I can understand better what
>> your issues are? (And why nobody adopted them when they appeared on
>> the mailing list in the form of your bug reports...)
>>
>>
>> Thanks,
>> David Cole
>>
>>
>> On Sat, Aug 11, 2012 at 9:42 PM, Amine Khaldi <amine.khaldi at reactos.org> wrote:
>>> 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 pay the attention that our
>>> issues deserve.. after all, we started using CMake because we read many
>>> positive reviews about the excellent support.
>>>
>>> Unfortunately, we're not able to use the VS generators due to the lack of
>>> support for ASM preprocessed files. We're not able to pass flags to C/C++
>>> source files without affecting the rc (resource) files. We're forced to do
>>> many ugly workarounds for the latter, and we found no solution for the
>>> former, and these are just examples.
>>>
>>> All these mentioned issues got into the backlog, so basically we're left
>>> off, without any help to get them solved.
>>>
>>> I'm writing this hopefully as a call to the CMake folks/community to address
>>> our issues, that we've been waiting release after release to get them fixed,
>>> only to find out that they ended up in backlog now.
>>>
>>> I'm writing this in the hopes of finding "a CMake developer who has the
>>> bandwidth to take it on, and ferry a fix through to our 'next' branch for
>>> dashboard testing".
>>>
>>> Regards,
>>> Amine.
>>> --
>>>
>>> Powered by www.kitware.com
>>>
>>> Visit other Kitware open-source projects at
>>> http://www.kitware.com/opensource/opensource.html
>>>
>>> Please keep messages on-topic and check the CMake FAQ at:
>>> http://www.cmake.org/Wiki/CMake_FAQ
>>>
>>> Follow this link to subscribe/unsubscribe:
>>> http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
>> --
>>
>> Powered by www.kitware.com
>>
>> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html
>>
>> Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ
>>
>> Follow this link to subscribe/unsubscribe:
>> http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
> --
>
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers



More information about the cmake-developers mailing list