[Cosmo-dev] Bug Council process for Cosmo

[Matthew Eernisse]

+1, excellent plan.

Ted Leung wrote:
> Hi folks,
> 
> This came up several times today in IRC, and in fact over the last few 
> days, where we are finding various small bugs.   Some of these bugs are 
> code level fixes only, and others are small, easy to fix and low 
> impact.   It seems wasteful to have developers waiting until the bug 
> council can meet, even if the bug council is meeting the next day.   I'd 
> like to propose a way to make the bug council process a little more 
> lightweight and less reliant on a synchronous meeting.
> 
> Bugs can be marked as blocking if myself, and someone from QA (anyone 
> from QA) can be convinced that the bug should be a blocker.   If we feel 
> that the bug may impact end user or product level features, then we will 
> involve someone from PPD and/or Jared before granting blocking status.
> Discussion of such bugs can occur in any medium, although an archived 
> medium such as e-mail or IRC is preferred.
> 
> These bugs should be tracked like any other bug -- that is, no checkin 
> without a bug number.  If discussion of the bug took place in IRC, then 
> the bug report should note that the discussion happened, summarize the 
> reasoning  (ideally it would link to the appropriate section of the IRC 
> log, but this is not mandatory) and list the names of the people who 
> approved blocking status.
> 
> Thoughts?
> 
> Ted
> 
> 
> _______________________________________________
> cosmo-dev mailing list
> cosmo-dev at lists.osafoundation.org
> http://lists.osafoundation.org/mailman/listinfo/cosmo-dev
>