canmove, Confirmed users
2,056
edits
Jetpack/Development Process: Difference between revisions
Jetpack/Development Process (view source)
Revision as of 06:21, 12 September 2011
, 12 September 2011add a draft landing requirements section
(add a draft landing requirements section) |
|||
| Line 50: | Line 50: | ||
New docs and docs enhancements that do not involve code changes, however, can land on the stabilization branch during the first two weeks of each stabilization period (i.e. while the code is in alpha), so tech writers have time to document late-breaking changes, and because such changes are less likely to cause regressions. | New docs and docs enhancements that do not involve code changes, however, can land on the stabilization branch during the first two weeks of each stabilization period (i.e. while the code is in alpha), so tech writers have time to document late-breaking changes, and because such changes are less likely to cause regressions. | ||
= Landing Requirements = | |||
{{draft|}} | |||
In order to land, a change must provide a notable benefit and not regress tests. In most cases, it must also pass a code review by an SDK code reviewer. And if it changes or adds a user-facing API, it must also pass an API review by the technical lead. | |||
Exceptions to the code review requirement include: | |||
* release management changes (f.e. version number bumps) | |||
* additions to the [https://addons.mozilla.org/en-US/developers/docs/sdk/1.0/dev-guide/appendices/credits.html credits] | |||
* obvious and trivial test bustage fixes | |||
* obvious and trivial typo (spelling, grammar) fixes in documentation | |||
= TBD = | = TBD = | ||