Release 3.15.0

[mgallien]

📝 TO DO

🏷️ Tagging

• 🎯 Check the milestone for 3.15.0 to make sure every merged PR is included.
• Send a mail to marketing with a changelog generated using github_helper scripts, with previous feature release as origin point and finishing at latest commit in master branch and the expected release date no sooner than 7 days later
• 🕐 wait 7 days
• Bump VERSION.cmake to 3.15.0 and doc/conf.py (release to 3.15.0 and version to 3.15) in the stable branch
• Create tag from stable branch on the commit introducing the version bump

$ git checkout stable-3.15
$ git pull
$ git tag -s -m "Release 3.15.0" v3.15.0
$ git push origin v3.15.0

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

🏭 Building: trigger the builds on brander and wait for them to succeed

• Linux
• Mac OS
• Mac OS VFS (virtual file system/file provider)
• Windows MSI

🧪 Testing: 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 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
      • 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)
      • check cpu usage during sync
    • 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)
      • check cpu usage during sync
• test important new feature from the release

🍎 Mac OS

• 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
      • 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)
      • check cpu usage during sync
    • 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)
      • check cpu usage during sync
• test important new feature from the release

🍎 Mac OS VFS

• 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
      • 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)
      • check cpu usage during sync
• test important new feature from the release

🚪 Windows

• 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 with VFS
      • 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)
      • check cpu usage during sync
    • 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)
      • check cpu usage during sync
• test important new feature from the release

🗝️ Signing

• Download the delta update file (.tbz) of the mac OS build.
• Download the delta update file (.tbz) of the mac OS VFS build.

Tip

The .tbz file is required for automated upgrade. The link is located after the last mention of Sharing succeeded in the build logs. The file needs to be signed similarly to the .pkg file and uploaded everywhere.

• Sign binaries (ssh -P 2200 to signing VM, then, cat how-to-sign, then scp -P 2200 to download signatures)

🚀 Publishing

• Close the milestone for 3.15.0

📖 Changelog: create draft pre-release and release notes (click on Generate release notes) at:

• nextcloud/desktop/releases

Warning

Only add the release notes to nextcloud/desktop/releases.
🚨 For security reasons, the binaries are only uploaded to nextcloud-releases/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)

📧 Marketing:

• notify Marketing that the release is ready.

🔈 When marketing gives the go then publish the draft pre-releases created previously at:

• nextcloud/desktop/releases

Caution

🚨 No binaries in nextcloud/desktop/releases

• nextcloud-releases/desktop/releases
• Run the publish_desktop.sh script on download.nextcloud.com so that the binaries appear at download.nextcloud.com/desktop/releases
• Ask sysadmin to update the .htaccess such that latest alias point toward the new release (for example https://download.nextcloud.com/desktop/releases/Windows/latest)

📝 Update the documentation:

• Add 3.15.0 to https://docs.nextcloud.com/ as the latest release.
• Make sure the link to the latest documentation (https://docs.nextcloud.com/desktop/latest/) is updated by sysadmin

🆕 Release via the updater server:

• In the updater server config change the following values to serve the release:
  • $stableReleaseDate
  • $fileProviderStableReleaseDate
  • $stableVersion
  • $fileProviderStableVersion

Warning

The mac update service needs the signature and length values in order to work: the sparkle:edSignature and length values are printed right after the last mention of Sharing succeeded in the build log.

• 🍎 Under stable, update the following values for macos :
  • signature
  • length
  • fileProviderSignature
  • fileProviderLength

🌐 Update the website and users:

• Ping marketing (Peter specifically via e-mail or chat) to change the install-clients page to update the link to the latest release on Nextcloud website.
• E-mail the company internal mailing list about the new client: just a reminder for them to update to the latest client and to report any issues they might find.
• Ensure that desktop client links work on website and release packages are downloaded fine
• Also test links on portal and that release packages are downloaded fine