Closed
Description
- Publish artifacts to Maven via CI
- On branch
0.15.x
, setbaseVersion
to0.15.0
andgit tag
it as0.15.0
. This will publish artefacts to Sonatype and GitHub Release - Merge branch
0.15.x
intomaster
to guarantee that all of the0.15.x
commits are propagated tomaster
- Look at the milestone of the RC version being released. Move all the open issues from it to the next milestone.
- Create branch
0.16.x
frommaster
- On
0.16.x
, setbaseVersion
to0.16.0-RC3
andgit tag
it as0.16.0-RC3
. This will publish artefacts to Sonatype and GitHub Release. - On
master
, setbaseVersion
to0.17.0
- On branch
- Update
scalaVersion
(and, if applicable, thesbt-dotty
version) in the Dotty ecosystem projects- https://github.com/lampepfl/dotty-example-project
- https://github.com/lampepfl/dotty-example-project/tree/mill
- https://github.com/lampepfl/dotty.g8
- Committed to
master
- Committed to
- https://github.com/lampepfl/dotty-cross.g8
- Committed to
master
- Committed to
- https://github.com/lampepfl/homebrew-brew
- Committed to
master
- SHA256 sum for the artifact:
wget -q -O- https://github.com/lampepfl/dotty/releases/download/0.16.0-RC3/sha256sum.txt | grep ".tar.gz"
- Committed to
- https://github.com/lampepfl/packtest
- Committed to
master
- Committed to
- https://github.com/scalacenter/scastie
- PR submitted
- PR merged
- https://scastie.scala-lang.org/ -> Build Settings -> Dotty mentions
0.16.0-RC3
- Dotty reference compiler
- PR submitted
- PR merged
- Scalac
- PR submitted
- PR merged
- 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