Development:Home Page
Contains development docs relating to bugs, triage, patching, etc.
Building
Development:Building list improvements we need to add to the build docs.
Reviewing
Development:Reviewing gives an overview of how reviewing works in the Camino Project. Most of this information will make its way onto caminobrowser.org/development, but the wiki will host the most recent version of those docs.
Working With Bugs
Development:Good Bugs and Projects is our start of a "good first bugs" list, as well as some summer-sized Camino and Mac Gecko projects that need love.
QA:Keywords & Status Whiteboard explains some of the commonly-used keywords and status whiteboard entries.
- See other Quality Assurance pages for related articles which are more targeted towards end-user support and bug triage than towards developers looking to learn about Camino's use of Bugzilla.
Tools
link to tools and explanations; currently links are all to explanations of some degree of usefulness
- LXR/MXR [1]
- Bonsai/CVS blame/“the hook” [2]
- Tinderbox (???) (tree status, also for perf stuff) [3] MDC doc
- Talkback: Looking at a report/Filing topcrash bugs
- Camino oddities:
- ardissone|away: there's one particularity about the Camino tinderbox
- ardissone|away: because we show all branches on the same page
- ardissone|away: the "Guilty" column and the "C" link on each build
- ardissone|away: are only correct for the trunk
- ardissone|away: if something regresses or busts on 1.8 or 1.8.0, we have to manually compare the times to bonsai
Roadmap
Development:Roadmap is a basic look at where Camino is headed including 1.1, 1.2, and 2.0. Most of this is taken from Sam's roadmap, with some based on Bugzilla targeting.
Note: This page is locked for editing.