On 12/10/2010 11:01 AM, Pau Garcia i Quiles wrote:
On Fri, Dec 10, 2010 at 3:42 PM, Bill Hoffman<bill.hoff...@kitware.com> wrote:
I have a third idea that we have not yet tried:
What do people think of automatically closing bugs if they are not modified
for some period of time (say 6 months). They can always be reopened if the
closed. By closing them, it will notify those that have expressed interest
in the bug. We could send the closed bugs to the cmake-developer list just
like the new ones. That way all developers will know that they are being
closed.
It's a bad idea, IMHO.
If a user took the time to file a bug and CMake developers do nothing
in 6 months, closing it is the wrong thing to do.
The message you are sending to the bugreporter is "I didn't care about
the bug you reported in 6 months, and now I will care even less". For
an example, see what I said yesterday about bug 8707: two years later,
a patch provided, still no action on Kitware's side.
Right, and by closing that bug after six months with a message like: "If
you are still interested in this issue, please re-open and comment. You
may want to bring this issue up on the CMake mailing list as well."
I am thinking that issues like 8707 would not be forgotten because they
would be re-opened and eventually addressed. So, by closing the issue,
it would keep the issues from getting stale.
-Bill
_______________________________________________
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://www.cmake.org/mailman/listinfo/cmake
