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 <a...@google.com> wrote: > On Wed, Dec 16, 2009 at 2:03 PM, Evan Stade <est...@chromium.org> wrote: >> On Wed, Dec 16, 2009 at 1:55 PM, Aaron Boodman <a...@google.com> wrote: >>> >>> On Wed, Dec 16, 2009 at 1:07 PM, Evan Stade <est...@chromium.org> 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 bugs open by mistake all the time. Also, this is hard to search >> for. > > I have a saved search setup for myself for mstone:4 > releaseblock:stable feature:extensions that I look at over and over. > If something is accidentally left open, I will keep pestering the > owner if it can be closed. > > - a > > -- > Chromium Developers mailing list: chromium-dev@googlegroups.com > View archives, change email options, or unsubscribe: > http://groups.google.com/group/chromium-dev > -- Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev
