You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
this restores the 2.11.7 status quo for the 2.11.8 release.
the upgrade turned out to be way too problematic. even after multiple
PRs addressing regressions, new ones continue to turn up; see
scala/scala-dev#92 for details on the latest
regressions. for past history (including details on regressions), see
these PRs in this repo: #159, #157, #156, #155, #154, #142, plus issue
so what's next after this?
- we could maybe still consider upgrading for 2.11.9, but someone
would need to thoroughly QA it on all platforms and assure us there
are no regressions
- or we could restrict the upgrade to 2.12.x and hope for
partially crowdsourced QA so that regressions would be caught
during the milestone and release candidate phases.
I lean towards leaving 2.11.x frozen at 0.6.4, at least unless the
upgrade brings concrete benefits to end users (no one has listed
any, to my knowledge). if this is mainly just dogfooding, then
2.12.x is a better context for that.
0 commit comments