Suggestions: * Let's go through all reports until Dec 31, 2010 (to have a clear boundary). * Comment on each report, even it is still valid, so that we do not do duplicate work * Start with the oldest ones ;) Nearly 80 % of all reports are from 2009.
2010/4/1 Hugh Tebby <hugh.tebby at gmail.com>: > I'll probably have a go at cleaning up next week-end, maybe even during the > week if I have a bit of time in the evenings. > > First objective : get the bug count down by 100 ! > > > 2010/4/1 Simon Eugster <simon.eu at gmail.com> >> >> 2010/4/1 Albert ARIBAUD <albert.aribaud at free.fr>: >> > To speed things up, I can already tell bug 436 is still relevant. :) >> >> Yeah, that's gonna speed up the process a lot :) >> >> I agree that a cleanup is necessary. >> Perhaps I might even have time to help next week. >> >> Simon >> >> >> ------------------------------------------------------------------------------ >> Download Intel® Parallel Studio Eval >> Try the new software tools for yourself. Speed compiling, find bugs >> proactively, and fine-tune applications for parallel performance. >> See why Intel Parallel Studio got high marks during beta. >> http://p.sf.net/sfu/intel-sw-dev >> _______________________________________________ >> Kdenlive-devel mailing list >> Kdenlive-devel at lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/kdenlive-devel > > > ------------------------------------------------------------------------------ > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > _______________________________________________ > Kdenlive-devel mailing list > Kdenlive-devel at lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/kdenlive-devel > >
