You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Variables to be expanded in this template (or export them in a local terminal, so that you can copy/paste the commands below without replacing anything):
Wind down PR queue. There has to be enough time after the last (non-trivial) PR is merged and the next phase. The core of the eco-system needs time to prepare for the final!
Triage scala/bug and scala/scala-dev tickets
Create next scala/scala milestone, move the magical "Merge to 2.13.x" description to it (so Scabot uses it as default for new PRs)
Close the scala/bug milestone, create next milestone, move pending issues
Close the scala/scala-dev milestone, create next milestone, move pending issues
Check PRs assigned to the milestone, also check WIP
Once sufficient time has passed since last merged PR (1-2 weeks depending on whether it's a maintenance or development branch), and core projects have tried out the candidate nightly, it's time to cut the release!
Make sure there are no stray staging repos on sonatype
Trigger a build on travis, specify SCALA_VER_BASE and SCALA_VER_SUFFIX in the custom config: https://travis-ci.org/scala/scala/builds/542650556 (failed at first because compiler-bridge_2.13 was missing at zinc version 1.2.5 -- backpublished)
Remember, tags are forever, so are maven artifacts (even staged ones, as they could end up in local caches) and S3 uploads (S3 buckets can be changed, but it can takes days to become consistent)
Create PR to update versions.properties (new file generated by the bootstrap job) and the baseVersion in build.sbt and the MiMa base version and exclusion filters
Variables to be expanded in this template (or export them in a local terminal, so that you can copy/paste the commands below without replacing anything):
Key links:
N weeks before the release
Release announcement / notes
documentation/api.md
download/index.md
_config.yml
(update devscalaversion or scalaversion)api/all.md
N days before release
Merge in any older release branchOn major release, bump PickleFormat versionPoint of no return
SCALA_VER_BASE
andSCALA_VER_SUFFIX
in the custom config: https://travis-ci.org/scala/scala/builds/542650556 (failed at first because compiler-bridge_2.13 was missing at zinc version 1.2.5 -- backpublished)before_install: export SCALA_VER_BASE=$SCALA_VER_BASE SCALA_VER_SUFFIX=$SCALA_VER_SUFFIX
git tag -s -m "Scala $SCALA_VER" v$SCALA_VER $SCALA_SHA
git tag -s -m "Scala $SCALA_VER" v$SCALA_VER $DIST_SHA
git push https://github.com/scala/scala.git v$SCALA_VER
git push https://github.com/scala/scala-dist.git v$SCALA_VER
before_install: export version=$SCALA_VER scala_sha=$SCALA_SHA mode=archives
: https://travis-ci.org/scala/scala-dist/builds/542716770before_install: export version=$SCALA_VER scala_sha=$SCALA_SHA mode=update-api
: https://travis-ci.org/scala/scala-dist/builds/542721620st_stagingRepoPromote orgscala-lang-1790
Check availability
When everything is on maven central
current
symlink for the API docsModules
if it's a 2.12.x release, publish macro paradise for the new versionAnnouncements
Afterwards
scala-version
on docs.scala-lang.org (example: bump scala-version docs.scala-lang#1294)versions.properties
(new file generated by the bootstrap job) and thebaseVersion
inbuild.sbt
and the MiMa base version and exclusion filtersUpdate WhiteSourceThe text was updated successfully, but these errors were encountered: