desktop
desktop copied to clipboard
Release X.Y.0
:memo: TO DO
- [ ] :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
- [ ] :clock1: wait 7 days
- [ ] :arrow_up: Bump VERSION.cmake to X.Y.0 and doc/conf.py (release to X.Y.0 and version to X.Y) in the master branch
- [ ] :label: Create tag from master on the commit introducing the version bump
$ git checkout stable-X.Y
$ git pull
$ git tag -s -m "Release X.Y.0" vX.Y.0
$ git push origin vX.Y.0
- [ ] :evergreen_tree: Create the new stable branch for the client-building repository
$ git checkout master
$ git pull
$ git checkout -b stable-X.Y
$ git push -u origin stable-X.Y
- :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
, thenscp -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 gives the go then publish the draft pre-releases created previously at:
- [ ] 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
- [ ] :up: Change the updater server config to serve the release.
- [ ] :up: Change the values of
$stableReleaseDate
and$stableVersion
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'stable'
.
- [ ] 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
- :memo: Update the documentation:
- [ ] Create an issue for the sysadmins to make sure https://docs.nextcloud.com/desktop/X.Y exists.
- [ ] Add X.Y.0 to https://docs.nextcloud.com/ as the latest release.
- [ ] 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
- [ ] :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 client: just a reminder for them to update to the latest client and to report any issues they might find.