Release 3.11.0 RC1

[mgallien]

📝 TO DO

• 🌲 Create the new stable branch for the desktop repository
  ⚠️ Only needed for the first release candidate.

$ git checkout master
$ git pull
$ git checkout -b stable-3.11
$ git push -u origin stable-3.11

• ⬆️ Bump VERSION.cmake to 3.11.50 in the master branch
• ⬆️ 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)
• 🏷️ Create tag from stable branch on the commit introducing the version bump

$ git checkout stable-3.11
$ git pull
$ git tag -s -m "Release 3.11.0-rc1" v3.11.0-rc1
$ git push origin v3.11.0-rc1

git remote add releases [email protected]:nextcloud-releases/desktop.git
git fetch origin v3.11.0-rc1
git push releases v3.11.0-rc1

• 🌲 Create the new stable branch for the client-building repository

$ git checkout master
$ git pull
$ git checkout -b stable-3.11
$ git push -u origin stable-3.11

• 🏭 Trigger the builds on brander and wait for them to succeed:
  • 🐧 Linux
  • 🍎 Mac OS
  • 🚪 Windows MSI
• 🧪 Execute the feature release test plan for each build:
  • 🐧 Linux
    • update from last release candidate (meaning that you have an existing account configured with the release candidate and use it with the official AppImage)
      • upload/download/check activity/check integration to file browser
      • check cpu usage during sync
      • tray menu interaction
      • test Talk notifications (receive notification, reply to a message)
    • fresh installation
      • configure a new account
      • upload/download/check activity/check integration to file browser
      • check cpu usage during sync
      • tray menu interaction
      • test Talk notifications (receive notification, reply to a message)
      • test important new feature from the release
  • 🍎 Mac OS
    ⚠️ Check the logs for:
    • Sharing succeeded: it needs to be signed similarly to .pkg file and uploaded everywhere.
    • Get the link after the last mention of Sharing succeeded to download the delta update file (.tbz) (required for automated upgrade).
    • update from last release candidate (meaning that you have an existing account configured with the release candidate and upgrade the installation via installer)
      • upload/download/check activity/check integration to file browser
      • check cpu usage during sync
      • tray menu interaction
      • test Talk notifications (receive notification, reply to a message)
    • fresh installation
      • configure a new account using VFS sync
        • upload/download/check activity/check integration to file browser
        • check cpu usage during sync
        • tray menu interaction
        • test Talk notifications (receive notification, reply to a message)
        • test important new feature from the release
      • configure a new account using selective sync
        • upload/download/check activity/check integration to file browser
        • check cpu usage during sync
        • tray menu interaction
        • test Talk notifications (receive notification, reply to a message)
  • 🚪 Windows MSI
    • update from last release candidate (meaning that you have an existing account configured with the release candidate and upgrade the installation via installer)
      • upload/download/check activity/check integration to file browser
      • check cpu usage during sync
      • tray menu interaction
      • test Talk notifications (receive notification, reply to a message)
    • fresh installation
      • configure a new account using VFS sync
        • upload/download/check activity/check integration to file browser
        • check cpu usage during sync
        • tray menu interaction
        • test Talk notifications (receive notification, reply to a message)
        • test important new feature from the release
      • configure a new account using selective sync
        • upload/download/check activity/check integration to file browser
        • check cpu usage during sync
        • tray menu interaction
        • test Talk notifications (receive notification, reply to a message)
• 🗝️ Sign binaries (ssh -P 2200 to signing VM, then, cat how-to-sign, then scp -P 2200 to download signatures)
• 📖 Create draft pre-release and release notes (click on Generate release notes) at:
  • nextcloud/desktop/releases
    ⚠️ Only add the release notes. Do not upload the binaries to nextcloud/desktop/releases.
  • nextcloud-releases/desktop/releases
    ⚠️ Copy the changelog from nextcloud/desktop/releases.
• 📦 Upload binaries to:
  • the draft pre-release at nextcloud-releases/desktop/releases
  • download.nextcloud.com in the user home directory (so still private)
• 🚀 Publish the draft pre-releases created previously at:
  • nextcloud/desktop/releases
    :warning: No binaries on this release page.
  • 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
  • 🛎️ Notify Marketing that the release is ready
• Create the milestone for X.(Y+1).0
• 📝 Update the documentation:
  • Create an issue for the sysadmins to make sure https://docs.nextcloud.com/desktop/3.11 exists.
  • Consider also adding to the docs the new features included in the release.
  • Adjust if needed https://docs.nextcloud.com/server/latest/admin_manual/installation/system_requirements.html#desktop-client
• 🆙 Change the values of $betaReleaseDate and $betaVersion in the updater server config to serve the release.
  ⚠️ For the mac update service: the sparkle:edSignature and length values are printed right after the last mention of Sharing succeeded in the brander build log. Replace the values "signature" and "length" under 'macos' in 'beta' with them.
  • Make sure betaVersionInternal is set to X.(Y-1).8Z, while betaVersion is set to 3.11.0-rc1 in the config/config.php.
• 📧 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.

[camilasan]

nextcloud/client_updater_server#126