There's also the FixedUnreleased status, which we usually use for
security bugs. That seems to fit this use case too.
Adam
On Wed, Dec 16, 2009 at 2:22 PM, Aaron Boodman wrote:
> On Wed, Dec 16, 2009 at 2:03 PM, Evan Stade wrote:
>> On Wed, Dec 16, 2009 at 1:55 PM, Aaron Boodman wrote:
>>>
>
On Wed, Dec 16, 2009 at 2:03 PM, Evan Stade wrote:
> On Wed, Dec 16, 2009 at 1:55 PM, Aaron Boodman wrote:
>>
>> On Wed, Dec 16, 2009 at 1:07 PM, Evan Stade wrote:
>> > a) what labels will a bug that's been deemed merge-worthy have?
>>
>> I dunno if there is an existing convention for this, but
On Wed, Dec 16, 2009 at 1:55 PM, Aaron Boodman wrote:
> On Wed, Dec 16, 2009 at 1:07 PM, Evan Stade wrote:
> > a) what labels will a bug that's been deemed merge-worthy have?
>
> I dunno if there is an existing convention for this, but I was
> thinking we just leave the bug open.
people leave
On Wed, Dec 16, 2009 at 1:07 PM, Evan Stade wrote:
> a) what labels will a bug that's been deemed merge-worthy have?
I dunno if there is an existing convention for this, but I was
thinking we just leave the bug open. Basically everything on mstone-4
releaseblock-stable needs to be merged, by defi
a) what labels will a bug that's been deemed merge-worthy have?
b) isn't the next beta cut from ToT? are we planning to re-release the
current beta?
-- Evan Stade
On Wed, Dec 16, 2009 at 11:27 AM, Aaron Boodman wrote:
> That's all, thanks.
>
> - a
>
> --
> Chromium Developers mailing list: chro
That's all, thanks.
- a
--
Chromium Developers mailing list: chromium-dev@googlegroups.com
View archives, change email options, or unsubscribe:
http://groups.google.com/group/chromium-dev