Received: from out2.migadu.com (out2.migadu.com [188.165.223.204])
	by nld3-dev1.alpinelinux.org (Postfix) with ESMTPS id B6F9F781142
	for <~alpine/devel@lists.alpinelinux.org>; Fri, 21 Jan 2022 00:59:15 +0000 (UTC)
MIME-Version: 1.0
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ayaya.dev; s=key1;
	t=1642726755;
	h=from:from:reply-to:subject:subject:date:date:message-id:message-id:
	 to:to:cc:cc:mime-version:mime-version:content-type:content-type:
	 content-transfer-encoding:content-transfer-encoding:
	 in-reply-to:in-reply-to:references:references;
	bh=z13wJ8eqtWdziOwb0fxJ8TzNg1a+dVAlUhJA5/W5A7U=;
	b=BfiipRfk559v4H5XJl7a9tssMn+rvEYSw2ntQvM8NuxUOhZGiZqBQtQ++PgsDCvEiZNMo7
	tW8Xhx3V6p78mCljZUorTYWibUmxl1Jh+9l7HIGiwhhCVMKxbkLtbDNb2Wb05UEU0EY3wa
	iIx1eoYVP9+kunZ4Qm7SWxaHNs4LLG4=
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=UTF-8
Date: Fri, 21 Jan 2022 01:59:12 +0100
Message-Id: <CHAY17XZ5EBB.2BPP437PIORUI@psykose>
To: "Wolf" <wolf@wolfsden.cz>, <~alpine/devel@lists.alpinelinux.org>
Cc: 
Subject: Re: Firefox and non-edge alpine releases
X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers.
From: "alice" <alice@ayaya.dev>
References: <20220121004231.zsk7h5q5wexz5hxd@mail.wolfsden.cz>
In-Reply-To: <20220121004231.zsk7h5q5wexz5hxd@mail.wolfsden.cz>
X-Migadu-Flow: FLOW_OUT
X-Migadu-Auth-User: ayaya.dev

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=20