Release 3.9.0

[mgallien]

:memo: TO DO

• [x] :mailbox: 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
• [x] :clock1: wait 7 days
• [x] :arrow_up: Bump VERSION.cmake to 3.9.0 and doc/conf.py (release to 3.9.0 and version to 3.9) in the master branch
• [x] :label: Create tag from master on the commit introducing the version bump

  $ git checkout stable-3.9
  $ git pull
  $ git tag -s -m "Release 3.9.0" v3.9.0
  $ git push origin v3.9.0

  git remote add releases git@github.com:nextcloud-releases/desktop.git
  git fetch origin v3.9.0
  git push releases v3.9.0

• [x] :evergreen_tree: Create the new stable branch for the client-building repository

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

• :factory: Trigger the builds on brander and wait for them to succeed:
  • [x] :penguin: Linux
  • [x] :apple: Mac OS
  • [x] :door: Windows MSI
• :test_tube: Execute the feature release test plan for each build:
  • [x] :penguin: Linux
  • [x] :apple: Mac OS ⚠️ Check the logs for:
    • [x] Sharing succeeded: it needs to be signed similarly to .pkg file and uploaded everywhere.
    • [x] Get the link after the last mention of Sharing succeeded to download the delta update file (.tbz) (required for automated upgrade).
  • [x] :door: Windows MSI
• [x] :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:
  • [x] nextcloud/desktop/releases ⚠️ Only add the release notes. Do not upload the binaries to nextcloud/desktop/releases.
  • [x] nextcloud-releases/desktop/releases (copy the changelog from nextcloud/desktop/releases)
• :package: Upload binaries to:
  • [x] the draft pre-release at nextcloud-releases/desktop/releases
  • [x] download.nextcloud.com in the user home directory (so still private)
• [x] :bellhop_bell: Notify Marketing that the release is ready
• :rocket: When marketing gives the go then publish the draft pre-releases created previously at:
  • [x] nextcloud/desktop/releases ⚠️ No binaries on this release page.
  • [x] nextcloud-releases/desktop/releases
  • [x] Run the publish_desktop.sh script on download.nextcloud.com so that the binaries appear at download.nextcloud.com/desktop/releases
  • [x] 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)
• [x] :up: Change the updater server config to serve the release.
• [x] :up: Change the values of $stableReleaseDate and $stableVersion 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 'stable' with them.
• :memo: Update the documentation:
  • [x] Create an issue for the sysadmins to make sure https://docs.nextcloud.com/desktop/3.9 exists.
  • [x] Add 3.9.0 to https://docs.nextcloud.com/ as the latest release.
  • [ ] Consider also adding to the docs the new features included in the release.
  • [x] Adjust if needed https://docs.nextcloud.com/server/latest/admin_manual/installation/system_requirements.html#desktop-client
• [x] :up: Change the install-clients page to update the link to the latest release on Nextcloud website (direct modification via wordpress web ui)
• [x] 📧 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.

[mathisdt]

Regarding the item Upload binaries to the draft pre-release at nextcloud-releases/desktop/releases: There seems to be a problem, the release (and the RCs starting with 3.9.0-rc2) don't have any binaries. Could you please attach them? This would be a great help for my scripted client update which fetches the AppImage from the latest release (which runs into an error currently) - thanks!

[mgallien]

@mathisdt they are now only uploaded to https://github.com/nextcloud-releases/desktop/releases and https://download.nextcloud.com/desktop/releases/Windows this is done to make sure what you download is legitimate and really what we built and released I am sorry if that generates more work for you but I highly suggest to simply switch to getting the releases from nextcloud-releases organization as that was a project wide policy change

[mathisdt]

@mgallien Thanks for the hint about nextcloud-releases! I only had to change the organisation and it worked again. BTW, the script is documented at https://zephyrsoft.org/nextcloud-client-updates/ (in case someone stumbles over this later).

[mgallien]

@mgallien Thanks for the hint about nextcloud-releases! I only had to change the organisation and it worked again. BTW, the script is documented at https://zephyrsoft.org/nextcloud-client-updates/ (in case someone stumbles over this later).

there was some contributions toward having auto updated AppImage I was never really able to have time to push this and properly work with the contributors (in part because of my lack of time and in part because of my lack of knowledge) hopefully at a point they will properly auto update making us able to rely on the updater mechanism that is built into AppImage