A bugsquad even! Reprioritized most of mine yesterday...
Marco
On Mon, Feb 2, 2009 at 2:47 PM, Bernie Innocenti wrote:
> Marco Pesenti Gritti wrote:
>> I guess at some point the default was Blocker, because there lots of
>> tickets marked that way in trac.
>
> Yeah, we should re-prioritize them.
Marco Pesenti Gritti wrote:
> I guess at some point the default was Blocker, because there lots of
> tickets marked that way in trac.
Yeah, we should re-prioritize them. Do we have a Bugmaster role?
We should
/me steps back... quickly!
--
// Bernie Innocenti - http://www.codewiz.org/
\X/
On Mon, Feb 2, 2009 at 11:28 AM, Bernie Innocenti wrote:
> Tomeu Vizoso wrote:
>> I would say it's a blocker because that's the default value for that
>> field and the first person who modified the ticket (Marco) after those
>> fields were set up didn't explicitly set a different value.
>>
>> So n
Tomeu Vizoso wrote:
> I would say it's a blocker because that's the default value for that
> field and the first person who modified the ticket (Marco) after those
> fields were set up didn't explicitly set a different value.
>
> So not really a blocker, just a mistake.
The default severity is no
On Mon, Feb 2, 2009 at 09:44, Bernie Innocenti wrote:
> Why is this bug marked as Blocker?
>
> http://dev.sugarlabs.org/ticket/199
I would say it's a blocker because that's the default value for that
field and the first person who modified the ticket (Marco) after those
fields were set up didn'
Why is this bug marked as Blocker?
http://dev.sugarlabs.org/ticket/199
Traditionally, we made Blocker mean that a XOOS release must wait for
it to be fixed. Now that we have multiple downstreams, we might want
to rethink the semantics to mean "no sucrose release until all
blockers are fixed",
6 matches
Mail list logo
