Re: [cmake-developers] The CMake bug tracker and the backlog of unresolved issues
On Thu, Mar 10, 2011 at 3:17 PM, Alexander Neundorf neund...@kde.orgwrote: On Friday 04 February 2011, David Cole wrote: On Fri, Feb 4, 2011 at 4:22 AM, Eric Noulard eric.noul...@gmail.com wrote: 2011/2/4 Michael Wild them...@gmail.com: You could actually add a backlog status by customising the configuration: http://manual.mantisbt.org/manual.customizing.mantis.customizing.status.v alues.php This would be IMHO much less confusing and also much easier to use when searching/filtering. +1 I agree with Michael, my previous proposal assumed you (Kitware) were not willing to change your Mantis config for whatever reason. -- Erk Membre de l'April - « promouvoir et défendre le logiciel libre » - http://www.april.org ___ cmake-developers mailing list cmake-developers@cmake.org http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers Thanks for the feedback, guys. The problem is that we share the mantis tracker with several open source projects. I'll ask around today and see if anybody minds adding a backlog status to *all* our projects. (Or maybe it's possible to add a custom status value just for the CMake project...?) So, if I have an issue assigned to me which I don't feel like working on in the forseeable future I should assign it to nobody and set it to backlog ? Alex ___ cmake-developers mailing list cmake-developers@cmake.org http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers Yes... That would be good. Although, if it's just that you don't feel like working on it, but it may be important, perhaps you should point us all to it and ask if any of us wants to take it instead. Thanks, David ___ cmake-developers mailing list cmake-developers@cmake.org http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
Re: [cmake-developers] The CMake bug tracker and the backlog of unresolved issues
On Thu, Mar 10, 2011 at 3:21 PM, David Cole david.c...@kitware.com wrote: On Thu, Mar 10, 2011 at 3:17 PM, Alexander Neundorf neund...@kde.orgwrote: On Friday 04 February 2011, David Cole wrote: On Fri, Feb 4, 2011 at 4:22 AM, Eric Noulard eric.noul...@gmail.com wrote: 2011/2/4 Michael Wild them...@gmail.com: You could actually add a backlog status by customising the configuration: http://manual.mantisbt.org/manual.customizing.mantis.customizing.status.v alues.php This would be IMHO much less confusing and also much easier to use when searching/filtering. +1 I agree with Michael, my previous proposal assumed you (Kitware) were not willing to change your Mantis config for whatever reason. -- Erk Membre de l'April - « promouvoir et défendre le logiciel libre » - http://www.april.org ___ cmake-developers mailing list cmake-developers@cmake.org http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers Thanks for the feedback, guys. The problem is that we share the mantis tracker with several open source projects. I'll ask around today and see if anybody minds adding a backlog status to *all* our projects. (Or maybe it's possible to add a custom status value just for the CMake project...?) So, if I have an issue assigned to me which I don't feel like working on in the forseeable future I should assign it to nobody and set it to backlog ? Alex ___ cmake-developers mailing list cmake-developers@cmake.org http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers Yes... That would be good. Although, if it's just that you don't feel like working on it, but it may be important, perhaps you should point us all to it and ask if any of us wants to take it instead. Thanks, David To put something into the backlog officially: - set its status to backlog - assign it to (nobody...) One can always look at the history of the bug if necessary to figure out who it used to be assigned to, if anyone. ___ cmake-developers mailing list cmake-developers@cmake.org http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
Re: [cmake-developers] The CMake bug tracker and the backlog of unresolved issues
2011/2/4 Michael Wild them...@gmail.com: You could actually add a backlog status by customising the configuration: http://manual.mantisbt.org/manual.customizing.mantis.customizing.status.values.php This would be IMHO much less confusing and also much easier to use when searching/filtering. +1 I agree with Michael, my previous proposal assumed you (Kitware) were not willing to change your Mantis config for whatever reason. -- Erk Membre de l'April - « promouvoir et défendre le logiciel libre » - http://www.april.org ___ cmake-developers mailing list cmake-developers@cmake.org http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
Re: [cmake-developers] The CMake bug tracker and the backlog of unresolved issues
On Fri, Feb 4, 2011 at 4:22 AM, Eric Noulard eric.noul...@gmail.com wrote: 2011/2/4 Michael Wild them...@gmail.com: You could actually add a backlog status by customising the configuration: http://manual.mantisbt.org/manual.customizing.mantis.customizing.status.values.php This would be IMHO much less confusing and also much easier to use when searching/filtering. +1 I agree with Michael, my previous proposal assumed you (Kitware) were not willing to change your Mantis config for whatever reason. -- Erk Membre de l'April - « promouvoir et défendre le logiciel libre » - http://www.april.org ___ cmake-developers mailing list cmake-developers@cmake.org http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers Thanks for the feedback, guys. The problem is that we share the mantis tracker with several open source projects. I'll ask around today and see if anybody minds adding a backlog status to *all* our projects. (Or maybe it's possible to add a custom status value just for the CMake project...?) Cheers, David ___ cmake-developers mailing list cmake-developers@cmake.org http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
[cmake-developers] The CMake bug tracker and the backlog of unresolved issues
Hello CMakers, The CMake issue tracker is located at: http://public.kitware.com/Bug All of the issues except for the most recent 15 or so have been assigned and looked at by at least one CMake developer at one point in each issue's history. However, not all issues that are assigned to developers are being actively worked on. Personally, I have just over 100 issues assigned to me, and I know it would take me on the order of months to work through all of them, even if I were able to work on them full time. I would like very much for us to introduce the notion of a backlog in the CMake bug tracker, where we can send bugs that are not being actively worked on, and we can review the backlog periodically for issues that should be brought forward into active development again. Since we do not have a status of backlog -- but we don't really use the status values of acknowledged or confirmed very much, I am thinking we could define backlog as: status=acknowledged AND assigned to= (empty string, none) As an exemplar, I just sent this one to the backlog by setting its status and de-assigning it: http://public.kitware.com/Bug/view.php?id=7867 Does this seem like a reasonable technique? Any comments or questions before we start sending more things to the backlog? When we send around the request (coming up soon, after the final 2.8.4 release is ready) to vote for your favorite issues... you'd still be able to vote for things in the backlog. And if we can find somebody willing to do the work, we'll assign it to them and set status=assigned again... Let me know what you think -- thanks for reading, David ___ cmake-developers mailing list cmake-developers@cmake.org http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
