Reminds me of the windows 8 saga, where someone decided every desktop had to 
act like a phone, 

The W8 release got junked, the guy behind W8 got fired. 

On my desktop I have a nice wide screen, a mouse and a functional keyboard, and 
other applications open that need to work with the browser.

On my phone I have a screen that can present perhaps 1 item of useful 
information at a time, normally transient.



Best Regards
Alan Bell
Tel: +44 (0) 2392 265109 ext 22
www.wessextech.co.uk
www.countermark.com
Wessex Technology OEP Ltd, Unit 16, Somerset House, Hussar Court, Westside 
View, Waterlooville, PO7 7SG, UK

Registered in England and Wales, no: 2833845. reg. office: 204 London Road, 
Waterlooville PO7  7AN, UK This email and any attachments are confidential and 
intended for the addressee only. If you are not the named recipient, you must 
not use, disclose, reproduce, copy or distribute the contents of this 
communication. If you have received this in error, please contact the sender 
and then delete this email from your system.
 
Spam Policy: Wessex Technology uses email filtering from Symantec and 
spamhaus.org for the protection of its system integrity


-----Original Message-----
From: Enterprise [mailto:[email protected]] On Behalf Of Michael 
Perkins
Sent: 21 December 2017 06:30
To: Fred Bauer; Sylvestre Ledru; [email protected]
Subject: Re: [Mozilla Enterprise] Announcing the next Extended Support Release 
of Firefox - ESR60 with policy engine

Agreed.  FireFox 57 sucks.  I had to go back to previous version.  When I found 
that the older ESR supported all the features I wanted, I decided to go back 
(in versions) even more to the ESR.




All my machines will soon have the ESR.




________________________________

From: Enterprise <[email protected]> on behalf of Fred Bauer 
<[email protected]>
Sent: Wednesday, December 20, 2017 1:39 PM
To: Sylvestre Ledru; [email protected]
Subject: Re: [Mozilla Enterprise] Announcing the next Extended Support Release 
of Firefox - ESR60 with policy engine 
 

I'm not a system administrator, and I don't even play one on TV. I'm just a 
long-time Firefox user who was forced to switch to the ESR channel because of 
intense dislike of the new "normal channel" Firefox release. I don't understand 
why Firefox had to essentially mimic the Chrome UI, which does not support how 
I want to use my computer browser. 





Now it seems from the messages on this listserve that the forthcoming ESR 
release next year will probably adopt the same ADD-friendly regular 
Firefox/Chrome UI, and I'll be left without a useful browser. Depressing.





I don't know if my feelings are shared by anyone else, but I did want to put 
them out there: not everybody wants their computer browser to work like a smart 
phone browser.




Thanks for listening,

Fred Bauer




________________________________

From: Enterprise <[email protected]> on behalf of Sylvestre Ledru 
<[email protected]>
Sent: Wednesday, December 20, 2017 5:06 AM
To: [email protected]
Subject: [Mozilla Enterprise] Announcing the next Extended Support Release of 
Firefox - ESR60 with policy engine 
 
The Firefox ESR (extended support release) is based on an official release of 
Firefox desktop for use by organizations including schools, universities, 
businesses and others who need extended support for mass deployments. Since 
Firefox 10, ESR has grown in popularity and many large organizations rely on it 
to let their employees browse the Internet securely. 

We want to make customization of Firefox deployments simpler for system 
administrators and we're pleased to announce that our next ESR version, Firefox 
60, will include a policy engine that increases customization possibilities and 
integration into existing management systems. 

What is the policy engine?
The Policy Engine is a project to build a Firefox desktop configuration and 
customization feature for enterprise users. The policy engine will work with 
any tool that wants to set policies and we intend to bring Windows Group Policy 
support soon. We'll be initially supporting a limited set of policies but this 
will be evolving through user feedback.
More details on the policy engine can be found here. 
<https://wiki.mozilla.org/Firefox/EnterprisePolicies> 
Bug reference <https://bugzilla.mozilla.org/show_bug.cgi?id=1419102> 

What's the plan?
In order to accommodate the group policy implementation, we are making Firefox 
60 our next ESR version and will be following this plan: 

*       May 8th - ESR 60.0 released (we'd love feedback from early adopters at 
that point and will be sharing a feedback form through the enterprise mailing 
list) 
*       July 3rd - ESR 60.1 released 
*       August 28th - End of life for ESR 52 and release of ESR 60.2.0. No 
further updates will be offered for ESR52 and an update to ESR60.0.2 will be 
provided through the application update service 


Also please keep in mind that Firefox 57, released last month, supports only 
add-ons built with the WebExtensions API 
<https://developer.mozilla.org/en-US/Add-ons/WebExtensions> . This means that 
Firefox 52 ESR is the last release that will support legacy add-ons.  If you 
developed an add-on that has not been updated to the WebExtensions API, there 
is still time to do so. Documentation 
<https://developer.mozilla.org/en-US/Add-ons/WebExtensions/Porting_a_legacy_Firefox_add-on>
  is available, and you can ask questions by emailing [email protected] or 
joining the #webextensions channel at irc.mozilla.org <http://irc.mozilla.org> .
If you are supporting users who use add-ons, now is a good time to encourage 
them to check if their add-on works 
<https://support.mozilla.org/en-US/kb/frequently-asked-questions-firefox-addon> 
 with Firefox 57+.

Erin, Felipe, Jeff, Kev, Mike Kaply, Romain, Shell & Sylvestre


_______________________________________________
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"

Reply via email to