Release 2.0.0-M3 (motive: to add Scala 3.0.0-M2 support)

[SethTisue]

• merge the 3.0.0-M2 PR (Update For Scala 3.0.0-M2 #470 by @isomarcte)
• choose version number
  • there aren't any actual code changes since M2, but I'm going to call it M3 anyway since these are just milestones and it's a little bit easier this way 🤷‍♂️
• create the release and write the notes
  • https://github.com/scala/scala-xml/releases/tag/v2.0.0-M3
• wait for release build
  • https://travis-ci.com/github/scala/scala-xml/builds/204557524
• release the staging repos
  • https://oss.sonatype.org/#stagingRepositories
• artifacts on Maven Central
  • https://repo1.maven.org/maven2/org/scala-lang/modules/scala-xml_3.0.0-M2/2.0.0-M3/
  • https://repo1.maven.org/maven2/org/scala-lang/modules/scala-xml_2.12/2.0.0-M3/
  • https://repo1.maven.org/maven2/org/scala-lang/modules/scala-xml_2.13/2.0.0-M3/
• post-release, bump version in README
  • 45864ed

[SethTisue]

weird, all the other artifacts have now shown up on Maven Central, but not https://repo1.maven.org/maven2/org/scala-lang/modules/scala-xml_2.13/2.0.0-M3/

the log at https://travis-ci.com/github/scala/scala-xml/jobs/448324169 appears normal, and I'm pretty sure when I reviewed the staging repos, 2.13-on-JVM was one of them

I guess maybe just be patient a bit longer...

UPDATE: haha yeah literally as I writing that, they showed up

[ashawley]

There was a way to publish a tag with a suffix, e.g. v2.0.0-M1#0.22.0-RC1, not sure if that still works, but a new milestone probably is easier.

[ashawley]

There's nothing particularly surprising about the upgrade and I'm not sure how many users will be reading the changelog (do they ever?), but keep in mind that the changelog probably needs to represent the changes since 1.3.0, since that will more likely the upgrade path for users.

[SethTisue]

There was a way to publish a tag with a suffix, e.g. v2.0.0-M1#0.22.0-RC1, not sure if that still works, but a new milestone probably is easier.

That special-tag stuff was removed by @lrytz; the new way to backpublish is to remove the unwanted matrix entries from .travis.yml, then tag and push the commit (tagged, but not on any branch). I did this recently over at scala/scala-parallel-collections#143 and it worked fine. Not sure why I apparently had a fit of laziness here yesterday, it would have been only slight additional effort to keep the version number the same.

Agree that as the 2.0 series gets closer to final, there is more and more pressure to put proper release notes together.