Loop/Loop-client Release Process: Difference between revisions

→‎Releasing loop-client for staging: Update section about filing a bug.
(New section to simplify descriptions of how to merge l10n changesets)
(→‎Releasing loop-client for staging: Update section about filing a bug.)
Line 118: Line 118:
   ./create_release.sh <version>
   ./create_release.sh <version>


* File a bug for ops to create the staging release (this may be automated soon).
* Use [https://github.com/rpappalax/deploy-tix deploy-tix] to create a bug for ops to deploy to staging (this is intended to be automated at a later date).
** Use [https://bugzilla.mozilla.org/show_bug.cgi?id=1135053 this bug] as a template
 
  cd ../deploy-tix
  # Build it if you haven't already
  make build
  # Now create the bug.
  ./build/venv/bin/python2.7 deploy_tix -r mozilla -a loop-client -e stage -n 0.16.0 -z -u <bugzilla username> -p <bugzilla password>
 
* Update the bug with the specifics of any configuration changes if needed.


= A note on version numbers =
= A note on version numbers =
canmove, Confirmed users, Bureaucrats and Sysops emeriti
3,628

edits