[CMake] CMake bug tracker discussion

[Alexander Neundorf]

On Friday 10 December 2010, Alan W. Irwin wrote:
> On 2010-12-10 17:01+0100 Pau Garcia i Quiles wrote:
> > On Fri, Dec 10, 2010 at 3:42 PM, Bill Hoffman <bill.hoffman at 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.
>
> I completely agree.  Time-based automatic bug closing is a bad idea.
>
> > On the other hand, on KDE, when we moved to KDE4, we closed almost all
> > KDE3-related bugs without checking if they had been fixed. It did not
> > made too much sense to keep bug reports around unless they were
> > feature requests.
>
> That sounds like you would support version-based (as opposed to
> time-based) bug report closing.

The switch from KDE3 to KDE4 involved a major rewrite, so there it made sense 
to close the KDE3 ones.
CMake doesn't have a major rewrite currently, so the situation is different 
here.

Alex