2.4.3

[guruz]

Some weeks before the release:

• Check if we should update the bundled sqlite3 (https://github.com/owncloud/client/tree/master/src/3rdparty/sqlite3)
• Check if we should update Sparkle on build machine (https://github.com/sparkle-project/Sparkle/releases)
• Ensure NSIS is up to date on the build machine
• Ensure up-to-date dependencies (e.g. latest Qt version is installed on the machine and picked up (cmake output)
• Ensure the crash reporter server is up
• Check crash reporter for bad crashes
• Ensure Windows Overlay DLLs are rebuilt
• Check nightly builds are up and running, that is Jenkins jobs ownCloud-client-linux, ownCloud-client-osx and ownCloud-client-win32 all green.
• Ensure Linux nightlies are built too for all distros https://build.opensuse.org/package/show/isv:ownCloud:community:nightly/owncloud-client
  • Check if patches still apply in the linux packages
• Build branded clients through the scripting machine and smoke test one or two branded clients (especially with predefined url)
• Upload a nightly build of the windows version to virustotal.com
  • Contact AV vendors whom's engine reports a virus
• Documentation should be online before the release http://doc.owncloud.org/desktop/1.X/
• QA goes over https://github.com/owncloud/client/wiki/Testing-Scenarios
• Make sure to have client/ChangeLog updated
• use git log --format=oneline v<lastrelease>...master if your memory fails you
• check if enterprise issues are fixed

2.4.3 rc1

• Add last updates to Changelog in the client source repository.
• Branch off a release branch called VERSION-rcX or VERSION-betaX (without v, v is for tags)
• Edit VERSION.cmake to set the suffix to beta1, beta2 etc. Commit the result to the release branch only
• Make sure to increase the version number of the branched of release, e.g. if you release 2.3.2 then you should change VERSION.cmake in 2.3 to 2.3.3 since that branch now will be 2.3.3
• Create build for theme 'ownCloud' using client-trigger (uncheck the "nightly build" checkbox, use the proper dropdown for version suffix)
• Create build for theme 'testpilotcloud' using client-trigger (uncheck the "nightly build" checkbox, use the proper dropdown for version suffix)
• Only now download the owncloudclient-*.tar.xz and sign it with gpg. Copy the signature into a new .asc file. (20180719jw: no more timing issue since client-trigger uses client-source-branded)
  (see https://github.com/owncloud/enterprise/wiki/Desktop-Signing-Knowledge)
• Build results are in https://download.owncloud.com/desktop/testing -- win and mac binaries are there, linux packages are listed in a *repo.html file.
• Mac: Perform smoke test (Install, make sure it does not explode, and check if all version indicators are correct)
• Win: Perform smoke test (Install, make sure it does not explode, and check if all version indicators are correct)
• Linux: Smoke test of one distro package (Install, make sure it does not explode, and check if all version indicators are correct)
• Linux: Run client-linux-tests ob for @SamuAlfageme 's magic Linux-test-all-packages-script
• Create a signed tag using git tag -u E94E7B37 tagname (https://github.com/owncloud/enterprise/wiki/Desktop-Signing-Knowledge)
• update the wordpress content at owncloud.org (20180719 jw: FIXME: clarify, no more staging??)
• Inform packagers @dragotin (openSUSE), @hefee (Debian), ??? (Fedora)
• Announce on https://central.owncloud.org
• Inform community mailinglists [email protected] and [email protected] (make sure to mention it is an rc). Link to the central post so discussion happens there.
• Check crash reporter

One week before the final release:

• Communicate the release schedule on mailinglist [email protected]. Give a high level overview of the upcoming new features, changes etc.
• Ensure marketing is aware ([email protected]) and prepared for the release (social, .com website, cust. communications)
• Inform GCX knows the next version is about 1 week out ([email protected])

Day before final Release:

• Check the translations coming from transifex: All synchronized?
• Run the tx.pl scripts on the final code tag
• Run make test
• Run smashbox (20180719 jw: FIXME: add details, how?)
• Inform product management and marketing that we are 1 day out

On Release Day (for final release):

• Add last updates to Changelog in the client source repository.
• Branch off a release branch called VERSION (without v, v is for tags)
• Edit VERSION.cmake to set the suffix to "" etc. Commit the result to the release branch only
• Create build for theme 'ownCloud' using client-trigger (uncheck the "nightly build" checkbox, use the proper dropdown for version suffix)
• Create build for theme 'testpilotcloud' using client-trigger (uncheck the "nightly build" checkbox, use the proper dropdown for version suffix)
• Only now download the owncloudclient-*.tar.xz and sign it with gpg. Copy the signature into a new .asc file. (20180719jw: no more timing issue since client-trigger uses client-source-branded)
  (see https://github.com/owncloud/enterprise/wiki/Desktop-Signing-Knowledge)
• Build results are in https://download.owncloud.com/desktop/testing -- win and mac binaries are there, linux packages are listed in a *repo.html file.
• Branch isv:ownCloud:desktop to isv:ownCloud:desktop:client-X.Y.Z before overwriting https://github.com/owncloud/administration/blob/master/jenkins/obs_integration/obs-backup-prj.sh (the linux packages will land in the :testing repository still)
  obs-backup-prj.sh isv:ownCloud:desktop isv:ownCloud:desktop:client-2.4.1 owncloud-client 2.4.1 # (if not already done)
• Re-download Mac builds and check signature. Interactive in installer window
• Re-download Win build check signature. From Mac or Linux: osslsigncode verify ownCloud-version-setup.exe
• Mac: Perform smoke test (Install, make sure it does not explode, and check if all version indicators are correct)
• Win: Perform smoke test (Install, make sure it does not explode, and check if all version indicators are correct)
• Linux: Smoke test of one distro package (Install, make sure it does not explode, and check if all version indicators are correct)
• Linux: Run @SamuAlfageme 's client-linux-tests Jenkins job (this tests only package installations!) Adjust REPO_URL in https://jenkins.int.owncloud.com/job/client-linux-tests/build (Better: gitlab? running the test in gitlab would be better for public transparency, but only jenkins can set the parameters easily)
• Win/Mac Copy builds from testing to stable on download.owncloud.com, double check the download links. (make sure the .asc is there too)
• Linux: disable publishing on project isv:ownCloud:desktop
• Linux: Use https://github.com/owncloud/administration/blob/master/jenkins/obs_integration/obs-deepcopy-prj.sh to copy from isv:ownCloud:community:testing to isv:ownCloud:desktop
  obs-deepcopy-prj.sh isv:ownCloud:desktop:testing isv:ownCloud:desktop
obs-deepcopy-prj.sh isv:ownCloud:testpilot:testing isv:ownCloud:testpilot
• check osc meta prj for needed updates between :desktop:testing and :desktop
• Linux: Re-enable OBS publishing on the project after official release date and if all distros build (check for accidentially disabled packages too)
• Linux: Wait until everything is built and published, then disable publishing on project isv:ownCloud:desktop
• Create git signed tag in client repository using git tag -u E94E7B37 tagname (https://github.com/owncloud/enterprise/wiki/Desktop-Signing-Knowledge)
• Create a (draft) release on https://github.com/owncloud/client/releases
• Update https://owncloud.org/changelog/desktop-client/
• Update https://owncloud.org/download/#owncloud-desktop-client -> Download ownCloud -> click open 'Desktop Client', edit win/mac/lin, each all three tabs "Production", "Technical Preview" [disabled], "Test pilot" enabled, edit the links.
• Announce on https://central.owncloud.org
• Announce on [email protected] Link to the central post so discussion happens there.
• Inform packagers @dragotin (openSUSE) @hefee (Debian) @Germano0 (Fedora)
• Send out Social (tweet, blog, other)
• Send out customer communication (if any)
• Inform GCX that the new version is released ([email protected])
• Inform [email protected]
• Ensure marketing is aware ([email protected])
• Take pride and celebrate!
• Tell GCX to increment the minimum supported version for enterprise customers
• Check if minimum.supported.desktop.version (https://github.com/owncloud/core/blob/master/config/config.sample.php#L1152) needs to be updated in server

15 minutes after after release:

• Test all advertised download links to have the expected version
• Check for build errors in OBS, do
  obs-deepcopy-prj.sh isv:ownCloud:desktop isv:ownCloud:desktop:client-2.X.X
• disable publishing in OBS to prevent that accidential rebuilds hit the end users.

A few days after the release (for final release)

• Review changes in the release branch, merge back into master
• check the crash reporter if auto update is a good idea or we need a new release
• Update the updater script clientupdater.php https://github.com/owncloud/enterprise/wiki/How-to-use-the-Client-Updater#updating-the-owncloud-hosted-updater
• Execute announced deprecations. Disable builds for deprecated platforms. Update accordingly: https://doc.owncloud.org/server/latest/admin_manual/installation/system_requirements.html#desktop
• Increment version number in nightly builds. Special case: after the last release in a branch, jump forward to the 'next release branch'... That may mean, this is nightly is the same as edge then.

[guruz]

45bf2e9 cherry-picked into 2.4 as 628daea

#6698 backport 2.4 needed -> DONE 235e314

d0bdccc backport 2.4 needed -> DONE 8c77bfa (for #6610)

[guruz]

Heads-up to @dragotin (openSUSE), @hefee (Debian)

[jnweiger]

obs backups done:

• https://build.opensuse.org/project/show/isv:ownCloud:desktop:client-2.4.2 (was already there)
• https://build.opensuse.org/project/show/isv:ownCloud:desktop:client-2.4.3 (new)

publishing disabled on :desktop,

[jnweiger]

Samuel's install test with 2.4.3 final: https://jenkins.int.owncloud.com/job/client-linux-tests/76/console
ERROR: 6 tests failed: 'test:Debian_8' 'test:Debian_9' 'test:Ubuntu_14.04' 'test:Ubuntu_16.04' 'test:Ubuntu_17.10' 'test:Ubuntu_18.04'

public key is not available: NO_PUBKEY 724E656F8287C4A8

Hmm, that is something new. Needs manual confirmation....

[guruz]

@dragotin @hefee https://download.owncloud.com/desktop/stable/owncloudclient-2.4.3.tar.xz

[jnweiger]

publishing for 2.4.3 enabled on

• https://build.opensuse.org/project/show/isv:ownCloud:desktop
• https://build.opensuse.org/project/show/isv:ownCloud:testpilot

[jnweiger]

owncloud.org/download links production updated to 2.4.3 (mac, win, lin)
(testing links remain at 2.50beta1, -- and yes, there is no staging any more for wordpress, afaik)

[guruz]

GitHub release: https://github.com/owncloud/client/releases/tag/v2.4.3

Announcements mail: https://mailman.owncloud.org/pipermail/announcements/2018-August/000104.html

Central post: Not worth to make a new post so I just commented on https://central.owncloud.org/t/desktop-sync-client-2-4-2-released/14408/3?u=guruz

CC @michaelstingl @felixboehm @pmaier1