On Mon, 2010-05-24 at 17:21 +0200, ermo | Rune Morling wrote: > Everyone, > > As part of the ongoing FITS and Wiki cleanup, I have created a set of > filters[1] to help us weed out really old issues. > > I would encourage everyone to add all the (FL) and Dash: filters to > their favourite list, which is displayed on the front page of the new > default FITS dashboard. > > In the interest of archiving obsolete FL versions in FITS, I propose > that we focus on the Dash: FL 1.4.x bug raid and the > Dash: FL 1.9.9.x bug raid filters over the next week or so. Once they're > taken care of, I propose that we take a good, hard look at the Dash: FL > 2.0.x bug raid -- I wouldn't be surprised if it turns out that there is > a significant overlap with the (FL) Open Issues - Not Triaged filter. > > > Cheers, > > /ermo > > [1] public FITS search filters: > http://issues.foresightlinux.org/secure/ManageFilters.jspa?filterView=search&searchName=&searchOwnerUserName=&searchShareType=any&groupShare=confluence-administrators&projectShare=10061&roleShare=&Search=Search >
I'm proud to announce that, thanks to the efforts of the dedicated and all around excellent Foresight Linux contributors and developers, the FL 1.9.9.x bug raid has been completed with plenty of bugs closed! I have updated the filters slightly, so you are all encouraged to revisit the above link and add the new shared filters to your favourite list. The completion of the first two bug raids means that we can now turn our attention fully to the FL 2.0.x bug raid, which has already seen significant work. I would suggest going over the issue list in ascending issue order (i.e. oldest to newest) and concentrate on pruning from the list all the issues that have already been fixed as part of the normal update cycle. In particular, it would be great if you could re-assign issues assigned to Ken, Paul or António to Distro so that having an issue assigned can again actually mean that it gets worked on and doesn't just sit there and bitrot. The goal of this dash/sprint/milestone is to get FITS into a state where we can trust that the issues reported from now on are triaged in a timely fashion and that potential users and contributors again begin to perceive us as being an active and conscientous community. If you have questions, comments or suggestions for improvements for the FITS workflow, do not hesitate to get in touch with me either her or on IRC in #foresight-devel or #foresight-qa. Let's go zap some bugs, shall we? /ermo _______________________________________________ Foresight-devel mailing list Foresight-devel@lists.rpath.org http://lists.rpath.org/mailman/listinfo/foresight-devel
