On Tue, 14 Jun 2011 16:02:00 +0000, Fathi Boudra <fathi.bou...@linaro.org> wrote: > On 14 June 2011 15:36, James Westby <james.wes...@canonical.com> wrote: > > On Tue, 14 Jun 2011 15:23:13 +0000, Fathi Boudra <fathi.bou...@linaro.org> > > wrote: > >> * All bugs in a 'High' or 'Critical' state should be highlighted to the > >> Linaro > >> Release Team: Please, add it to the wiki page 'Bugs' section for the next > >> release meeting. The release meeting calendar can be found on the wiki. > >> Meetings are held on Thursday. If possible, attend the meeting. > > > > Why do we notify the release team both through editing a wiki page and > > subscribing the team? > > It's part of the previous process. It makes sure we have high/critical > bugs under the radar. > These bugs aren't qualified as release blocker yet (or even proposed). > > Do you think it's a duplicate effort and whatever a bug importance is, > it could be proposed? > In any case, the triage will be done at the Release Team level.
I think it's duplicate. I think there should be one method to put bugs on the release team radar, and it should be simple. If we are doing it purely based on importance of the bug then let's do it by reporting those bugs automatically, rather than having people manually move things over to a wiki page. I would personally like to have just the subscription method, and the release team to work from their subscribed bugs, raising things in the meeting if they need to be raised. Thanks, James _______________________________________________ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
