- scala/scala milestone: https://github.com/scala/scala/milestone/72
- scala/bug milestone: https://github.com/scala/bug/milestone/91
- scala/dev milestone: https://github.com/scala/scala-dev/milestone/23
Before the release
- [x] Notify community on https://contributors.scala-lang.org/c/announcements
- [x] Does macro paradise need any adjustments because of compiler changes? If so, make them
- [x] Create next milestone, move the "Merge to 2.12.x" description to it (default for new PRs)
- [x] Close the milestones
- [x] Triage scala/bug and scala/scala-dev tickets that target [version]
- [x] Check PRs assigned to the milestone, also check WIP
- [x] Check merged PRs for the next milestone in this branch, and assign them to this milestone
- [x] Check module versioning
- [x] Merge in older release branch
- [x] version number of release candidate is:
2.12.6-bin-d7ae7a8 - [x] Make sure the community build is green
- [x] bump version in
run.shif we haven't re-automated that yet: https://github.com/scala/community-builds/commit/8dbf83dd07c03e054480324a0c0ea6631ec5ea78 - [x] use the freeze script in the repo to freeze all the project SHAs: https://github.com/scala/community-builds/commit/f7f80ecb535adbdd8903e6a7c5b2d00fbc2a6e80
- [x] we do have a recent green run https://scala-ci.typesafe.com/view/scala-2.12.x/job/scala-2.12.x-integrate-community-build/2764/ and changes since then seem safe, but....
- [x] new run in progress:
https://scala-ci.typesafe.com/view/scala-2.12.x/job/scala-2.12.x-integrate-community-build/2765/https://scala-ci.typesafe.com/view/scala-2.12.x/job/scala-2.12.x-integrate-community-build/2766/~~gah, a bad Travis run I aborted had already deleted 2.12.6-bin-d7ae7a8 from the scala-ci artifactory before I could stop it. trying to re-publish now at https://travis-ci.org/scala/scala/jobs/371777774~~https://scala-ci.typesafe.com/view/scala-2.12.x/job/scala-2.12.x-integrate-community-build/2767/~~https://scala-ci.typesafe.com/view/scala-2.12.x/job/scala-2.12.x-integrate-community-build/2768/https://scala-ci.typesafe.com/view/scala-2.12.x/job/scala-2.12.x-integrate-community-build/2772/
- [x] bump version in
- [x] make sure the nightly Windows run is green
- can be triggered manually, you don't need to wait for the automatic one necessarily
- [x] recent runs are actually red, but I merged a PR that should fix them, and we already evaluated the failures as harmless. but anyway, let's do a new run:
- [x] https://scala-ci.typesafe.com/view/scala-2.12.x/job/scala-2.12.x-integrate-windows/962/ 馃挌
- [x] do extra JDK 9 and 10 testing
- [x] verify that minimal community build catches regressions of interest when run with previous release
- yup, it catches the macro bug
- [x] run minimal community build on Mac JDK 9
- [x] run minimal community build on Mac JDK 10
- [x] run minimal community build on Linux JDK 9
- [x] try a distro
- [x] any other combinations we should hit?
- [x] Windows?
- [x] verify that minimal community build catches regressions of interest when run with previous release
Release notes
- [x] PRs with release-notes label must have excellent title & description (title will be pasted literally in release note bullet list)
- [x] Draft release notes (to be published once GitHub tag is pushed)
- previous release, for reference: https://github.com/scala/scala/releases/v2.12.5
- draft in gist form, for sharing on Slack and Gitter and Discourse, to crowdsource mistake-spotting: https://gist.github.com/SethTisue/ebccff7e2b8b994771452880c7d3a0d9
- this release: https://github.com/scala/scala/releases/edit/v2.12.6
More release prep
- [x] Announce start of release process, point to release note gist for feedback
- [x] Close the scala/bug milestone, create next, move pending issues
- [x] Close the scala-dev milestone, create next, move pending issues
- [x] Double check
version.properties, maybe create a PR with updates
Stage the release
- [x] Trigger a build on travis, specify
SCALA_VER_BASEandSCALA_VER_SUFFIXin the custom config (e.g.before_install: export SCALA_VER_BASE=2.12.6 SCALA_VER_SUFFIX=)
- Check the build status on https://github.com/scala/scala/commits/2.12.x
- https://travis-ci.org/scala/scala/jobs/371920785
- https://travis-ci.org/scala/scala-dist/builds/371930449
https://ci.appveyor.com/project/scala/scala-dist/build/84https://travis-ci.org/scala/scala-dist-smoketest/builds/354330498- [x] Note the scala/scala@NNNNNN commit
- https://github.com/scala/scala/commit/d7ae7a8b9668d52699d1e1c5066a22ec89a1d379
- [x] Create the scala/scala tag locally:
git tag -s -m "Scala 2.12.6" v2.12.6 d7ae7a8b9668d52699d1e1c5066a22ec89a1d379 - [x] Note the scala/scala-dist@NNNNNN commit
- https://github.com/scala/scala-dist/commit/11da0884a4af4520c8704499c95bce10b731eafa
- [x] Create scala-dist tag locally:
git tag -s -m "Scala 2.12.6" v2.12.6 11da0884a4af4520c8704499c95bce10b731eafa - [x] Note the repos to be promoted after tag is cut (see travis log)
- https://oss.sonatype.org/content/repositories/orgscala-lang-1534
- https://oss.sonatype.org/content/repositories/orgscala-lang-1535
- https://oss.sonatype.org/content/repositories/orgscala-lang-1536
- https://oss.sonatype.org/content/repositories/orgscala-lang-1537
- https://oss.sonatype.org/content/repositories/orgscala-lang-1538
- [x] Sanity check jar/pom
- https://oss.sonatype.org/content/repositories/staging/org/scala-lang/scala-compiler/2.12.6/ (and check a module, too)
- [x] Announce release is staged at https://oss.sonatype.org/content/repositories/staging/ on https://contributors.scala-lang.org/c/announcements
More release notes stuff
- [x] Summarize release notes and submit to https://github.com/typesafehub/techhub-blog
- we didn't do this for 2.12.5, so, skipping for 2.12.6 too. do we only do this for .0 releases?
- [x] Prepare PR to https://github.com/scala/scala-lang/ (using scala/make-release-notes)
runMain MakeReleaseNotes 2.12.5 2.12.6 2018/04/27 /Users/tisue/scala.212documentation/api.mddownload/index.md_config.yml(update devscalaversion or scalaversion)- https://github.com/scala/scala-lang/pull/889
Soft point of no return
- these steps caaaaaan be redone (tags can be deleted and re-pushed, distros can be overwritten) but we'd reeeeeeally rather not have wrong tags or distros out there even briefly
- [x] Push scala/scala tag:
git push https://github.com/scala/scala.git v2.12.6 - [x] Push scala/scala-dist tag:
git push https://github.com/scala/scala-dist.git v2.12.6 - [x] Trigger two scala-dist jobs on travis (https://travis-ci.org/scala/scala-dist) with custom config
before_install: export version=2.12.6 scala_sha=d7ae7a8b9668d52699d1e1c5066a22ec89a1d379 mode=archiveshttps://travis-ci.org/scala/scala-dist/builds/372071551before_install: export version=2.12.6 scala_sha=d7ae7a8b9668d52699d1e1c5066a22ec89a1d379 mode=update-apihttps://travis-ci.org/scala/scala-dist/builds/372072090
Hard point of no return
- there is no such thing as un-publishing from Maven Central
- [x] Promote staging repos:
st_stagingRepoPromote [scala-repo],st_stagingRepoPromote [modules-repo](or use oss.sonatype.org web UI)
Check availability
- [x] Check release on sonatype: https://oss.sonatype.org/content/repositories/releases/org/scala-lang/scala-compiler/2.12.6/
- [x] Check the release on maven central: http://central.maven.org/maven2/org/scala-lang/scala-compiler/2.12.6/
- [x] Check the release on maven search (takes longer): http://search.maven.org/#search%7Cga%7C1%7Cg%3Aorg.scala-lang%20v%3A2.12.6
When everything is on maven central
- [x] make sure the draft release notes are on GitHub tag: https://github.com/scala/scala/releases/tag/v2.12.6
- [x] Pre-announce the release on https://contributors.scala-lang.org/c/announcements
- [x] Check that the API docs are published
- [x] Merge the scala-lang PR
- https://github.com/scala/scala-lang/pull/889
- [x] wait for it to reach https://www.scala-lang.org and make sure it looks okay
Announcements
- [x] Scala Users discourse https://users.scala-lang.org
- [x] add a reply on the same https://contributors.scala-lang.org thread where you announced that the release process was starting
- [x] Tweet from @scala_lang
- [x] https://gitter.im/scala/scala
- [x] if you feel like it, say something in https://gitter.im/scala/contributors too
- [x] ask Seth to announce on #scala IRC
Afterwards
- Create PR to update
versions.properties(new file generated by the bootstrap job) and thebaseVersioninbuild.sbt
- [x] submit PR: https://github.com/scala/scala/pull/6568
- [x] wait for Jenkins to be green, then merge it
- [x] Unfreeze the community build project SHAs (and bump
run.shto a version that includes the re-STARRing from the previous step) - [x] publish Fortify SCA for Scala (Seth)
- [ ] publish macro paradise (Adriaan has contacted Eugene B about getting access to do so)
SethTisue
🎉5
All 2 comments
ran https://github.com/SethTisue/community-builds/tree/wip-2.12.x-jdk9 on it:
[info] Project scala-------------------: SUCCESS (unchanged, not rebuilt)
[info] Project scala-js----------------: SUCCESS (project rebuilt ok)
[info] Project scala-js-stubs----------: SUCCESS (project rebuilt ok)
[info] Project scala-parser-combinators: SUCCESS (unchanged, not rebuilt)
[info] Project scalacheck--------------: SUCCESS (unchanged, not rebuilt)
[info] Project utest-------------------: SUCCESS (project rebuilt ok)
[info] >>> The dbuild result is------------: SUCCESS (project rebuilt ok)
UPDATES
- also ran the same thing on 2.12.5 to verify that the macro bug makes it fail.
- ran this on both Mac locally, and Linux via Jenkins
SethTisue
on 27 Apr 2018
🎉3
pending todos:
- release macro paradise (Adriaan & Eugene B)
- publish Fortify SCA for Scala (Seth)
- finish re-STARRING (Seth)
- unfreeze the 2.12 community build (Seth)
closing anyway, tracking in my own to-do list.
SethTisue
on 27 Apr 2018
Was this page helpful?
0 / 5 - 0 ratings
Related issues
lrytz
路
7Comments
retronym
路
7Comments
adriaanm
路
5Comments
adriaanm
路
6Comments
SethTisue
路
4Comments
Most helpful comment
ran https://github.com/SethTisue/community-builds/tree/wip-2.12.x-jdk9 on it:
UPDATES