You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
π·οΈ Create tag from corresponding stable branch in client-building. Steps to create the tag are the same as the above.
π Trigger the builds on brander and wait for them to succeed:
π§ Linux
π Mac OS
πͺ Windows MSI
π§ͺ Execute the bugfix 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)
check cpu usage during sync
test important new fixes in this 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)
check cpu usage during sync
test important new fixes in this 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)
check cpu usage during sync
πͺ 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)
check cpu usage during sync
test important new fixes in this 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)
check cpu usage during sync
ποΈ 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.
Close the milestone for 3.12.7 (make sure every merged PR is included)
Create the milestone for X.Y.(Z+1) (make sure every merged PR is included)
π 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.
π 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.
The text was updated successfully, but these errors were encountered:
π TO DO
ssh -P 2200
to signing VM, then,cat how-to-sign
, thenscp -P 2200
to download signatures)Generate release notes
) at:β οΈ Only add the release notes. Do not upload the binaries to nextcloud/desktop/releases.
β οΈ No binaries on this release page.
publish_desktop.sh
script on download.nextcloud.com so that the binaries appear at download.nextcloud.com/desktop/releases.htaccess
such that latest alias point toward the new release (for example https://download.nextcloud.com/desktop/releases/Windows/latest)$stableReleaseDate
and$stableVersion
in the updater server config to serve the release."signature"
and"length"
under'macos'
in'stable'
with them.The text was updated successfully, but these errors were encountered: