[meego-releases] Handling of Release / Update Blocker requests in MeeGo Bugzilla
jeremiah.foster at pelagicore.com
Thu Jun 23 04:18:23 PDT 2011
On Tue, Jun 21, 2011 at 11:13 PM, Selbak, Rolla N
<rolla.n.selbak at intel.com> wrote:
> On 6/21/11 9:46 AM, "Andre Klapper" <aklapper at openismus.com> wrote:
>>[Reposting for a second time as I still have not received an answer to
>>this by MeeGo's Release Engineering team in the last two weeks.]
>>I was wondering who actually makes the decisions on tickets in
>>bugs.meego.com with "MeeGo_Release_Blocker requested" and
>>"MeeGo_Update_Release_Blocker requested" flags.
>>Rolla N Selbak states in  that
>>"Release Engineering gathers feedback from Program Management and
>>Development teams as to which bugs should be accepted or rejected."
>>"Release Engineering sets bugs to 'accepted' or 'rejected', depending on
>>the feedback given."
> Yes, this is correct.
>>This raises the following questions:
>> * How is the feedback from PM and dev teams gathered? Does this
>> happen in the corresponding bug reports by adding comments? If
>> it is handled differently, how can I follow these discussions?
> Yes, discussions can happen within the bugzillas themselves, through the
> mailing lists, etc.
When you say "etc." does this also include closed mailing lists, i.e.
internal corporate mailing lists? If the answer is yes, I might argue
that internal corporate lists stand in stark contrast to how Open
Source projects traditionally work. Is it possible for the
communication channels to be defined and adhered to so that at least
the community knows that there might be communication they are not
>> * I think I have seen people deciding on release blocker requests
>> that are not listed on the wikipage. Does the list need an
> Sometimes, a PM will set the blocker flag to accept/reject after a
> decision has been made, and that is probably what you are seeing.
> But the general process is that Release Engineering should flip the switch.
>> * Assuming that the group of people indeed has been extended in
>> the meantime: What is the process for adding more/new people to
>> Release Management, where is it discussed, and where is that
>> process documented? Maybe I just did not find the corresponding
> Release Engineering is currently not looking for new candidates for Meego,
> although we always appreciate feedback and support.
But that would imply that there is one central decision making body
for Meego and not an open community of decision makers. Is this the
case? Is "Release Engineering" a closed body?
>> * The differentiation between Release Management and the Change
>> Control Board (CCB) is not very clear to me. Could somebody
>> elaborate? Also how would I contact the CCB folks?
> CCB folks include Release Engineering, PMs and key developers.
> If you have a question about a certain bug you would like to discuss,
> email the meego-packaging mailing list so we can discuss together
More information about the MeeGo-releases