You can still disable updates, you just have to do it via policy: https://github.com/mozilla/policy-templates/blob/master/README.md#disableappupdate
Mike On Wed, Aug 28, 2019 at 9:51 AM William Spratt <[email protected]> wrote: > Hi All, > > > > We have a controlled environment, so we don’t allow an update to be > released until we’ve QA’d it. We used on control that by setting it to > “Never update” in the options. With ESR 68 that option is gone. What’s > the recommended best practice for ESR 68 to prevent pop-up messages about > the need to update until we’ve QA’d it? > > > > Regards > > > > Will > > > > *Will Spratt* > > *IT Scientific Support Specialist* > > *Fera Science Ltd.* > > > > [email protected] | Tel +44 (0)1904 46 2631 | Mob +44 > (0)7810855621 > > > > www.fera.co.uk | Twitter <https://twitter.com/ferascience> | LinkedIn > <https://www.linkedin.com/company/fera-science> | YouTube > <http://www.youtube.com/user/FeraUK1> > > > _______________________________________________ > Enterprise mailing list > [email protected] > https://mail.mozilla.org/listinfo/enterprise > > To unsubscribe from this list, please visit > https://mail.mozilla.org/listinfo/enterprise or send an email to > [email protected] with a subject of "unsubscribe" >
_______________________________________________ Enterprise mailing list [email protected] https://mail.mozilla.org/listinfo/enterprise To unsubscribe from this list, please visit https://mail.mozilla.org/listinfo/enterprise or send an email to [email protected] with a subject of "unsubscribe"
