of the request.
After having talked to Olav Vitters at FOSDEM I (or we?) would like to
propose using Bugzilla flags for freeze break requests in GNOME 3.5.
Personally I consider keywords too cumbersome plus too easy to forget.
Please also read Olav's initial comments on this thread again:
https
about the freeze break request,
or about the status of the request.
After having talked to Olav Vitters at FOSDEM I (or we?) would like to
propose using Bugzilla flags for freeze break requests in GNOME 3.5.
Awesome!
Personally I consider keywords too cumbersome plus too easy to forget
On Fri, Sep 23, 2011 at 09:53, Baptiste Mille-Mathias
baptiste.millemath...@gmail.com wrote:
On Fri, Sep 23, 2011 at 9:40 AM, Olav Vitters o...@vitters.nl wrote:
On Thu, Sep 22, 2011 at 10:44:32PM +0100, Bastien Nocera wrote:
I think that, at the very least for GNOME 3.4 onwards, we should
Op Vr, 2011-09-23 om 10:11 +0200 skryf Jorge González:
On Fri, Sep 23, 2011 at 09:53, Baptiste Mille-Mathias
baptiste.millemath...@gmail.com wrote:
On Fri, Sep 23, 2011 at 9:40 AM, Olav Vitters o...@vitters.nl wrote:
On Thu, Sep 22, 2011 at 10:44:32PM +0100, Bastien Nocera wrote:
...
As
On Thu, Sep 22, 2011 at 10:44:32PM +0100, Bastien Nocera wrote:
I think that, at the very least for GNOME 3.4 onwards, we should switch
to using a keyword in bugzilla, and the release-team, docs team and i18n
teams can monitor newly request breaks, through RSS feeds (the design
team does
On Fri, Sep 23, 2011 at 9:40 AM, Olav Vitters o...@vitters.nl wrote:
On Thu, Sep 22, 2011 at 10:44:32PM +0100, Bastien Nocera wrote:
I think that, at the very least for GNOME 3.4 onwards, we should switch
to using a keyword in bugzilla, and the release-team, docs team and i18n
teams can
On Fri, Sep 23, 2011 at 10:11:13AM +0200, Jorge González wrote:
There could be a shared calendar. I have my own to know when we
release and when are we in string freeze and such. It's very easy.
http://www.gnome.org/start/unstable/schedule.ics
webcal://www.gnome.org/start/unstable/schedule.ics
On 23 September 2011 08:40, Olav Vitters o...@vitters.nl wrote:
The Bugzilla way of doing this is to use flags. A flag is either defined
for attachments _or_ (not and) bugs. This is possible on our currently
bugzilla; we just do not use them.
For what it's worth this is exactly what we do in
On Fri, Sep 23, 2011 at 09:57:15AM +0100, Ross Burton wrote:
On 23 September 2011 08:40, Olav Vitters o...@vitters.nl wrote:
The Bugzilla way of doing this is to use flags. A flag is either defined
for attachments _or_ (not and) bugs. This is possible on our currently
bugzilla; we just do
On 23 September 2011 10:58, Olav Vitters o...@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?
On Fri, 2011-09-23 at 09:40 +0200, Olav Vitters wrote:
On Thu, Sep 22, 2011 at 10:44:32PM +0100, Bastien Nocera wrote:
I think that, at the very least for GNOME 3.4 onwards, we should switch
to using a keyword in bugzilla, and the release-team, docs team and i18n
teams can monitor newly
On Fri, Sep 23, 2011 at 12:51:04PM +0100, Bastien Nocera wrote:
Here's the workflow with a keyword:
1. Developer adds a patch to an important bug, and realises that the
patch needs to make it to stable during a freeze (possibly through a
banner, auto-updated via ical)
2. Developer adds
On 09/23/2011 07:58 AM, Olav Vitters wrote:
I think that will add too much burden on the people who have to approve?
I don't track RSS at all. Release-team gets a lot of freeze breaks and I
want to be notified immediately, not after a delay. I need to see the
comments that other teams make
On Thu, 2011-09-22 at 21:24 -0400, Shaun McCance wrote:
On Thu, 2011-09-22 at 22:44 +0100, Bastien Nocera wrote:
I think that, at the very least for GNOME 3.4 onwards, we should switch
to using a keyword in bugzilla, and the release-team, docs team and i18n
teams can monitor newly request
Hi!
Instead of keywords, we could just add bugzilla pseudo accounts for
string-freeze-br...@gnome.bugs, ui-freeze-br...@gnome.bugs,
code-freeze-br...@gnome.bugs. Then to request a break, just cc: the
appropriate address on the bug along with a comment explaining why.
Release/docs/i18n team
Heya,
After having to send in another code freeze break request e-mail, I
realised that the process is problematic. Apart from the release team
and the patch sender, nobody else knows about the freeze break request,
or about the status of the request.
I think that, at the very least for GNOME
On Thu, 2011-09-22 at 22:44 +0100, Bastien Nocera wrote:
Heya,
After having to send in another code freeze break request e-mail, I
realised that the process is problematic. Apart from the release team
and the patch sender, nobody else knows about the freeze break request,
or about the
On Thu, Sep 22, 2011 at 5:44 PM, Bastien Nocera had...@hadess.net wrote:
Heya,
After having to send in another code freeze break request e-mail, I
realised that the process is problematic. Apart from the release team
and the patch sender, nobody else knows about the freeze break request,
or
On Thu, 2011-09-22 at 18:28 -0400, Matthias Clasen wrote:
On Thu, Sep 22, 2011 at 5:44 PM, Bastien Nocera had...@hadess.net wrote:
Heya,
After having to send in another code freeze break request e-mail, I
realised that the process is problematic. Apart from the release team
and the
On Thu, 2011-09-22 at 22:44 +0100, Bastien Nocera wrote:
Heya,
After having to send in another code freeze break request e-mail, I
realised that the process is problematic. Apart from the release team
and the patch sender, nobody else knows about the freeze break request,
or about the
20 matches
Mail list logo
