*Report for 2009-12-23* I have updated the Wiki so there is a 90 day trend report. It will update daily automatically. It is a good idea to look at http://code.google.com/p/chromium/wiki/StabilizeTrunk for the latest information.
The Wiki also includes information on how to help fix layout tests. This is a great way to get involved and begin to learn the codebase. If you have ever wanted to be an open source developer then this is a great way to start! *Layout Tests* We have not made much improvement on the layout tests so far, although we improved .2% on Want to Pass since yesterday. The 90 day trend shows that we have recovered from the webkit merges but we still have a long way to go. When everyone is back from the holidays we will be having a crash-course on layout tests. I hope to get this video-taped so we can share it broadly. [image: To+Be+Fixed=0.6][image: All+Tests=74.9][image: Want+To+Pass=90.4] The Fixed percentage is based on the layout tests in the tests_fixable<http://src.chromium.org/viewvc/chrome/trunk/src/webkit/tools/layout_tests/test_lists/tests_fixable.txt?view=markup> file. These are tests we are currently ignoring because we know they fail. As soon as we fix them we move them out of fixable so this number does not tend to get very high. It can momentarily spike between the time we fix the test and update the file. All tests is based on all available layout tests including those that we are currently not trying to pass. There are tests in this group which are known to be bad or relate to future technologies. Want to Pass is based on the tests that we need to be passing before we will ship a revision of the browser. Getting this number as high as possible is the goal of the stabilization effort. Some of these tests are failing due to subtle changes that require the test to be re-baselined. *Purify Bugs (Memory)* We have resolved 8 of the 40 Purify issues. No change since yesterday. *Regressions* We have resolved 10 of 25 regressions. That is 2 more since yesterday. *Other bugs* We have also resolved 10 of the 41 "other" bugs. That is 2 more since yesterday. So our bug burndown chart looks like this: As long as we keep the red line below the blue line we are on track for the bugs. Keep in mind that this does not include the work on Layout Tests. You will find a lot more information about the Stabilization effort on the Wiki at http://code.google.com/p/chromium/wiki/StabilizeTrunk --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
