Firefox 100 is coming soon...

[Mike Kaply]

Firefox 100 will be released on May 3, 2022.

We want to make sure that folks are testing to make sure their applications work with the new version number.

We've created a blog post that has more detail:

https://hacks.mozilla.org/2022/02/version-100-in-chrome-and-firefox/

including information on how to test with Nightly.

We strongly encourage taking some time to test your internal applications to make sure they work properly with Firefox 100.

Similar to Chrome, we will be providing a preference (network.http.useragent.forceVersion) that can be set using the Preferences policy if for some reason you need to keep the version below 100.

Mike Kaply

[Hoang (US), Victor T]

Do you have a recommendation on how we would best approach managing updates? Should we:

• Disable updates all together (what my company is currently doing) and push a new version
• Use this preference to force a version, and just update it later).

 

Just curious…not sure if one is more popular or recommended. Thanks!

 

Victor

 

From: enter...@mozilla.org <enter...@mozilla.org> On Behalf Of Mike Kaply
Sent: Thursday, February 17, 2022 7:32 AM
To: Mozilla.org <enter...@mozilla.org>
Subject: [EXTERNAL] [Mozilla Enterprise] Firefox 100 is coming soon...

 

EXT email: be mindful of links/attachments.

--
You received this message because you are subscribed to the Google Groups "enter...@mozilla.org" group.
To unsubscribe from this group and stop receiving emails from it, send an email to enterprise+...@mozilla.org.
To view this discussion on the web visit https://groups.google.com/a/mozilla.org/d/msgid/enterprise/CAHueOzDApJfjUfhgpTKLfTuQk-V4y%3DP-eN8OeTGEJ5oy8c3%2Bzg%40mail.gmail.com.

[pascal....@orange.com]

Dear Victor

 

On on side we have implemented the following process

 

• We let the auto update process for MINOR releases (those after the dot)
• We disable the auto update process (via GPO) before the release of the next MAJOR release
• We evaluate the MAJOR .0 and .1 against the ecosystem we have in place and evaluate the new features and their settings. We decide what we take immediately and what we keep for later releases during the cycle
• We package the MAJOR .2 release and align our GPO with this. We proceed with PreProd and then a PILOT phase on 10% or our wks.
• If PILOT phase went well – we might have adjusted some settings during it – we proceed with a MASSIVE rollout of this MAHOR .2 release
• Once done we sent turn on again the auto update feature (GPO) in order to take the MINOR releases until the next MAJOR

Hope this helps

 

Bien Cordialement / Best Regards

 

 

“Preparing the future, powering the present” 

 

Pascal Wulleput
Orange Innovation

IT and Services – IT-S

Digital Infrastructure & End-to-end Secure Environments – DIESE

Digital Workspace Services – DWS

e-buro, Services & Maintenances – ESM

 

tel:  +33 633 467 082

pascal....@orange.com

 

 

 

Orange Restricted

De : enter...@mozilla.org <enter...@mozilla.org> De la part de Hoang (US), Victor T
Envoyé : lundi 21 février 2022 21:47
À : Mike Kaply <mka...@mozilla.com>; Mozilla.org <enter...@mozilla.org>
Objet : RE: [EXTERNAL] [Mozilla Enterprise] Firefox 100 is coming soon...

To view this discussion on the web visit https://groups.google.com/a/mozilla.org/d/msgid/enterprise/13e8df3fe53348f08f2fc105c0ca3df6%40boeing.com.

[Mike Kaply]

On Mon, Feb 21, 2022 at 3:47 PM Hoang (US), Victor T <victor....@boeing.com> wrote:

Do you have a recommendation on how we would best approach managing updates? Should we:

• Disable updates all together (what my company is currently doing) and push a new version
• Use this preference to force a version, and just update it later).

 

Just curious…not sure if one is more popular or recommended. Thanks!

We don't have any specific recommendations. I know some folks like to disable updates and only enable them when they know things work.

The goal of having the pref to keep the version below 100 is to make sure folks that want to stay updated can.

We are working on update pinning this year which (hopefully) will make this easier.

Mike Kaply