[cmake-developers] backlog status ?

David Cole david.cole at kitware.com
Wed May 25 16:01:05 EDT 2011


Yes. The purpose of the backlog status is to indicate that nobody will work
on it in the near future.

If you have bugs assigned to you that are not in the realm of your
expertise, then by all means, assign them to somebody else.

When putting bugs into the "backlog" you can either leave them assigned to
yourself (if you might come back to it eventually), or assign them to
"nobody".

Eventually, we will actively review the backlog periodically and activate
and assign bugs as people become available for making fixes. Or we can point
people who would like to "get involved" to the backlog and see if they are
able to pick anything off...


Thanks,
David


On Wed, May 25, 2011 at 3:44 PM, Alexander Neundorf <neundorf at kde.org>wrote:

> Hi,
>
> what was the exact purpose of the backlog status in the bugtracker ?
>
> I have a few issues assigned to me, where the reporter does not respond
> anymore, or where I don't have the time or feel qualified to work on them.
> So, a bunch of issues which make sense, but where I know I won't work on
> them
> in the near future.
>
> What should I do with them ?
> Just assign to nobody ?
> Which status should I gove them ? Backlog ?
>
> Alex
> _______________________________________________
> cmake-developers mailing list
> cmake-developers at cmake.org
> http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/cmake-developers/attachments/20110525/9d94e0e3/attachment.html>


More information about the cmake-developers mailing list