Mozilla Firefox Browser Stable Version Releases

It is, of course.
Regarding what Brummelchen asked about the snap version, I suppose that was because of the info that is in the About Mozilla Firefox window, specifically "canonical-002 - 1.0".
I think that made Brummelchen wonder whether that Firefox snap 117.0 was compiled with the latest RC2 and not the earlier RC1.
That is why I replied, mentioning that on Kubuntu, in Discover (package manager, software center), if I look at Installed, Firefox snap, it shows: Version: 117.0-2, and I suppose that is compiled with RC2.

 

My guess would be that the Canonical snap is compiled with RC2.

 

my questions is about the used code for build a package offside the official mozilla release. it happend more than once, that some devs cant wait until the official release and compiled RC1 as a release which contains bugs and more. issue where 116.0.3 was not released yet.

Code:

renner@solaris:~$ dpkg --list firefox

Desired=Unknown/Install/Remove/Purge/Hold

| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend

|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)

||/ Name Version Architecture Description

+++-==============-===================================-============-======================================

ii firefox 116.0.3+build1-0ubuntu0.22.04.1~mt1 amd64 Safe and easy web browser from Mozilla

as visible some idiot compiled the rc1 and released it and it came to issues.
so i am sure that snap or mozilla deliver a final package while the package form OS can be different.
the mozilla staged rollout will happen for any OS.

you will find this at least only with firefox, not clear if that means "Ubuntu" but i think so.

 

@Brummelchen,
As in Kubuntu Discover (package manager, software center) for the installed Firefox snap the version number is 117.0-2, wouldn't you think that is compiled with RC2? Is there any reason to think otherwise?

 

i dont know, i dont use linux, i only have ubuntu in vbox rarely used, currently megabytes of updates loading.
"-2" is no official counting at mozilla, it can be anything.

this (see image) is offcial, because from snap because mozilla releases to snap.
and this means also that you are using the own compilation from kubuntu packages.

 

That image is of the German version, where Daveski17 showed the English version.
I still don't see where the idea comes from that the offered snap version may not be compiled from RC2.
I think you are trying to make some point, but I don't see on what it is based.

 

ofc its german, because snap is detecting german language, means that i got a german language pack installed, see image: no lang pack, but same version number. and still snap.
"-2" is package given, not from mozilla. you need to ask the community which base was grabbed, i am not sure we can resolve it here.
the point at least is, that the developer from the package may use other compiler switches and thus the product may be more specific to the used OS, but may cause other unexpected issues. in such cases user need to speak with the community instead mozilla because mozilla is not reponsible for the package.

this one is from mozilla
https://archive.mozilla.org/pub/firefox/releases/117.0/linux-x86_64/en-US/ (tar.bz2)
same file as from here https://www.mozilla.org/en-US/firefox/all/ -> Linux 64-bit

next images shows firefox from that tar.bz2, same numbers - to underline the differences, or not.

therefore - #5072 from Davski17 has to be snap or mozilla(tar)

 

If I'm not mistaken, you were the one who wrote,

So, I don't see why I need to ask the community about it. It was your question, not mine.
I merely wondered where your question arose from.

Is that true?
If I'm not mistaken, Mozilla is the publisher of Firefox snap, not the community.
See: https://snapcraft.io/firefox
Also, if in the terminal I run: snap list, the Firefox publisher is listed as Mozilla, not Canonical (Ubuntu).

 

and then, why did you answer me than Daveski17?

i wrote nothing else.

compiling does not mean to change the publisher.
i think you dont have any clue how compiling is done or about switches.

as i wrote, "-2" means nothing in a package from another source than snap or mozilla directly.
it could also mean the second try of anything, but not RC2.
your package labeled with "117.0-2" is NOT compiled from mozilla instead someone else concerned to kubuntu.
and i gave you an example, and that example got buggy.

i would stop this because i dont see success on your side

 

Thanks.

 

someone else answered me:
-2 is based on RC2
https://github.com/canonical/firefox-snap/commit/a80b15f401a56726a84e8f0d42e8ed6b35a2016f

 

This would make sense, as I actually am English lol.

So, is the RC2 version buggy or what?

 

RC2 may not buggy, but its not the released stage. the code to get compiled lies within that folder. if there is no other RC then it may be the final. for windows - you can compare the hashes for EXE for RC2 and release, if they are same, so the result is that RC2 got final. and even when not you can extract both and compare hashes of files.

the github link shows another one - there exists a "-1" build, probably based on the RC1, i dont know if it was distributed. but that has the underlying problem which i wrote above - no one can be sure that the compiling dude is releasing this early build as the final build. users may think oh great, v117 (117.0-1) is ready, but indeed they got a buggy RC, maybe start ranting against mozilla.

and the example with 116.0.2 -> 116.0.3 in #5078 is one of those. user got 116.0.3 RC1 which contains bugs and not the bugfree 116.0.3 RC2. because he trusted the distributor which was not mozilla.

in your case i assume snap or mozilla directly, but in case of a packaging manager where snap and a origin distributor (like mozilla) is not involved people should not trust blindly into packages.

 

I thought the Ubuntu Firefox snap was compiled by Mozilla.

 

thats what i wrote above and your image shows. snap is filled from mozilla, no one else. but the builds from canonical are not from mozilla.

 

An "interesting" feature for Firefox users as well:

https://www.ghacks.net/2023/09/08/g...ks-in-chromes-safe-browsing-security-feature/

https://www.ghacks.net/2023/09/10/chromes-new-real-time-protection-feature-explained/

P.S.

In Edge I will not take advantage of this new feature:



except indirectly via NextDNS (if I leave it enabled):

 

sorry, you are writing in the wrong thread, this is about firefox, firefox is currently not able to perform this, up to nightly.

 

Version 117.0.1, first offered to Release channel users on September 12, 2023

Spoiler

Fixed

• Fixed a bug causing links opened from outside Firefox to not open on macOS (bug 1850828)
  
  
• Fixed a bug causing extensions using an event page for long-running tasks to be terminated while running, causing unexpected behavior changes (bug 1851373)
  
  
• Temporarily reverted an intentional behavior change preventing JavaScript from changing URL.protocol (bug 1850954).
  NOTE: This change is expected to ship in a later Firefox release alongside other web browsers, and sites are encouraged to find alternate ways to change the protocol if needed.
  
  
• Fixed audio worklets not working for sites using WebAssembly exception handling (bug 1851468)
  
  
• Fixed the Reopen all tabs option in the Recently closed tabs menu sometimes failing to open all tabs (bug 1850856)
  
  
• Fixed the bookmark's menu sometimes remaining partially visible when minimizing Firefox (bug 1843700)
  
  
• Fixed an issue causing incorrect time zones to be detected on some sites (bug 1848615)
  
  
• Security fix
  

 

hi
has somebody received the 115.2 ESR update on/for w7?
thanks