Hi,

I have a couple questions regarding firefox in non-edge releases (3.15
in this case):

Q:
Firefox-esr is behind and 91.5 seems to contain some security fixes.
However when I try to flag it on [0], I get 404. Is that expected?

Q:
I do not mind trying to send an patch, however what is the approach to
sending patches against non-master branches? Should I somehow tag them
in the patch? Is there some convention here?

Q:
Normal firefox is behind as well. But that is technically a difference
in a major version, so that might be correct. However I wonder if
firefox is not an exception. What is story here? Are major
version upgrades to firefox accepted even in 3.15 (non-edge) branch?

Thanks,
W.

0: https://pkgs.alpinelinux.org/package/v3.15/community/x86_64/firefox-esr

-- 
There are only two hard things in Computer Science:
cache invalidation, naming things and off-by-one errors.

On Fri Jan 21, 2022 at 1:42 AM CET, Wolf wrote:
> Q:
> Firefox-esr is behind and 91.5 seems to contain some security fixes.
> However when I try to flag it on [0], I get 404. Is that expected?
Yes, afaik flagging can only be done against edge.

> Q:
> I do not mind trying to send an patch, however what is the approach to
> sending patches against non-master branches? Should I somehow tag them
> in the patch? Is there some convention here?
Ideally you can just create a merge request on gitlab. Not sure if the
mailing list bot can create mrs against other branches.
I have also raised an upgrade[1].

> Q:
> Normal firefox is behind as well. But that is technically a difference
> in a major version, so that might be correct. However I wonder if
> firefox is not an exception. What is story here? Are major
> version upgrades to firefox accepted even in 3.15 (non-edge) branch?
It is behind on edge because it depends on an icu upgrade.
Generally does not get upgraded on stable- same story more or less for
chromium.

[1]: https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/29800