Re: Using Bugzilla for freeze break requests?
- From: Ross Burton <ross burtonini com>
- To: Ross Burton <ross burtonini com>, Bastien Nocera <hadess hadess net>, Desktop Hackers <desktop-devel-list gnome org>, Translation Team <gnome-i18n gnome org>, gnome-doc-list <gnome-doc-list gnome org>, release-team <release-team gnome org>
- Subject: Re: Using Bugzilla for freeze break requests?
- Date: Fri, 23 Sep 2011 11:30:31 +0100
On 23 September 2011 10:58, Olav Vitters <olav vitters nl> wrote:
>> For what it's worth this is exactly what we do in MeeGo for
>> distribution freezes and we find it works very well.
> Do you have multiple freezes? Do you use one flag or multiple? How do
> you handle multiple teams and e.g. one flag?
We have a single freeze which does make things easier. There is a
group of people who can approve the flag, they all have rights to it
and we rely on clue so e.g. the netbook approver doesn't approve
> My idea would be:
> * 1 flag, freeze_break
> * 3 teams having access to grant/deny (i18n+docs+r/t)
> with a limited amount of people we'd just rely on awareness instead of
> technical solutions. E.g. i18n team should not mark a break as
> 'approved' if we're in hard code freeze
> * only people marked as developers being able to request (simply to avoid
> confusing random users with a flag option)
Agreed that this alternative would be more sensible than presenting
multiple flags. If you require that people explain what their change
does so the approvers understand what freezes are being broken, then
it should become automatically peer reviewed if say the i18n team
approved a code change.
] [Thread Prev