We are coming up with a plan to build and ship system addons out of mozilla-central. This way teams won't need to sync their system addons over to the `mozilla-extensions` org in Github. The details are still being worked out, for instance it's not clear if *all* system addons will need to live in mozilla-central, or if we'll support both mozilla-central and mozilla-extensions. The thing, that is clear is that we'll need tasks in mozilla-central that: 1. Build the system addon 2. Sign the system addon 3. Push the system addon to archive.mozilla.org 4. Create a release in balrog for the system addon Basically, copy / share the release pipeline from `mozilla-extensions`. We'll also want to integrate this with Shipit after the automation is all in place.
Bug 1959718 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
We are coming up with a plan to build and ship system addons out of mozilla-central. This way teams won't need to sync their system addons over to the `mozilla-extensions` org in Github. The details are still being worked out, for instance it's not clear if *all* system addons will need to live in mozilla-central, or if we'll support both mozilla-central and mozilla-extensions. The thing that is clear is that we'll need tasks in mozilla-central that: 1. Build the system addon 2. Sign the system addon 3. Push the system addon to archive.mozilla.org 4. Create a release in balrog for the system addon Basically, copy / share the release pipeline from `mozilla-extensions`. We'll also want to integrate this with Shipit after the automation is all in place.