Felix Bruckmeier

CI failed because sbt-scoverage was updated to 2.0.0 [here](https://github.com/twitter/util/commit/8d06d68b477d011d912cb12264913e80c7d8b62b). Once `develop` is green again, I can rebase this PR once more, which should fix it.

Well, locally it always works, even with a very very low grace period. My suspicion is that a different timeout (e.g. from `Await.ready`) somewhere is firing the `TimeoutException` and so...

Ok, so apart from the usual flaky test in `util-app` everything seems to be working decently. I've downgraded sbt-scoverage to `1.9.1` though, because `develop` is currently not green. I'm rebasing...

@bryce-anderson There you go. The one failing test is the usual flaky one in util-app. I'd recommend setting its timeout much higher because it's really annoying that PRs are red...

I rebased the PR onto `develop`.

Just wanted to mention that this update is also necessary for the Scala3 migration in general (see #290 where I had to include it as well). 🙂

CI failed because sbt-scoverage was updated to 2.0.0 [here](https://github.com/twitter/util/commit/8d06d68b477d011d912cb12264913e80c7d8b62b). Once `develop` is green again, I can rebase this PR once more, which should fix it.

So, [JDK8 is EoL end of March 2022](https://endoflife.date/java). Also there are several known bugs in JDK8 which would be fixed in JDK11+. I suspect Twitter still doesn't support anything beyond...

Oh, that's great news! :)

The biggest problem is that Dotty/Scala 3 is not stable yet, so (if I understand correctly) for any given Dotty version we want to use for a cross-build, the dependencies...