[cmake-developers] Pushing to next and closing bugs?

Alexander Neundorf neundorf at kde.org
Tue Jul 27 16:16:46 EDT 2010


On Tuesday 06 July 2010, Eric Noulard wrote:
> 2010/7/5 Bill Hoffman <bill.hoffman at kitware.com>:>
>
> > So, although not perfect, I prefer to close the bug when it is checked in
> > to next.   My reason is that we have wayyyy too many bugs open as it is.
> >  I don't want to have to wait on the reporter to close it, as often times
> > they have lost interest and gone away never to come back anyway. They can
> > always reopen it as they often do.
>
> Ok then, may be setting the bug to resolved when in next
> and close it when merged in master would be better?
> That way the Reporter may get a chance to confirm the fix is OK and
> we are sure that if ever the next-->master switch does not occur
> (for any reason) we do not claim to have fixed the bug if it is not in
> any release.

As Bill also said, I wouldn't rely on the bug reporter for this. And I would 
also prefer not having to rely on myself to remember to change the bug 
from "Resolved" to "Closed" when the patch is merged from next into master.

Alex



More information about the cmake-developers mailing list