From: Joonas Niilola <juippis@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] www-client/chromium needs a new maintainer
Date: Thu, 8 Jun 2023 10:31:27 +0300 [thread overview]
Message-ID: <212983af-9ef4-687f-0f16-15a6fdb68dc3@gentoo.org> (raw)
In-Reply-To: <CAENw6g7Oc4CgSVFbpfJpBGXp9r_3nD6zE3hHeqnVqpFvxyvy5g@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1311 bytes --]
On 8.6.2023 1.11, Alexe Stefan wrote:
>
> Also, with all this discussion, one can't help but wonder, is
> firefox/librewolf also in such danger?
>
>
Maintaining Firefox shares many of the bullet points mentioned above. We
used to provide alpha/beta builds so issues would be caught early and
reported upstream before a release was made. Luckily few years ago
Mozilla invested in a pretty efficient CI system where they now test
commits/releases using multiple different setups; for example, multiple
different llvm releases, gcc etc. That does relieve us from some burden,
but obviously Gentoo ships Firefox with multiple configure options and
something is bound to be broken every now and then. We've made the
choice of only stabilizing the ESR release which takes some pressure
off, because ESR is usually pretty stable between minor releases.
They also happily welcome patches to fix any issues, although new
features may not get in without strong reasoning first.
I'd also like to credit previous Firefox's maintainers in Gentoo who've
historically been active and done a good job while having close ties
with upstream. I'm glad upstream mostly takes us seriously, even with
our ability to heavily customize the build outcome.
Let's hope this doesn't change.
-- juippis
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 618 bytes --]
next prev parent reply other threads:[~2023-06-08 7:31 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-26 23:59 [gentoo-dev] www-client/chromium needs a new maintainer Mike Gilbert
2023-06-07 10:54 ` Sam James
2023-06-07 10:58 ` Alexe Stefan
2023-06-07 11:00 ` Alexe Stefan
2023-06-07 11:04 ` Sam James
2023-06-07 13:09 ` Jeff Gazso
2023-06-07 14:12 ` Toralf Förster
2023-06-07 14:20 ` Sam James
2023-06-07 14:31 ` Ionen Wolkens
2023-06-07 17:45 ` Mike Gilbert
2023-06-07 18:38 ` Maciej Barć
2023-06-07 19:25 ` Jeff Gazso
2023-06-07 19:31 ` Sam James
2023-06-07 19:48 ` Mike Gilbert
2023-06-07 22:11 ` Alexe Stefan
2023-06-08 7:31 ` Joonas Niilola [this message]
2023-06-08 10:08 ` Alexe Stefan
2023-06-08 10:19 ` Joonas Niilola
2023-06-08 13:49 ` Sam James
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=212983af-9ef4-687f-0f16-15a6fdb68dc3@gentoo.org \
--to=juippis@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox