Difference between revisions of "Delta debugging framework"
RichardChu (talk | contribs) m (→Project Leader(s)) |
RichardChu (talk | contribs) m (→Project Contributor(s)) |
||
| Line 15: | Line 15: | ||
== Project Contributor(s) == | == Project Contributor(s) == | ||
| − | Name(s) of people casually working on the project, or who have contributed significant help. | + | Name(s) of people casually working on the project, or who have contributed significant help. Include links to personal pages within wiki. |
| + | NOTE: only Project Leader(s) should add names here. You '''can’t''' add your own name to the Contributor list. | ||
;[[User:Dean|Dean Woodside]] | ;[[User:Dean|Dean Woodside]] | ||
;[[User:Cbguy1|Colin Guy]] | ;[[User:Cbguy1|Colin Guy]] | ||
;[[User:Sherman|Sherman Fernandes]] | ;[[User:Sherman|Sherman Fernandes]] | ||
| − | |||
| − | |||
== Project Details == | == Project Details == | ||
Revision as of 21:53, 15 September 2006
Contents
Project Name
Delta debugging framework
Project Description
Delta debugging is an automated approach to debugging that isolates failures systematically. Given a failing test that can be mechanically verified (including a browser crash), delta debugging is a way of automatically isolating the change that introduced the failure. Having a framework in place to pull builds from CVS, bisect by date and change set (using bonsai data -- remember, CVS doesn't have changesets!), and report results would let computers make developers more productive.
Project Leader(s)
Name(s) of primary people working on the project. If you want to join a project as leader, discuss with other leaders first. Include links to personal pages within wiki.
Project Contributor(s)
Name(s) of people casually working on the project, or who have contributed significant help. Include links to personal pages within wiki. NOTE: only Project Leader(s) should add names here. You can’t add your own name to the Contributor list.
Project Details
Provides more depth than the Project Description. This is the place for technical discussions, project specs, or other details. If this gets very long, you might consider breaking this part into multiple pages and linking to them.
Project News
This is where your regular updates will go. In these you should discuss the status or your work, your interactions with other members of the community (e.g., Seneca and Mozilla), problems you have encountered, etc.
Put detailed technical information into the Project Details page (i.e., update it as you go), and save this section for news about participation in the project.
