Next week June 29 - July 2 is the Fixit week focusing on reliability.

All crash bugs are Fixit work items.

http://code.google.com/p/chromium/issues/list?can=2&q=label:Crash&sort=owner<http://code.google.com/p/chromium/issues/list?can=2&q=label:Crash&sort=owner&colspec=ID%20Stars%20Pri%20Area%20Type%20Status%20Summary%20Modified%20Owner%20Mstone>

In addition, there are purify, valgrind, and coverity issues labeled for
this round of Fixit.

http://code.google.com/p/chromium/issues/list?can=2&q=coverity%20OR%20valgrind%20OR%20purify%20label:fixit&sort=owner&;

We welcome *all* chromium contributors to participate. For committers
(including provisional committers), please plan to set aside about 2 days
for the next week to fix the above bugs.

The process of this round of Fixit is same as what we did before and I list
here for people recently joined the chromium development community.

1. If you have not done so, please look through the list and take the bugs
you'd like to work on.
2. If you are overloaded with Fixit bugs, find new owners for some bugs or
simply unassign yourself.
3. During the week, we will assign unclaimed bugs. For this reason, you may
want to take the bug you'd like to work on yourself instead of being
assigned with random bugs.
4. As our development culture, be prepared to work on bugs across all
chromium code base. If you are assigned with bugs in an unfamiliar area,
consider the following options:
    - Identify the best person to fix the bug and assign the bug to him/her
if the person has cycles.
    - Do as much as you can to help out, for example, analyzing crash dumps,
querying crash server to find common pattern across crash dumps, narrowing
down the revision range that causes the bug, searching through reports from
user group and bug database to get additional information, finding repro
steps, constructing reduced test cases, etc.
    - Understand the code and fix it.

Huan and Anthony.

--~--~---------~--~----~------------~-------~--~----~
Chromium Developers mailing list: [email protected] 
View archives, change email options, or unsubscribe: 
    http://groups.google.com/group/chromium-dev
-~----------~----~----~----~------~----~------~--~---

Reply via email to