[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Will firefox-esr move to version 102 in bullseye?



Sorry for top-posting, but it makes sense for this summary.

As indicated by the replies to my initial email, it is now late
September and firefox-esr has moved to version 102 in the stable
branch. I just upgraded without even noticing any difference,
definitely nothing that broke.

What's more, I no longer have to continue my research about
hardware-accelerated video playback in the browser which prompted all
of this - it just started working automatically after the upgrade. As
a "seasoned" linux user I'm not used to things going this smooth, so
thanks everyone involved for making this upgrade as painless and
invisible as expected from Debian stable.

On Wed, Aug 24, 2022 at 9:13 PM Sven Joachim <svenjoac@gmx.de> wrote:
>
> On 2022-08-24 15:01 -0400, Greg Wooledge wrote:
>
> > On Wed, Aug 24, 2022 at 07:52:44PM +0100, Tixy wrote:
> >> Mozilla stops supporting the old ESR a few months after a new one is
> >> released [1]. So I assume Debian would ship the new one, certainly at
> >> least at the point the old one gets known security vulnerabilities.
> >>
> >> [1] https://support.mozilla.org/en-US/kb/firefox-esr-release-cycle
> >
> > Yes, this is correct.  A current timeline seems to be here:
> >
> > https://wiki.mozilla.org/Release_Management/Calendar
> >
> > Looking at the ESR column in the first table, 2022-08-23 brought us
> > ESR versions 91.13 and 102.2, while 2022-09-20 will have only version
> > 102.3.
> >
> > So, as of Sept. 20th (projected), the 91.x ESR branch will be unsupported,
> > and we'll all have to move to the 102.x branch, whether we want it or not.
>
> For Debian stable, I expect Firefox and Thunderbird to move to the 102
> branch after the next Bullseye point release, scheduled for September
> 10[1].  To build them, at least rustc 1.59 is needed, and Bullseye
> currently only has version 1.51 (packaged as rustc-mozilla).
>
> Cheers,
>        Sven
>
>
> 1. https://lists.debian.org/debian-live/2022/08/msg00006.html
>


Reply to: