I brainstormed a bit today and I came up with this flowchart. Looking for input. I read through email threads and see that prioritizing bugs has been an interesting discussion but as of now looks to be pretty unsettled. I'm going to make a similar chart for myself for setting bugs status. These kinds of things help me, not sure if they help others, but if they do, feel free to comment :) This is meant as a general guideline, possibly to put up on the wiki for future and current QA/Devs to have a bit of focus. It's NOT meant to be me forcing everyone to conform as I know that QA requires quite a bit of discretion. Thanks to all of you for your continued hard work on this project :) Joel On Wed, Jun 13, 2012 at 9:11 AM, Joel Madero <jmadero.dev@gmail.com> wrote:
Sure thing. As soon as I do what I'm considering "Phase 1" (just changing from UNCONFIRMED to NEEDINFO or NOTOURBUG) I'll be moving to the second phase which is to prioritize. I'll bookmark those links, appreciate the heads up. It would be nice if we could get 2-3 people to just pound through them and focus on nothing else until they are done but I know that's wishful thinking. My goal is to do 200 a week, that's still 5 months worth of sorting just for phase 1 :( But, progress is progress and once it's done we'll all be able to tackle these bugs a bit easier. Joel P.S. I still really think we need a CONFIRMED status so that devs don't have to look at UNCONFIRMED bugs or at least don't have to always look at them. I've voiced this a few times but I think I may be the only one On Wed, Jun 13, 2012 at 8:42 AM, Petr Mladek <pmladek@suse.cz> wrote:Hi Joel, your plans are great. On Thu, 2012-06-07 at 23:49 -0700, Joel Madero wrote:With thousands of unknown bugs I think that this will help us divvy up the work and prioritize a bit. After I do this phase I'll try to get consensus on how to prioritize. Obviously security bugs and resource leaks get highest, next I'm not sure but we can discuss this after.Just a side note. Some proposals of bug priorities were discussed in another thread, see: http://lists.freedesktop.org/archives/libreoffice/2012-June/032776.html http://lists.freedesktop.org/archives/libreoffice/2012-June/033011.html My opinion is that some prioritization would be highly appreciated. In each case, we should not fight about each bug. The severity and priority is just a helper information. It could motivate but it can't force volunteers to work on the bugs. Too many comments that does not bring any new information makes bugs less readable and worse to handle :-) Thanks for helping with sorting the bugs. Best Regards, Petr
Attachment:
Prioritizing Bugs FlowChart.pdf
Description: Adobe PDF document
Attachment:
Prioritizing Bugs FlowChart.odg
Description: application/vnd.oasis.opendocument.graphics