canmove, Confirmed users, Bureaucrats and Sysops emeriti
3,628
edits
Loop/Loop-client Release Process: Difference between revisions
Loop/Loop-client Release Process (view source)
Revision as of 15:34, 23 February 2015
, 23 February 2015Add sections on version numbers & auto update of loop-client.
(→Releasing loop-client: Add section on how to release to staging) |
(Add sections on version numbers & auto update of loop-client.) |
||
| Line 114: | Line 114: | ||
* File a bug for ops to create the staging release (this may be automated soon). | * File a bug for ops to create the staging release (this may be automated soon). | ||
** Use [https://bugzilla.mozilla.org/show_bug.cgi?id=1135053 this bug] as a template | ** Use [https://bugzilla.mozilla.org/show_bug.cgi?id=1135053 this bug] as a template | ||
= A note on version numbers = | |||
Version numbers are generally arbitrary, however, we've so far been following the major.minor.sub version scheme. For releases from the same branch, major and minor stay the same. When a new release occurs with string changes, the minor version gets bumped. | |||
= Automatic updating of loop-client = | |||
The master branch of Loop-client is automatically updated from mozilla-central by a script each hour. | |||
The script lives in loop-client repository and is called [https://github.com/mozilla/loop-client/blob/master/extract_from_hg.py extract_from_hg.py]. | |||
The [[CloudServices/Loop/Deploy#Dev|development server]] runs a cronjob ever hour which runs the script on the loop-client directory on the server (using the mozilla-central hg clone as a base). This also ensures that the development server is automatically updated as well. | |||