Release RC1

• Finalize release
  • Look at the milestone of the version being released. Move all the open issues from it to the next milestone.
  • Merge branch of the previous release into master to guarantee that all of the commits are propagated to master
• Publish artifacts to Maven via CI
  • Create branch 3.0.0-RC1 from master
  • On that branch, set baseVersion and tag it as 3.0.0-RC1
  • On master, set baseVersion to the next version to be released
• Update scalaVersion (and, if applicable, the sbt-dotty version) in the Dotty ecosystem projects
  • https://github.com/scala/scala3-example-project
  • https://github.com/scala/scala3-example-project/tree/mill
  • https://github.com/scala/scala3.g8
  • https://github.com/scala/scala3-cross.g8
  • https://github.com/lampepfl/scala3-staging.g8
  • https://github.com/scala/scala3-tasty-inspector.g8
  • https://github.com/lampepfl/homebrew-brew
    • SHA256 sum for the artifact: wget -q -O- https://github.com/lampepfl/dotty/releases/download/<rc-version>/sha256sum.txt | grep ".tar.gz"
  • https://github.com/lampepfl/packtest
  • https://github.com/lampepfl/xml-interpolator
    • PR submitted
    • PR merged
  • https://github.com/scalacenter/scastie
    • PR submitted
    • PR merged
    • https://scastie.scala-lang.org/ -> Build Settings -> Dotty mentions <rc-version>
  • Dotty reference compiler
    • PR submitted
    • PR merged
  • Scalac
    • PR submitted
    • PR merged
  • Update the dotty-repl Coursier app definition
• Announce the release
  • Publish releases for the RC and stable versions on GitHub Releases
  • Publish Blog Post on dotty.epfl.ch
  • Make an announcement thread on https://contributors.scala-lang.org
  • Tweet the announcement blog post on https://twitter.com/scala_lang

Instructions on how to release

[larsrh]

We need a new release of sbt-dotty, too: f75e6fb3c59fae896b5b9e46c8bb294f04042924

[bishabosha]

@ShapelessCat I am not sure what’s happening, but thank you for linking to the discussion, I added my example there.