New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Release 2.13.0-M5 #544

Closed
SethTisue opened this Issue Aug 21, 2018 · 3 comments

Comments

Projects
None yet
1 participant
@SethTisue
Copy link
Member

SethTisue commented Aug 21, 2018

Before the release

  • Notify community on https://contributors.scala-lang.org/c/announcements
  • 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
  • Triage scala/bug and scala/scala-dev tickets
  • Check PRs assigned to the milestone, also check WIP
  • Check merged PRs for the next milestone in this branch, and assign them to this milestone
  • Merge in older release branch
  • Make sure the community build is green
  • make sure the Windows Jenkins job is green
  • make sure scala-collections-laws is green
    • this is an easy to forget step as we don't have proper automation for this. for M5 we did only a quick run and a quick eyeball of the results (not green, because of the big collections overhaul), we should do better for RC1

Stage the release

Release notes

  • Review merged PRs, make sure release-notes label is applied appropriately
  • PRs with release-notes label must have excellent title & description (title will be pasted literally in release note bullet list)
  • Draft release notes (to be published once GitHub tag is pushed)
  • On contributors thread, link to release note gist and request feedback
  • Prepare PR to https://github.com/scala/scala-lang/ (using scala/make-release-notes)

Soft point of no return

Hard point of no return

  • there is no such thing as un-publishing from Maven Central
  • Promote staging repos: st_stagingRepoPromote [scala-repo], st_stagingRepoPromote [modules-repo] (or use oss.sonatype.org web UI)

Check availability

When everything is on maven central

Modules

Announcements

Afterwards

  • Create PR to update versions.properties (new file generated by the bootstrap job) and (if appropriate) the baseVersion in build.sbt

@SethTisue SethTisue self-assigned this Aug 21, 2018

@SethTisue

This comment has been minimized.

Copy link
Member

SethTisue commented Aug 28, 2018

separate ticket on trials and tribulations of re-staging and re-building: #550

@SethTisue

This comment has been minimized.

Copy link
Member

SethTisue commented Aug 28, 2018

a couple user-visible differences that distinguish the two builds:

  • size in bytes of scala-2.13.0-M5.tgz:
    • old build: 17712216
    • new build: 17721111
  • scala.concurrent.duration.Duration.Inf.isFinite()
    • old build: compiles
    • new build: fails with error: Boolean does not take parameters
  • in the scala.math package-level Scaladoc, at e.g. https://www.scala-lang.org/api/2.13.0-M5/scala/math/index.html
    • old build: "scala.collection.TraversableOnce has min and max methods"
    • new build: "scala.collection.IterableOnceOps has min and max methods"
@SethTisue

This comment has been minimized.

Copy link
Member

SethTisue commented Aug 30, 2018

It is done.

@SethTisue SethTisue closed this Aug 30, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment