[meego-releases] Handling of Release / Update Blocker requests in MeeGo Bugzilla
aklapper at openismus.com
Thu Jun 23 14:17:29 PDT 2011
On Tue, 2011-06-21 at 14:13 -0700, Selbak, Rolla N wrote:
> Thanks for your inquiry, and apologies for the late response.
No problem - guess we're all busy. :)
> >Rolla N Selbak states in  that
> >"Release Engineering sets bugs to 'accepted' or 'rejected', depending on
> >the feedback given."
> Yes, this is correct.
> > * 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.
So far in Bugzilla I mostly had the impression that decisions are just
made by changing the flag in a report without further comments
explaining it, and I have seen only a few discussions in Bugzilla and on
public mailing lists, but maybe I watch the wrong tickets and lists. :)
> > * I think I have seen people deciding on release blocker requests
> > that are not listed on the wikipage. Does the list need an
> > update?
> 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.
So above quoted statement "Release Engineering sets bugs to
'accepted' or 'rejected'" is incorrect as not only RE but also PMs
(Project management? Product management?) can set this?
Is there any way for me to find out which people in MeeGo actually are
I really miss a documentation of this process in the wiki (and that's
why I'm asking here), but after understanding it better I might give
that a try.
> > * 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
> > wikipage?
> Release Engineering is currently not looking for new candidates for Meego,
> although we always appreciate feedback and support.
I see. I'm member of the GNOME Release Team (r-t) and we don't let
people "apply" either for r-t membership; instead we watch out for good
candidates in our community and in case one of us plans to leave soon we
contact candidates. So what happens if one RE member plans to leave and
a replacement has to get found? Or has this simply not happened yet? :)
And as I consider different opinions and backgrounds helpful in a team
(in GNOME r-t we only allow 2 members from the same company), may I ask
how many different companies employ (or "are represented by") the six
MeeGo RE team members?
> CCB folks include Release Engineering, PMs and key developers.
As per "key developers" I assume that CCB is not a "well-defined" group
but quite open to anybody. Nice...
Thanks for your answers,
> > http://lists.meego.com/pipermail/meego-packaging/2011-May/247434.html
Andre Klapper (maemo.org bugmaster)
More information about the MeeGo-releases