Firefox/Go Faster/Releasing an add-on mechanics: Difference between revisions

Jump to navigation Jump to search
Update ftp details and basic access information.
(Initial version, dump the know notes so far.)
 
(Update ftp details and basic access information.)
Line 3: Line 3:
{{warning|This document does not yet contain how to handle multiple add-ons. Please talk to ianb and Standard8 before attempting to proceed.}}
{{warning|This document does not yet contain how to handle multiple add-ons. Please talk to ianb and Standard8 before attempting to proceed.}}


* Sign xpi
This document only contains details about the mechanics for releasing. You will need to discuss with release drivers and other folks about being able to actually do a release.
* Upload xpi to ftp
 
== Access Rights ==
 
To upload and release add-ons, you'll need access to:
 
* ftp (<code>[https://ftp.mozilla.org/pub/system-addons/ /pub/system-addons/]</code>)
** Talk to the Cloud Services team for access
* balrog via VPN
** Talk to Release Engineering team for access
 
== Procedure
 
This process assumes you have a xpi that is ready for release.
 
* Get the xpi signed, e.g. [https://bugzilla.mozilla.org/show_bug.cgi?id=1249764 clone this bug]
* Upload the signed xpi to ftp in the <code>[https://ftp.mozilla.org/pub/system-addons/ /pub/system-addons/]</code> directory.
** Use a sub-directory appropriate for the add-on.
* Generate Balrog template
* Generate Balrog template
** Under Releases, search for `SystemAddons`
** Under Releases, search for `SystemAddons`
canmove, Confirmed users, Bureaucrats and Sysops emeriti
3,628

edits

Navigation menu