Release X.Y.0-rcZ

[er-vin]

:memo: TO DO

• [ ] :evergreen_tree: Create the new stable branch for the desktop repository (only done for the first release candidate)

$ git checkout master
$ git pull
$ git checkout -b stable-X.Y
$ git push -u origin stable-X.Y

• [ ] :arrow_up: Bump VERSION.cmake to X.Y.50 in the master branch
• [ ] :arrow_up: Bump VERSION.cmake to X.(Y-1).8Z in the stable branch (e.g.: If you want to make a pre-release rc1 for 3.2.0 then bump to 3.1.81, a rc2 for instance will be 3.1.82 and so on) and doc/conf.py (release to X.(Y-1).8Z or X.(Y-1).9Z in the same way)
• [ ] :label: Create tag from stable branch on the commit introducing the version bump

$ git checkout stable-X.Y
$ git pull
$ git tag -s -m "Release X.Y.0-rcZ" vX.Y.0-rcZ
$ git push origin vX.Y.0-rcZ

• :factory: Trigger the builds on brander and wait for them to succeed:
  • [ ] :penguin: Linux
  • [ ] :apple: Mac OS
  • [ ] :door: Windows MSI
• :test_tube: Execute the feature release test plan for each build:
  • [ ] :penguin: Linux
  • [ ] :apple: Mac OS
    • [ ] ⚠️ Have a look at the build log on brander to also download the delta update file (.tbz) required for automated upgrade: Sharing succeeded (it needs to be signed similarly to .pkg file and uploaded everywhere)
  • [ ] :door: Windows MSI
• [ ] :old_key: Sign binaries (ssh -P 2200 to signing VM, then, cat how-to-sign, then scp -P 2200 to download signatures)
• :book: Create draft pre-release and release notes (click on Generate release notes) at:
  • [ ] nextcloud/desktop/releases
  • [ ] nextcloud-releases/desktop/releases (copy the changelog from nextcloud/desktop/releases)
• :package: Upload binaries to:
  • [ ] the draft pre-release at nextcloud/desktop/releases
  • [ ] the draft pre-release at nextcloud-releases/desktop/releases
  • [ ] download.nextcloud.com in the user home directory (so still private)
• [ ] :bellhop_bell: Notify Marketing that the release is ready
• :rocket: When marketing has been notified then publish the draft pre-releases created previously at:
  • [ ] nextcloud/desktop/releases
  • [ ] nextcloud-releases/desktop/releases
  • [ ] run the publish_pre_release_desktop.sh script on download.nextcloud.com so that the binaries appear at download.nextcloud.com/desktop/releases
• [ ] :up: Change the values of $betaReleaseDate and $betaVersion in the updater server config to serve the release.
  • [ ] For the mac update service, you need find the value of sparkle:edSignature and length in the brander build log (near the very end of the build log) and replace the values "signature" and "length" under 'macos' in 'beta'.
  • [ ] make sure betaVersionInternal is set to X.(Y-1).8Z, while betaVersion is set to X.Y.0-rcZ in the config/config.php
• [ ] :up: Change the install-clients page to update the link to the latest release on Nextcloud website (direct modification via wordpress web ui)
• [ ] 📧 E-mail the company internal mailing list about the new release candidate: just a reminder for them to help testing the release candidate and report issues they might find.