canmove, Confirmed users
2,056
edits
Jetpack/Release Process: Difference between revisions
Jump to navigation
Jump to search
→Thaw Development
(update the Build/Test Release Candidate(s) section with Git specifics) |
|||
| Line 151: | Line 151: | ||
= Thaw Development = | = Thaw Development = | ||
Clone the canonical repository and enter its working directory: | |||
git clone git@github.com:mozilla/addon-sdk.git | |||
cd addon-sdk | |||
Update references to the version in static-files/index.html and other files to the development cycle version, which is the conservative anticipated next release followed by the "pre" suffix (e.g. 1.0b2pre), then commit and push the change: | |||
(update references to the version) | |||
git commit -a -m"update version for next development cycle" | |||
git push origin master | |||
Notify Jetpack code contributors that development has been thawed via a post to the forum. The post should specify that the repository is open for general checkins and that checkins no longer need driver approval. | Notify Jetpack code contributors that development has been thawed via a post to the forum. The post should specify that the repository is open for general checkins and that checkins no longer need driver approval. | ||
{{note|in theory, you can thaw development any time after the first release candidate, since it's possible to | {{note|in theory, you can thaw development any time after the first release candidate, since it's possible to fix release blockers on the branch. In practice, it's better to keep the tree frozen longer to focus the team's attention on release blockers.}} | ||
= Release = | = Release = | ||