Closed SethTisue closed 1 year ago
all the todo items before the "Point of no return" are now complete
The release job went fine except that the scala-dist jobs it triggered failed early because apt-get update
failed:
W: The repository 'http://apt.postgresql.org/pub/repos/apt xenial-pgdg Release' does not have a Release file.
217E: Failed to fetch http://apt.postgresql.org/pub/repos/apt/dists/xenial-pgdg/main/binary-amd64/Packages 404 Not Found [IP: 87.238.57.227 80]
218E: Some index files failed to download. They have been ignored, or old ones used instead.
I merged https://github.com/scala/scala-dist/pull/220 and re-ran the release job with the sole purpose of re-triggering the scala-dist jobs. (It will also create staging repos on Sonatype, but I'll just drop them.)
downstream publishing is done, so everything appears to be on track for Wednesday
:tada: It's a lot of checkmarks.
Variables to be expanded in this template (or set and 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
gh api --paginate -X GET search/issues -f q='repo:scala/scala is:pull-request is:merged milestone:2.13.9 label:release-notes' -q '.items[] | " * \(.title) ([#\(.number)](\(.html_url)) by [@\(.user.login)](\(.user.html_url)))"'
N days before release
Point of no return
Once sufficient time for community testing has passed, it's time to cut the release!
What is "sufficient" time? A week is a bare minimum. Two weeks is a better "normal" amount. We should also respect requests from Scala Center advisory board members, if they explicitly ask for additional testing time. (In the past, we sometimes only waited a day or two, but this was overly optimistic in presuming that people had been testing nightlies all along.)
Be mindful of others' schedules; even minor releases make work downstream (for Scala.js and Scala Native, for the Scala 3 team, for compiler plugin authors, and so on). And a botched release might make unexpected work for ourselves as well as for others. So it's better not to release on a Friday or even a Thursday, or too close to a major holiday. And it's best to release while everyone in both America and Europe is awake. (First thing in the morning in America is a good choice.)
before_script: export SCALA_VER_BASE=2.13.9 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 v2.13.9
git push https://github.com/scala/scala-dist.git v2.13.9
before_script: export version=2.13.9 scala_sha=986dcc160aab85298f6cab0bf8dd0345497cdc01 mode=archives
: https://app.travis-ci.com/github/scala/scala-dist/builds/?before_script: export version=2.13.9 scala_sha=986dcc160aab85298f6cab0bf8dd0345497cdc01 mode=update-api
: https://app.travis-ci.com/github/scala/scala-dist/builds/?st_stagingRepoPromote [scala-repo]
,st_stagingRepoPromote [modules-repo]
(or use oss.sonatype.org web UI)Check availability
When everything is on maven central
NOTE (Mar 2 2022): at next release time, update these steps as needed to accomodate https://github.com/scala/scala-lang/pull/1344
download/index.md
_config.yml
(update devscalaversion or scalaversion)index.md
(updatecurrentScalaVersion
)api/all.md
,_config.yml
,_overviews/jdk-compatibility/overview.md
current
symlink for the API docs~/home/linuxsoft/archives/scala/api
onchara.epfl.ch
2.1x.y
to $SCALA_VER)ssh jenkins-worker-publish
, then from there you canssh -i ~/.ssh/jenkins_lightbend_chara scalatest@chara.epfl.ch
Prepare downstream
Wait for downstream
Before proceeding any further, wait for the ecosystem to catch up.
We have promised to wait 48 non-weekend hours, minimum.
If there are delays downstream, at some point it may make sense to go ahead and announce anyway, since news of the release will already be spreading in the community.
Announcements
.zip
format,.tgz
doesn't workcurl -X POST -H "Consumer-Key: xxx" -H "Consumer-Token: xxx" -H "Content-Type: application/json" -H "Accept: application/json" -d '{"candidate": "scala", "version": "2.12.14", "url": "https://downloads.lightbend.com/scala/2.12.14/scala-2.12.14.tgz"}' https://vendors.sdkman.io/release
xxx
s with the credential information provided to Seth by Marco Vermeulen (marco at sdkman dot io)sdk list scala
andsdk install scala <version>
(these should work immediately once thePOST
succeeds)PATCH
andDELETE
are also availableAfterwards
project/Build.scala
community-build/community-projects/stdLib213
(after updating https://github.com/dotty-staging/scala to include recent commits)ScalaTarget.scala
will need updatinglatestSpecVersion
inspec/_config.yml
on the old branch, so that spec is marked as no longer current~_data/footer.yml
and_data/doc-nav-header.yml
on docs.scala-lang.org~starr.version
in/versions.properties
Global / baseVersion
in/build.sbt
mimaReferenceVersion
in/project/MimaFilters.scala
mimaFilters
in/project/MimaFilters.scala
, except the one(s) labeled "KEEP"spec/_config.yml
, if it's a major release~You're done!