441
edits
Calendar:Review Process: Difference between revisions
Jump to navigation
Jump to search
m
fixed wiki markup on link
No edit summary |
m (fixed wiki markup on link) |
||
| Line 1: | Line 1: | ||
This document is intended to describe a refinement of the current code ownership and review process in calendar/. For a similar proposal for toolkit/, see [ http://groups.google.com/group/mozilla.dev.planning/msg/5897ab5dd6332098?fwc=1 | This document is intended to describe a refinement of the current code ownership and review process in calendar/. For a similar proposal for toolkit/, see [http://groups.google.com/group/mozilla.dev.planning/msg/5897ab5dd6332098?fwc=1 this newsgroup thread]. | ||
== Problem statement == | == Problem statement == | ||
Within Mozilla, code-ownership and the review process are closely tied. In order to maintain consistency, clarity, and quality in the code in CVS, the code owner and a small group of peers act as a filter for incoming code through the review process. The number of people involved in this filtering has, of necessity, remained small due to the need for each of them to be trusted by all to make similar/compatible decisions. This, however, has resulted in a rather long wait for reviews, which leads to frustration and slow patch development. | Within Mozilla, code-ownership and the review process are closely tied. In order to maintain consistency, clarity, and quality in the code in CVS, the code owner and a small group of peers act as a filter for incoming code through the review process. The number of people involved in this filtering has, of necessity, remained small due to the need for each of them to be trusted by all to make similar/compatible decisions. This, however, has resulted in a rather long wait for reviews, which leads to frustration and slow patch development. | ||