Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

overall coverage and quality of 2.12 build leaves much to be desired #158

Closed
SethTisue opened this issue Oct 28, 2015 · 3 comments
Closed
Assignees

Comments

@SethTisue
Copy link
Member

around the time of 2.12.0-M2, we threw together a 2.12 build by-any-means-necessary. it's pretty janky. I've opened tickets on many of the most significant issues (frozen sbt, forked Play, frozen scala-js, commented-out ENSIME, and so on and so on), but there plenty more forked and frozen projects and projects where we aren't running the tests.

I believe we've already overspent our notional budget for 2015 for doing big, intensive rounds of upgrades here, but it would be good to keep chipping away at this.

@SethTisue
Copy link
Member Author

now that RC1 is imminent it's probably time to put some concerted effort into this

@SethTisue
Copy link
Member Author

SethTisue commented Oct 5, 2016

great strides on this made in #324 (as well as other, smaller recent PRs)

some things I'd like to at least take a stab at before closing this ticket:

there's always lots of things that could be improved, but those seem like the big two

@SethTisue
Copy link
Member Author

the ScalaCheck upgrade is #13, so I think we can close this one now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant