From: Till S. <til...@tu...> - 2013-10-24 16:03:22
|
Hi everyone, in the source forge tracker for bugs and wishes, we had a mess of different milestones. Many bugs were assigned to milestone which were released long time ago. We used to have milestones like "2.2.x", which leads to the situation, that old bugs that are not fixed in 2.2.x have to be manually updated to 2.3.x. As SF does not support batch processing, this was nearly never done. I have created a new milestone "any future version" in the sf-tracker, which should be used for any new bug and wish. This will avoid the above situation, where the bugs have to be moved to new milestones. We will move the bugs to a specific version now only for concrete planing. That means, if we want to release a new version and are planing which bugs should be fixed before the release, we will move this bug to the specific version. Sorry to the peoples that are receiving change notification for the bugs and have received all that change spam from reassigning every single bug to a new milestone. Greetings Till -- Dipl.-Inf. Till Schäfer Technische Universität Dortmund Chair 11 - Algorithm Engineering Otto-Hahn-Str. 14 / Raum 237 44227 Dortmund, Germany e-mail: til...@cs... phone: +49(231)755-7706 fax: +49(231)755-7740 web: http://ls11-www.cs.uni-dortmund.de/staff/schaefer pgp: https://keyserver2.pgp.com/vkd/SubmitSearch.event?&&SearchCriteria=0xD84DED79 |