We're about to land an update to our WebKit code that contains about 4
months worth of changes. This will make the tree unreleasable. We need to
get the tree healthy again so that we can get back to releasing new stuff to
users.

Until we resolve all of the post-WebKit-merge issues, nothing's going out
the door (well, maybe a few important patches to 154), so you're effectively
blocked on this anyway. In the short term (a couple of days?), I expect that
the tree will be red, so you shouldn't even be checking in new code.

*** Please make it a priority to help fix the issues in any way you can. ***
*** I want to get the tree back to a releasable state by 15 October (2
weeks). ***

Things you can help fix:

   1. Layout test failures and regressions. There are ~1000 tests that need
   to be fixed or rebaselined. Sometimes just getting a bug on file with
   accurate root-cause analysis is a huge help.
   2. Other test failures. There will be failures in other test areas, such
   as UI tests and the page cycler tests.
   3. Crashes. I'm sure we have crashes that reliability tests and the page
   cyclers will shake out.

Getting all the layout tests passing is the largest amount of work and where
we need the most help.

I've asked Jon to coordinate the layout test fixing. He'll have more details
in the next day or so.

Thanks,
Mark
--------------------
Resources:

   - The list of tests to fix:
   
http://src.chromium.org/viewvc/chrome/branches/chrome_webkit_merge_branch/webkit/tools/layout_tests/test_lists/tests_fixable.txt
   New test failures in this merge start on line 919.

   - How to run the layout tests:
   http://dev.chromium.org/developers/testing/webkit-layout-tests

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Chromium-dev" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/chromium-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to