Bug 22426

Summary: Propose the latest version of firefox as a complement to or replacement for ESR firefox
Product: Mageia Reporter: Jean Michel Varvou <jeanmichel.varvou>
Component: New RPM package requestAssignee: Mageia Bug Squad <bugsquad>
Status: RESOLVED INVALID QA Contact:
Severity: enhancement    
Priority: Normal CC: marja11
Version: Cauldron   
Target Milestone: ---   
Hardware: All   
OS: Linux   
URL: https://www.mageialinux-online.org/forum/topic-24723.php#m236008
Whiteboard:
Source RPM: CVE:
Status comment:

Description Jean Michel Varvou 2018-01-20 07:55:51 CET 
Description of problem:

A survey is launched on MLO to determine the need for the latest version of Firefox. This initiative is launched because many users have to manually install the latest version 57 of Firefox to take advantage of the latest browser upgrades and troubleshooting of the ESR version.

Survey in French : https://www.mageialinux-online.org/forum/topic-24723.php#m236008
Survey translate with Google : https://translate.google.fr/translate?sl=fr&tl=en&js=y&prev=_t&hl=fr&ie=UTF-8&u=https%3A%2F%2Fwww.mageialinux-online.org%2Fforum%2Ftopic-24723.php%23m236008&edit-text=&act=url

Thank you in advance for your attention to this request. Very cordially.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
Comment 1 Marja Van Waes 2018-01-20 13:24:15 CET 
Please read
https://forums.mageia.org/en/viewtopic.php?f=10&t=3806&p=27369&hilit=esr#p27347 and further:

Using the ESR version enables stability and security to be maintained with less maintenance effort by Mageia's overworked volunteers, than would be required if each new version were to be provided. 

If some of the people who think this is really needed become Mageia packagers and promise to make sure that the non-ESR version is updated when needed, then we can discuss doing this.

CC: (none) => marja11

Comment 2 David Walser 2018-01-21 02:27:56 CET 
Even then we can't.  For instance, we wouldn't be able to package 57 or 58 or whatever the milestone releases are on right now, as those require nss 3.35 and 52 requires nss 3.28.  Granted, nss isn't usually an issue with that, but sometimes sqlite3 is.  There's really no reason for us to package the milestones anyway as they can easily be obtained from Mozilla.

Status: NEW => RESOLVED
Resolution: (none) => INVALID