Time to Punt Bugs from Milestone 11!

[Karen Grunberg]

Now that we've branched M10, we're already trying to prepare for M11, here are the current stats:

• 1364 m11 bugs
• 153 m11 bugs marked as Available
• 104 m11 bugs with no owner
• 31 m11 bugs marked as Untriaged

All of these numbers are too high for this point. Especially the overall bug count:

Here is my plan:

• All available m11 bugs go back to untriaged Monday
• All ownerless m11 bugs go back to untriaged Monday
• All untriaged bugs have the m11 label removed on March 1 (a little over 3 weeks from now)

All bugs that I move will get a special label denoting which move they were a part of, so we can revert if needed.  If anyone has any concerns with this, please let me know.

Brach Date for M11 is: March 7, 2011. A Lot sooner than it seems!!

I will also send individual emails to bug owners. I know that we've just cut M10 branch and it seems too soon to worry about M11. But please know that we have to punt aggressively if we're going to make the timelines we've set, so please spend a few moments looking through your bugs for M11 and punt anything that you will not realistically going to be able to tackle in the next few weeks. 

thanks,

-Karen

[Paweł Hajdan, Jr.]

Can we clarify the meaning of StopPunting label? I've seen bugs with that label being punted anyway, so maybe we should just remove that label.

On the other hand, we have flakiness-related bugs that get punted multiple times. Some examples:

http://code.google.com/p/chromium/issues/detail?id=50447

http://code.google.com/p/chromium/issues/detail?id=54717 (I just hate that flake, the test fails very frequently)

http://code.google.com/p/chromium/issues/detail?id=26296 (flaky since 2009, someone comments the problem reproduces with his extension, i.e. this is not a test-only problem)

http://code.google.com/p/chromium/issues/detail?id=35965 (flaky since early 2010, browser crashes)

Test flakiness/instability slows down the development, so for the top flakes I'd really suggest not punting.

--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev

[Aaron Boodman]

On Fri, Feb 4, 2011 at 12:04 PM, Paweł Hajdan, Jr.
<phajd...@chromium.org> wrote:
> http://code.google.com/p/chromium/issues/detail?id=26296

Note: it just so happens that Sam checked in a change on this test today.

- a

[Paweł Hajdan, Jr.]

Sounds great to me. I'm generally impressed by your effort to make extensions tests more solid, it's really non-trivial.

To make the Mstone-11 test lists slightly more focused, I've punted some of the test bugs:

http://code.google.com/p/chromium/issues/detail?id=54822

http://code.google.com/p/chromium/issues/detail?id=54825

After that we have 72 bugs with Tests label targeted for Mstone-11. Those are mostly tests that trigger crashes or assertions.

For the disabled tests, I'd suggest re-enabling them with more debugging code added. It might turn out some of the issues have already been fixed.