Uh. I forgot to Reply All. Here are my reply and ermo's answer to my question.
On Wed, Mar 30, 2011 at 4:27 PM, Jesse Zhang <zh.je...@gmail.com> wrote: > On Wed, Mar 30, 2011 at 10:07 PM, Rune Morling <e...@foresightlinux.org> > wrote: >> Realistically, everything before 2.1.1 and 2.1.2 should probably be retired. >> >> Last I looked, it seemed that issues belonging to a retired version >> would be left to rot basically. We did a major cleanup sprint where >> we went through many of the stale issues and re-assigned them to the >> proper release versions, so it might be worthwhile to go through the >> 2.0.x list and see if any of the issues there are still present in >> 2.5.x before we retire them completely. ISTR that our last cleanup >> digged up quite a few unaddressed bugs that we subsequently fixed. > > Then let's clean it up. I can have a look when I get tired on other things :) > > You want to first update all the issues (that belong to retired > versions), and then delete the version once it has no open issues? > > jesse > That was how we did it the last time. The point is that some of the issues are likely already resolved and others are likely invalid, but there is likely also a minority of issues that can be carried over from 2.0.x to 2.5.x because the issue in question still needs fixing. ermo _______________________________________________ Foresight-devel mailing list Foresight-devel@lists.rpath.org http://lists.rpath.org/mailman/listinfo/foresight-devel
