3.3.1-RC3 Release procedure

[Kordyjan]

• Backport relevant fix:
  • Add clause for protected visibility from package objects #18134
    • Backport "Add clause for protected visibility from package objects" #18148
• Publish artifacts to Maven via CI
  • On release-3.3.1 branch:
    • In Build.scala: Set baseVersion to 3.3.1-RC3
    • In Build.scala: Set previousDottyVersion to 3.3.1-RC2
    • in changelogs add file with a changelog
    • Tag the branch as 3.3.1-RC3
• On main:
  • In Build.scala: Set referenceVersion to 3.3.1-RC3
  • Set reference version to 3.3.1-RC3 #18154
• Announce the release
  • Publish release on GitHub Releases
  • Comment on the announcement thread on https://contributors.scala-lang.org

[He-Pin]

@Kordyjan Hi I'm wondering how do you keep track which commit/pr need to be back-ported to 3.3.x from master?

[Kordyjan]

I'm wondering how do you keep track which commit/pr need to be back-ported to 3.3.x from master?

I'm just tracking backport:nominated and backport:accepted labels.

main is still 3.3.x though. Once we start working on 3.4, there will be some changes to the workflow.