Jetpack/Release Process: Difference between revisions

Jump to navigation Jump to search

Jetpack/Release Process (view source)

Revision as of 18:07, 2 February 2011

1,229 bytes removed ,  2 February 2011
remove overview, which duplicates info on Development Process page
(remove overview, which duplicates info on Development Process page)
Line 1: Line 1:
= Overview =
This document describes the release process for Add-on SDK.  Also see [[Labs/Jetpack/Process|Development Process]].
 
Jetpack SDK development happens in roughly four week cycles, as described in [[Labs/Jetpack/Process|Development Process]], each of which culminates in stabilization and release of the codebase. This document describes the release process.
 
In general, we freeze on a Tuesday night at 11:59pm, make the first release candidate available the next day, spend about a week stabilizing the code and preparing the materials, and release the following Wednesday. To ensure that the code is well-baked, we release no sooner than a week after the first candidate and two days after the last one.
 
We use numerically consecutive versions to denote major releases (0.1, 0.2, etc.). Development cycles use the version of the next release followed by "pre" (0.1pre before 0.1, 0.2pre before 0.2, etc.). Release candidates use the final release version internally (i.e. in all code, documentation, and other files inside the package) and that version followed by "rc" and the number of the candidate (0.1rc1, 0.1rc2, etc.) in references external to the package (e.g. in the names of the packages).
 
The rest of this document describes each step in more detail. When following these steps to release a new version, track the non-trivial work being done by filing a meta-bug for the release that depends on individual bugs for each discrete task.


= Freeze Development =
= Freeze Development =
MykMelez
canmove, Confirmed users
2,056

edits

Retrieved from "https://wiki.mozilla.org/Special:MobileDiff/281763"

Navigation menu