Release a new version with nowarn removed?

[cjllanwarne]

Is there any chance of a new version to get #460 out into a release?

Right now this import collision is making us jump through some awkward hoops to update our project to 2.12.13, and we could do it much more neatly if this merged ticket was part of an official release.

Thank you!

[SethTisue]

Sure, I can do that.

[SethTisue]

sorry for the delay...

• merge outstanding PRs
• choose version number
  • hmm, this seems subjective... I guess let's call it 2.5.0 (rather than 2.4.5) since we're removing something. going to 3.0.0 seems excessive, since the removed thing should only affect compile-time, not run-time
• create the release
  • https://github.com/scala/scala-collection-compat/releases/tag/v2.5.0
• wait for release build
  • https://travis-ci.com/github/scala/scala-collection-compat/builds/232236299
• release the staging repos
  • https://oss.sonatype.org/#stagingRepositories
• artifacts on Maven Central
  • https://repo1.maven.org/maven2/org/scala-lang/modules/scala-collection-compat_3/2.5.0/
  • (not a complete list)
• post-release, bump version in README
  • reset MiMa on 2.5.0 #469