| 1 |
On Tue, 06 Jun 2017 07:28:00 +0200 |
| 2 |
Hans de Graaff <graaff@g.o> wrote: |
| 3 |
|
| 4 |
> What kind of timeframe do you propose? |
| 5 |
> |
| 6 |
> > 1.5 Months from "We're not working on this" to "its dead jim, kill |
| 7 |
> > it from orbit" |
| 8 |
> > is a bit fast for anything entrenched. |
| 9 |
> |
| 10 |
> The problems were there a lot longer so for me at least it still feels |
| 11 |
> slow. The fact that Chromium is now an alternative finally made it |
| 12 |
> easier to mask this, but really we should have masked this months ago. |
| 13 |
> If not for security reasons than for all the QA violations such as |
| 14 |
> tons of bundled code. |
| 15 |
> |
| 16 |
> > Chromium 59 is also, similarly, quite new. |
| 17 |
> |
| 18 |
> It has hit stable upstream so we should see stable versions in Gentoo |
| 19 |
> soon, I expect. |
| 20 |
|
| 21 |
I'm sort of hoping that we can delay at least until it becomes viable |
| 22 |
to use newer stuff on travis. |
| 23 |
|
| 24 |
That way when all the underlying ecosystem things are updated to work |
| 25 |
with chromium-headless, and it becomes viable to actually test this in |
| 26 |
a consistent way the same way on every target, the need to maintain |
| 27 |
phantomjs goes away. |
| 28 |
|
| 29 |
But at this time, the context that matters is: |
| 30 |
|
| 31 |
Seeing the last-riting was the *first* indication I received that any |
| 32 |
changes were being done that I needed to pay attention to. |
| 33 |
|
| 34 |
So making sure everything is up-to-scratch on top of all the other |
| 35 |
stuff I have to do Gentoo side ( *cough* bug 613764 ) just means I |
| 36 |
haven't had any of the sort of time I need to to respond to this that |
| 37 |
quickly. |
| 38 |
|
| 39 |
I'm fine with it living in pmask as long as its "insecure, but usable". |
| 40 |
|
| 41 |
Just 30 days to overhaul things on top of other work is a serious |
| 42 |
problem for anyone with time issues already. |
| 43 |
|
| 44 |
But as to how long is a reasonable time frame before tree-cleaning, I |
| 45 |
hope other responders can give a better depiction of this. |
| 46 |
|
| 47 |
( I only consider my own use of this "amateur" at best right now, and |
| 48 |
even with such a low usage I have a hard time working out what I need |
| 49 |
to do to stay current, I'd hate to know what its like for people |
| 50 |
relying on this in their production testing toolchain :/ ) |
Archives