[Go Faster] Intent to unship: Firefox Hotfix

Andrew McKay amckay at mozilla.com
Fri Mar 31 23:58:16 UTC 2017

I didn't hear anything against this, but I did speak to Julien about
the signing of the hotfix. That uses a server that needs to moved with
the end of life of SCL3. Currently Go Faster add-ons only go back to
Firefox 44. A recent hotfix fixed something in a version earlier than
Firefox 44.

How far back do release management want to be able to go in affecting
changes to Firefox?

This ability to go back to earlier releases does not affect the code
in Firefox, but will affect our ability to remove hotfix support from
an AMO and signing of the hotfix.

On 1 March 2017 at 19:12, Felipe Gomes <fgomes at mozilla.com> wrote:
> Having been involved in shipping fixes with both of these systems, I can say
> that I fully support this.  From a client point of view, system add-ons are
> a lot better; and the release process for them has gotten easier and better
> than hotfixes too.
> I believe there are some developer ergonomics improvements that can be made
> to make them a bit easier to develop and test locally. I have some
> suggestions/ideas and I'll file bugs for them.
> Felipe
> On Wed, Mar 1, 2017 at 5:09 PM, Andrew McKay <amckay at mozilla.com> wrote:
>> Now that we have system add-ons we'd like to deprecate and remove the
>> Hotfix. Given the research that rhelmer recently did, we can see that
>> the uptake of system add-ons is similar to the Hotfix.
>> I've made a proposal here: https://wiki.mozilla.org/Add-ons/HotfixRemoval
>> I'm specifically looking for feedback from release drivers that we are
>> comfortable with system add-ons going forward.
>> _______________________________________________
>> release-drivers mailing list
>> release-drivers at mozilla.org
>> https://mail.mozilla.org/listinfo/release-drivers

More information about the Gofaster mailing list