Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(443)

Side by Side Diff: docs/stabilize_trunk.md

Issue 1309473002: WIP: Migrate Wiki content over to src/docs (Closed) Base URL: https://chromium.googlesource.com/chromium/src.git@master
Patch Set: documentation_best_practices.md Created 5 years, 4 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View unified diff | Download patch
OLDNEW
(Empty)
1 # What should I work on?
Robert Sesek 2015/08/24 18:07:43 Seems obsolete.
2
3 This query is handy to find the Issues assigned to you: http://code.google.com/p /chromium/issues/list?can=2&q=owner:me&sort=mstone+pri
4
5 Otherwise, lend a hand on the important areas listed below.
6
7 If you are new to the project you should try fixing a layout test and take on it ems from this list: http://code.google.com/p/chromium/issues/list?can=2&q=size: small%20OR%20label:helpwanted&sort=owner+size
8
9 Questions to jon@chromium.org
10
11 ## Crashing Bugs
12
13 http://code.google.com/p/chromium/issues/list?can=2&q=mstone:2.1+label:crash
14
15 ## Layout Tests
16
17 Fixing layout tests may involve one or more of the following:
18 1. Fixing a bug
19 1. Implementing missing test methods
20 1. Adding a missing baseline to a new test
21 1. Updating a baseline
22
23 **How To** http://dev.chromium.org/developers/testing/webkit-layout-tests
24
25 **List of Fixable Tests** http://src.chromium.org/viewvc/chrome/trunk/src/webkit /tools/layout_tests/test_lists/tests_fixable.txt?view=markup
26
27 Sign up to work on a layout test by putting your name on the spreadsheet at http ://spreadsheets.google.com/ccc?key=pMwul3Seofg448Q1VFJjsJA&hl=en
28
29 ![http://chart.apis.google.com/chart?chtt=Test+Passing+Trend+Over+90+Days&chxt=r &cht=lxy&chs=675x125&chd=t:-1|1.0,1.0,2.0,1.0,2.0,2.0,1.0,1.0,1.0,2.0,2.0,1.0,1. 0,1.0,1.0,1.0,1.0,1.0,1.0,1.0,2.0,2.0,2.0,2.0,2.0,2.0,2.0,2.0,2.0,2.0,2.0,2.0,2. 0,2.0,2.0,2.0,2.0,2.0,2.0,2.0,2.0,1.0,3.0,3.0,3.0,3.0,3.0,3.0,3.0,3.0,3.0,3.0,0. 0,0.0,1.0,0.0,1.0,0.0,0.0,0.0,0.0,0.0,1.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0. 0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0|-1|63.0,63 .0,64.0,64.0,62.0,62.0,62.0,62.0,62.0,58.0,60.0,62.0,62.0,62.0,62.0,62.0,62.0,62 .0,62.0,62.0,62.0,62.0,61.0,62.0,60.0,60.0,60.0,59.0,59.0,59.0,59.0,59.0,59.0,53 .0,52.0,58.0,58.0,58.0,58.0,58.0,58.0,58.0,58.0,58.0,59.0,59.0,59.0,59.0,60.0,60 .0,60.0,60.0,60.0,60.0,60.0,61.0,61.0,55.0,55.0,57.0,57.0,57.0,60.0,61.0,61.0,56 .0,56.0,56.0,56.0,57.0,57.0,57.0,56.0,57.0,57.0,57.0,57.0,59.0,62.0,62.0,62.0,62 .0,62.0,62.0,62.0,62.0,62.0,62.0,62.0,62.0&chco=FF0000,0000FF&chdl=All+Tests|Wan t+Pass&chdlp=b&chxr=0,81.4,100&ext=.png](http://chart.apis.google.com/chart?chtt =Test+Passing+Trend+Over+90+Days&chxt=r&cht=lxy&chs=675x125&chd=t:-1|1.0,1.0,2.0 ,1.0,2.0,2.0,1.0,1.0,1.0,2.0,2.0,1.0,1.0,1.0,1.0,1.0,1.0,1.0,1.0,1.0,2.0,2.0,2.0 ,2.0,2.0,2.0,2.0,2.0,2.0,2.0,2.0,2.0,2.0,2.0,2.0,2.0,2.0,2.0,2.0,2.0,2.0,1.0,3.0 ,3.0,3.0,3.0,3.0,3.0,3.0,3.0,3.0,3.0,0.0,0.0,1.0,0.0,1.0,0.0,0.0,0.0,0.0,0.0,1.0 ,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0 ,0.0,0.0,0.0,0.0,0.0,0.0,0.0|-1|63.0,63.0,64.0,64.0,62.0,62.0,62.0,62.0,62.0,58. 0,60.0,62.0,62.0,62.0,62.0,62.0,62.0,62.0,62.0,62.0,62.0,62.0,61.0,62.0,60.0,60. 0,60.0,59.0,59.0,59.0,59.0,59.0,59.0,53.0,52.0,58.0,58.0,58.0,58.0,58.0,58.0,58. 0,58.0,58.0,59.0,59.0,59.0,59.0,60.0,60.0,60.0,60.0,60.0,60.0,60.0,61.0,61.0,55. 0,55.0,57.0,57.0,57.0,60.0,61.0,61.0,56.0,56.0,56.0,56.0,57.0,57.0,57.0,56.0,57. 0,57.0,57.0,57.0,59.0,62.0,62.0,62.0,62.0,62.0,62.0,62.0,62.0,62.0,62.0,62.0,62. 0&chco=FF0000,0000FF&chdl=All+Tests|Want+Pass&chdlp=b&chxr=0,81.4,100&ext=.png)
30
31 This chart shows our progress in fixing layout tests on Windows for the last 90 days. The goal is to get Want to Pass (blue) up to 100%. The All Tests perform ance number indicates that there are some tests that are not part of the goal fo r stabilization. These tests may be part of future specifications or bad tests.
32
33 ## Memory Bugs
34
35 We are using [valgrind](http://dev.chromium.org/developers/how-tos/using-valgrin d) to look for mistakes in memory management. These bugs are filed in the bug t racker.
36
37 http://code.google.com/p/chromium/issues/list?can=2&q=label:valgrind
38
39 ## Regressions
40
41 We have identified a number of regressions. These are also filed in the bug tra cker.
42
43 http://code.google.com/p/chromium/issues/list?can=2&q=mstone:2.1+label:regressio n&sort=owner
44
45 ## Other bugs
46
47 There are other bugs as well of interest.
48
49 http://code.google.com/p/chromium/issues/list?can=2&q=mstone:2.1+-label:regressi on,crash&sort=owner
50
51 # Details
52
53 Add your content here. Format your content with:
54 * Text in **bold** or _italic_
55 * Headings, paragraphs, and lists
56 * Automatic links to other wiki pages
OLDNEW

Powered by Google App Engine
This is Rietveld 408576698