Date: Sun, 28 Jun 2020 20:10:22 +0200 From: Christoph Moench-Tegeder <cmt@burggraben.net> To: Christopher Tipper <chris.tipper@gmail.com> Cc: gecko@freebsd.org Subject: Re: FreeBSD Port: www/firefox Message-ID: <20200628181022.GB2469@elch.exwg.net> In-Reply-To: <46977ff1-9662-4030-a812-7b0d5be9f6fd@Spark> References: <CAHJc3PgWzzFOpdqVFKNxo9Z-msUYw5qeOBGkgxrrpmPyEGF-pw@mail.gmail.com> <20200628124317.GA2469@elch.exwg.net> <46977ff1-9662-4030-a812-7b0d5be9f6fd@Spark>
next in thread | previous in thread | raw e-mail | index | archive | help
Please keep this on the list. ## Christopher Tipper (chris.tipper@gmail.com): > I expect more than slag-quoting and bureaucratic obfuscation. "Long > standing policies" are not an excuse for not taking the time for review > and reflection. That doesn't change a thing. The process with firefox (and thunderbird) has been this way for years, without problems so far. > > It's standing policy (for several years now, really) to use the > > release candidates in order to get critical fixes faster and to > > have at least some chance to catch FreeBSD-specific regressions > > earlier, especially as FreeBSD is not a fully-supported platform > > at Mozilla. > > So do that after release. You are shipping unreleased software? Yes, we're shipping release candidates. And they are released - tarballs and binaries (for supported platforms) are readily available on Mozilla's servers. > I didn't say it was that easy but shipping unreleased software is > an opportunity to ship flaws potentially security flaws. Almost all Firefox releases do fix some security problems - and everyone with enough idle time can review those fixes in Mozilla's mercurial and craft exploits for that. If anything, we're shipping security fixes faster. New problems would have to be found first, the're new therefore unknown at that moment. > Let Mozilla do the testing, I didn't sign up to that as well. They don't - that's what "FreeBSD not being a fully-supported platform" is all about. And it's totally fine if you want to wait for Mozilla's public announcement before upgrading - nobody here is forcing you to upgrade at all. > > Font rendering in chromium being "completely broken" is news for me. > Have you used Chromium on FreeBSD? Nobody else has either non of the > settings to X11 fonts have any effect sub-pixel font rendering is > non-existent. I think it expects help from the GPU I am using integrated > graphics and it doesn't work. It works for me, but then I don't have integrated graphics. Did you report that to the cromium maintainers? Regards, Christoph -- Spare Space
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20200628181022.GB2469>