Hi Saros Developers, I just read the content on our webpage: http://www.saros-project.org/TicketGuidelines and I really wonder how this fits into a good development process.
Prio: 9 ... well this can only happen if we release a version with a major bug and so a re-release is needed. For Prio 7 - 8 ... well this is straight forward but: We have a new tracker system that let us define milestones / groups and so we can organize those groups and put the bugs into them that we want have to be fixed in the next release (milestone). And so comes Prio 2 - 5 (leaving out 6). If they are not used how should a developer / project lead decide which bugs should be put into the due list (next milestone) ? I do not think that those guidelines help to improve our product as we do not have an indicator on which bugs we should spend our focus ... according to this guide nearly every bug will have Prio 6 = Should be fixed some day which is ***************. BR, Stefan ------------------------------------------------------------------------------ October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60134071&iu=/4140/ostg.clktrk _______________________________________________ DPP-Devel mailing list DPP-Devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dpp-devel
