[chromium-dev] [extensions] Please leave bugs open until they've been merged to beta (where necessary)
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
Re: [chromium-dev] [extensions] Please leave bugs open until they've been merged to beta (where necessary)
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 a...@google.com wrote: 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 -- Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev
Re: [chromium-dev] [extensions] Please leave bugs open until they've been merged to beta (where necessary)
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. Basically everything on mstone-4 releaseblock-stable needs to be merged, by definition, right? b) isn't the next beta cut from ToT? are we planning to re-release the current beta? No, I confirmed with Mal. 249 is bound for stable. Everything we want in m4 stable needs to be merged to 249. - a -- Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev
Re: [chromium-dev] [extensions] Please leave bugs open until they've been merged to beta (where necessary)
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. Basically everything on mstone-4 releaseblock-stable needs to be merged, by definition, right? sounds right b) isn't the next beta cut from ToT? are we planning to re-release the current beta? No, I confirmed with Mal. 249 is bound for stable. Everything we want in m4 stable needs to be merged to 249. ah ok. - a -- Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev
Re: [chromium-dev] [extensions] Please leave bugs open until they've been merged to beta (where necessary)
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
