Skip to content
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-RC2 #626

Closed
adriaanm opened this issue May 16, 2019 · 6 comments

Comments

Projects
None yet
3 participants
@adriaanm
Copy link
Member

commented May 16, 2019

For every Scala release, make a copy of this file named after the release, and expand the variables.
Ideally this should become a script you can run on your local machine. The only missing piece is programmatic triggering of travis jobs with custom config.

Variables to be expanded in this template:

  • SCALA_VER_BASE="2.13.0"
  • SCALA_VER_SUFFIX="-RC2"
  • SCALA_SHA=06392a55749f34ece097863c50a2af3fd6b3a88b
  • DIST_SHA=4507b42f85a51cec140d1fb230a2ea34d02eb697
  • SCALA_VER="$SCALA_VER_BASE$SCALA_VER_SUFFIX"

Key links:

N weeks before the release

  • 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
  • Announce expected release date and current nightly "release candidate" (nightly sha-mangled version) at https://scala-ci.typesafe.com/artifactory/scala-integration/ on https://contributors.scala-lang.org/c/announcements

Release announcement / notes

N days before release

  • Announce no more PRs will be merged unless last-minute regressions are found. Re-iterate current nightly sha version for testing.
  • Community build
  • Run scala-collections-laws and evaluate results
    • Rex Kerr (@Ichoran) is the keeper and expert on this
  • !!! Windows Jenkins job
  • Check any merged PRs accidentally assigned to the next milestone in this branch, and re-assign them to this milestone
  • Merge in any older release branch (decided not to)
  • Check module versioning (is everything in versions.properties up to date?)
  • On major release, bump PickleFormat version

Point of no return

Check availability

When everything is on maven central

Modules

Announcements

Afterwards

@adriaanm

This comment has been minimized.

Copy link
Member Author

commented May 16, 2019

Sorry, I forgot to create this ticket earlier. Will be tagging and staging RC2 today!

@adriaanm

This comment has been minimized.

Copy link
Member Author

commented May 16, 2019

Transcript:

➜  ~ export SCALA_VER_BASE="2.13.0" SCALA_VER_SUFFIX="-RC2" SCALA_SHA=06392a55749f34ece097863c50a2af3fd6b3a88b DIST_SHA=4507b42f85a51cec140d1fb230a2ea34d02eb697 
export SCALA_VER="$SCALA_VER_BASE$SCALA_VER_SUFFIX"

➜  ~ echo "before_install: export SCALA_VER_BASE=$SCALA_VER_BASE SCALA_VER_SUFFIX=$SCALA_VER_SUFFIX"
before_install: export SCALA_VER_BASE=2.13.0 SCALA_VER_SUFFIX=-RC2

➜  ~ cd git/scala           
➜  scala git:(2.13.x) g fetch scala                                          
➜  scala git:(2.13.x) git tag -s -m "Scala $SCALA_VER" v$SCALA_VER $SCALA_SHA
➜  scala git:(2.13.x) g show v2.13.0-RC2                                     

➜  scala git:(2.13.x) cd ../scala-dist      
➜  scala-dist git:(2.13.x) g fetch scala     
➜  scala-dist git:(2.13.x) git tag -s -m "Scala $SCALA_VER" v$SCALA_VER $DIST_SHA
➜  scala-dist git:(2.13.x) g show v2.13.0-RC2                                     

➜  scala-dist git:(2.13.x) echo "before_install: export version=$SCALA_VER scala_sha=$SCALA_SHA mode=release"             
before_install: export version=2.13.0-RC2 scala_sha=06392a55749f34ece097863c50a2af3fd6b3a88b mode=release
@adriaanm

This comment has been minimized.

Copy link
Member Author

commented May 16, 2019

The update-api part of scala-dist again failed to update the symlink. Running the exact same ssh invocation from my machine worked fine:

ssh scalatest@chara.epfl.ch -i ~/.ssh/for_chara 'cd ~linuxsoft/archives/scala/api/ ; [[ -d 2.13.0-RC2 ]] && ln -sfn 2.13.0-RC2 2.13.x'
@lrytz

This comment has been minimized.

Copy link
Member

commented May 16, 2019

We had the same for RC1 #599

@adriaanm

This comment has been minimized.

Copy link
Member Author

commented May 16, 2019

Yeah, I wonder why.

@SethTisue

This comment has been minimized.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.