From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id A039F139694 for ; Tue, 6 Jun 2017 09:19:05 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 388A421C23C; Tue, 6 Jun 2017 09:12:06 +0000 (UTC) Received: from smtp.gentoo.org (mail.gentoo.org [IPv6:2001:470:ea4a:1:5054:ff:fec7:86e4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id CE65D21C03C for ; Tue, 6 Jun 2017 09:11:55 +0000 (UTC) Received: from katipo2.lan (unknown [203.86.205.69]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: kentnl) by smtp.gentoo.org (Postfix) with ESMTPSA id 77B833418B1 for ; Tue, 6 Jun 2017 09:11:49 +0000 (UTC) Date: Tue, 6 Jun 2017 21:11:24 +1200 From: Kent Fredric To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] Last rites: www-client/phantomjs and dev-ruby/poltergeist Message-ID: <20170606211124.38b51703@katipo2.lan> In-Reply-To: <1496726880.31590.1.camel@gentoo.org> References: <1496646687.9038.9.camel@gentoo.org> <20170605230605.099dfdc3@katipo2.lan> <1496726880.31590.1.camel@gentoo.org> Organization: Gentoo X-Mailer: Claws Mail 3.15.0-dirty (GTK+ 2.24.31; x86_64-pc-linux-gnu) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; boundary="Sig_/Cmh5O_QppS5K.vGVCSGMW8R"; protocol="application/pgp-signature" X-Archives-Salt: e94cdbcb-1913-432c-82b4-674e8a500557 X-Archives-Hash: 640b35afd7065f65457230fdbe5eba6a --Sig_/Cmh5O_QppS5K.vGVCSGMW8R Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Tue, 06 Jun 2017 07:28:00 +0200 Hans de Graaff wrote: > What kind of timeframe do you propose? >=20 > > 1.5 Months from "We're not working on this" to "its dead jim, kill > > it from orbit" > > is a bit fast for anything entrenched. =20 >=20 > The problems were there a lot longer so for me at least it still feels > slow. The fact that Chromium is now an alternative finally made it > easier to mask this, but really we should have masked this months ago. > If not for security reasons than for all the QA violations such as > tons of bundled code. >=20 > > Chromium 59 is also, similarly, quite new. =20 >=20 > It has hit stable upstream so we should see stable versions in Gentoo > soon, I expect. I'm sort of hoping that we can delay at least until it becomes viable to use newer stuff on travis. That way when all the underlying ecosystem things are updated to work with chromium-headless, and it becomes viable to actually test this in a consistent way the same way on every target, the need to maintain phantomjs goes away. But at this time, the context that matters is: Seeing the last-riting was the *first* indication I received that any changes were being done that I needed to pay attention to. So making sure everything is up-to-scratch on top of all the other stuff I have to do Gentoo side ( *cough* bug 613764 ) just means I haven't had any of the sort of time I need to to respond to this that quickly. I'm fine with it living in pmask as long as its "insecure, but usable". Just 30 days to overhaul things on top of other work is a serious problem for anyone with time issues already. But as to how long is a reasonable time frame before tree-cleaning, I hope other responders can give a better depiction of this. ( I only consider my own use of this "amateur" at best right now, and even with such a low usage I have a hard time working out what I need to do to stay current, I'd hate to know what its like for people relying on this in their production testing toolchain :/ ) --Sig_/Cmh5O_QppS5K.vGVCSGMW8R Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEPZazbI/qrFT1o9rn6FQySxNmqCAFAlk2ccgACgkQ6FQySxNm qCDFbA/+NWlNzHgUa3GEzDIMWCyYsqfT6zORENjuXTFhnFLXCvOtKH0x3OjErPQh syz7sBnRWBJ8zzUU3YHYOeHGUPHDEF4igD+bBZLD1DkiAP9zXOQwqTwtNm2lUiCn CVAvRmvp0EDbSTVCxrWhwXACJLzNhpoLiDb1Ixshg/UWRdEjyLsQwhRgogzPXOyn werFhgH0OmMAJd+Ll7thDFhrVnwQq8yb96Rky+C4hqCkJnH114nYnNY6uGc9YNWu 5c/eHrwm8DUUshOmlfTHtVr51Zggxn+lhBvV+GzIrh2Gui4olZcspVAMs2TyVB0e 7gHgkdS5Ga029e5Qg0K7mMqzMpK/fqgnyXzj39B81UhrVagnKxa0Rjs1PVywLaSm de7FQu/CTP9ZKwtoRPVK0mDHqhtKuxhBLvdCNnUCsIq2r78In4wrRyWF0iYAXAvI JfT0ewtLcYGOOy23JtPwnASxUvGhDcyjwKOQF2o27jTawOjZ86+wB0qPdvKx1vTM 4fzfhU5VJLN4nud45z9eh1qRJIw4uiuWvVA/QZPRN2Wi/bIb9TMxfyrq/NlfS7Qs N/JR2hRatyZw1GmAIUbtYj7fkjpZSi1uL/QkzHpHeudjkfliYw4F7SeakwqCBV6x Bd07sCBa6SFf6u1M8GWVONSj7+MTRP1vuBiP5OUAWIspRkxZVCY= =fKe8 -----END PGP SIGNATURE----- --Sig_/Cmh5O_QppS5K.vGVCSGMW8R--