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

Before a point release, MIMA should be run on the test suite, and more #6847

Closed
scabug opened this issue Dec 19, 2012 · 3 comments
Closed

Before a point release, MIMA should be run on the test suite, and more #6847

scabug opened this issue Dec 19, 2012 · 3 comments
Milestone

Comments

@scabug
Copy link

scabug commented Dec 19, 2012

Running MIMA on the distribution tells us a lot about the distribution but not very much about the code being generated. Anything which can be compiled with 2.10.0 should be compilable with 2.10.1 and the generated artifacts should be MIMA-clean. At a minimum there is the whole test scala suite; but by the time 2.10.1 nears release, there will be dozens or hundreds of decent sized scala projects which compile with 2.10.0.

The level of curation of individual projects should not be an issue, because the tests can be the moral equivalent of

for (p <- project) {
  if ("sbt -scala-version 2.10.0 test" passes) {
    ("sbt -scala-version 2.10.1 -mima-against 2.10.0 test" passes) || {
      throw new WeHaveAMimaProblem
    }
  }
}
@scabug
Copy link
Author

scabug commented Dec 19, 2012

Imported From: https://issues.scala-lang.org/browse/SI-6847?orig=1
Reporter: @paulp
Affected Versions: 2.10.0

@scabug
Copy link
Author

scabug commented Jul 10, 2013

@adriaanm said:
Unassigning and rescheduling to M6 as previous deadline was missed.

@scabug
Copy link
Author

scabug commented Dec 11, 2013

@adriaanm said:
we're doing this

@scabug scabug closed this as completed Dec 11, 2013
@scabug scabug added this to the 2.10.0 milestone Apr 7, 2017
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