Client: 2.6.0

Created on 1 Mar 2019  路  58Comments  路  Source: owncloud/client

Some weeks before the release:

  • [x] 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)
  • [x] Ensure up-to-date dependencies (e.g. latest Qt version is installed on the machine and picked up (cmake output)
  • [x] Ensure the crash reporter server is up
  • [ ] Check crash reporter for bad crashes
  • [x] Check daily builds are up and running, that is Jenkins.int jobs client-linux, client-osx and client-win32-msvc, client-win32--msvc-msi all green.
  • [x] Ensure Linux daily builds are built too for all distros https://build.opensuse.org/package/show/isv:ownCloud:desktop:daily:2.X/owncloud-client
  • [ ] Build branded clients through the scripting machine and smoke test one or two branded clients (especially with predefined url)
  • [x] Upload a daily 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/2.X/
  • [ ] QA goes over https://github.com/owncloud/client/wiki/Testing-Scenarios
  • [x] 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

For first Alpha/Beta of a minor release:

  • [ ] branch off master to new version branch (e.g. master -> 2.1, when releasing 2.1)
  • [x] Adjust VERSION.cmake in master and count up (e.g. 2.2)
  • [ ] Add the new branch v2.X.X for the new version to gitea/jw/client-linux-build
  • [x] Add the new version to gitea/ownbrander/scripting/client-linux/templates/client/2.X.X
  • [ ] Add branch to branches.only section in appveyor.yml, so PRs to that branch will be built by AppVeyor
  • [ ] Adjust translation jobs for client to point to the release branch (e.g. 2.1).
  • [ ] Make sure there is a job for the docs of the new master branch and the current release branch on rotor e.g. http://doc.owncloud.org/desktop/1.X/ exists

Alpha1:

  • [x] Add last updates to Changelog in the client source repository.
  • [x] Branch off a release branch called VERSION-rcX or VERSION-betaX (without v, v is for tags)
  • [x] Edit VERSION.cmake to set the suffix to beta1, beta2 etc. Commit the result to the release branch only
  • [x] 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
  • [x] Create build for theme 'ownCloud' using client-trigger (uncheck the "daily build" checkbox, use rcX or betaX dropdown for version suffix)
  • [x] Create build for theme 'testpilotcloud' using client-trigger (uncheck the "daily build" checkbox, use the rcX or betaX dropdown for version suffix)
  • 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.
  • [x] Check if *tar.xz.asc files are there. If not resort to https://github.com/owncloud/enterprise/wiki/Desktop-Signing-Knowledge
  • [x] Mac: Perform smoke test (Install, make sure it does not explode, and check if all version indicators are correct)
  • [x] Win: Perform smoke test (Install, make sure it does not explode, and check if all version indicators are correct)
  • [x] Linux: Smoke test of one distro package (Install, make sure it does not explode, and check if all version indicators are correct)
  • [ ] Linux: Run https://jenkins.int.owncloud.com/job/client-linux-tests/ with REPO_URL=https://download.opensuse.org/repositories/isv:/ownCloud:/desktop:/testing
  • [ ] Linux: add/remove build targets in isv:ownCloud:Qt5101 and isv:ownCloud:desktop:testing to match the list of supported platforms and announced(!) deprecations. Keep in sync with https://doc.owncloud.org/server/latest/admin_manual/installation/system_requirements.html#desktop
  • [x] 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/download (Attention: No staging!)
  • [x] Inform packagers @dragotin (openSUSE), @hefee (Debian), ??? (Fedora)
  • [x] Announce on https://central.owncloud.org
  • [x] 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

Alpha2

  • [x] Add last updates to Changelog in the client source repository.
  • [x] Branch off a release branch called VERSION-rcX or VERSION-betaX (without v, v is for tags)
  • [x] 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
  • [x] Create build for theme 'ownCloud' using client-trigger (uncheck the "daily build" checkbox, use rcX or betaX dropdown for version suffix)
  • [x] Create build for theme 'testpilotcloud' using client-trigger (uncheck the "daily build" checkbox, use the rcX or betaX dropdown for version suffix)
  • 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.
  • [ ] Check if *tar.xz.asc files are there. If not resort to https://github.com/owncloud/enterprise/wiki/Desktop-Signing-Knowledge
  • [ ] 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 https://jenkins.int.owncloud.com/job/client-linux-tests/ with REPO_URL=https://download.opensuse.org/repositories/isv:/ownCloud:/desktop:/testing
  • [ ] Linux: add/remove build targets in isv:ownCloud:Qt5101 and isv:ownCloud:desktop:testing to match the list of supported platforms and announced(!) deprecations. Keep in sync with https://doc.owncloud.org/server/latest/admin_manual/installation/system_requirements.html#desktop
  • [x] 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/download (Attention: No 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

beta1

  • [x] Add last updates to Changelog in the client source repository.
  • [x] Branch off a release branch called VERSION-rcX or VERSION-betaX (without v, v is for tags)
  • [x] 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
  • [x] Create build for theme 'ownCloud' using client-trigger (uncheck the "daily build" checkbox, use rcX or betaX dropdown for version suffix)
  • [x] Create build for theme 'testpilotcloud' using client-trigger (uncheck the "daily build" checkbox, use the rcX or betaX dropdown for version suffix)
  • 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.
  • [x] Check if *tar.xz.asc files are there. If not resort to https://github.com/owncloud/enterprise/wiki/Desktop-Signing-Knowledge
  • [x] Mac: Perform smoke test (Install, make sure it does not explode, and check if all version indicators are correct)
  • [x] Win: Perform smoke test (Install, make sure it does not explode, and check if all version indicators are correct)
  • [x] Linux: Smoke test of one distro package (Install, make sure it does not explode, and check if all version indicators are correct)
  • [ ] Linux: Run https://jenkins.int.owncloud.com/job/client-linux-tests/ with REPO_URL=https://download.opensuse.org/repositories/isv:/ownCloud:/desktop:/testing
  • [ ] Linux: add/remove build targets in isv:ownCloud:Qt5101 and isv:ownCloud:desktop:testing to match the list of supported platforms and announced(!) deprecations. Keep in sync with https://doc.owncloud.org/server/latest/admin_manual/installation/system_requirements.html#desktop
  • [x] Create a signed tag using git tag -u E94E7B37 tagname (https://github.com/owncloud/enterprise/wiki/Desktop-Signing-Knowledge)
  • [x] update the wordpress content at owncloud.org/download (Attention: No staging!)
  • [x] Inform packagers @dragotin (openSUSE), @hefee (Debian), ??? (Fedora)
  • [x] Announce on https://central.owncloud.org
  • [x] 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

rc1

  • [x] Add last updates to Changelog in the client source repository.
  • [x] Branch off a release branch called VERSION-rcX or VERSION-betaX (without v, v is for tags)
  • [x] 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
  • [x] Create build for theme 'ownCloud' using client-trigger (uncheck the "daily build" checkbox, use rcX or betaX dropdown for version suffix)
  • [x] Create build for theme 'testpilotcloud' using client-trigger (uncheck the "daily build" checkbox, use the rcX or betaX dropdown for version suffix)
  • 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.
  • [x] Check if *tar.xz.asc files are there. If not resort to https://github.com/owncloud/enterprise/wiki/Desktop-Signing-Knowledge
  • [x] Mac: Perform smoke test (Install, make sure it does not explode, and check if all version indicators are correct)
  • [x] 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 https://jenkins.int.owncloud.com/job/client-linux-tests/ with REPO_URL=https://download.opensuse.org/repositories/isv:/ownCloud:/desktop:/testing
  • [ ] Linux: add/remove build targets in isv:ownCloud:Qt5101 and isv:ownCloud:desktop:testing to match the list of supported platforms and announced(!) deprecations. Keep in sync with https://doc.owncloud.org/server/latest/admin_manual/installation/system_requirements.html#desktop
  • [x] 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/download (Attention: No staging!)
  • [x] Inform packagers @dragotin (openSUSE), @hefee (Debian), ??? (Fedora)
  • [x] 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

rc2

  • [x] Add last updates to Changelog in the client source repository.
  • [x] Branch off a release branch called VERSION-rcX or VERSION-betaX (without v, v is for tags)
  • [x] Edit VERSION.cmake to set the suffix to beta1, beta2 etc. Commit the result to the release branch only
  • [x] 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
  • [x] Create build for theme 'ownCloud' using client-trigger (uncheck the "daily build" checkbox, use rcX or betaX dropdown for version suffix)
  • [x] Create build for theme 'testpilotcloud' using client-trigger (uncheck the "daily build" checkbox, use the rcX or betaX dropdown for version suffix)
  • 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.
  • [x] Check if *tar.xz.asc files are there. If not resort to https://github.com/owncloud/enterprise/wiki/Desktop-Signing-Knowledge
  • [x] Mac: Perform smoke test (Install, make sure it does not explode, and check if all version indicators are correct)
  • [x] 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 https://jenkins.int.owncloud.com/job/client-linux-tests/ with REPO_URL=https://download.opensuse.org/repositories/isv:/ownCloud:/desktop:/testing
  • [ ] Linux: add/remove build targets in isv:ownCloud:Qt5101 and isv:ownCloud:desktop:testing to match the list of supported platforms and announced(!) deprecations. Keep in sync with https://doc.owncloud.org/server/latest/admin_manual/installation/system_requirements.html#desktop
  • [x] 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/download (Attention: No staging!)
  • [ ] Inform packagers @dragotin (openSUSE), @hefee (Debian), ??? (Fedora)
  • [x] Announce on https://central.owncloud.org
  • [x] 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

rc3

  • [x] Add last updates to Changelog in the client source repository.
  • [x] Branch off a release branch called VERSION-rcX or VERSION-betaX (without v, v is for tags)
  • [x] 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 "daily build" checkbox, use rcX or betaX dropdown for version suffix)
  • [ ] Create build for theme 'testpilotcloud' using client-trigger (uncheck the "daily build" checkbox, use the rcX or betaX dropdown for version suffix)
  • 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.
  • [ ] Check if *tar.xz.asc files are there. If not resort to https://github.com/owncloud/enterprise/wiki/Desktop-Signing-Knowledge
  • [ ] 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 https://jenkins.int.owncloud.com/job/client-linux-tests/ with REPO_URL=https://download.opensuse.org/repositories/isv:/ownCloud:/desktop:/testing
  • [ ] Linux: add/remove build targets in isv:ownCloud:Qt5101 and isv:ownCloud:desktop:testing to match the list of supported platforms and announced(!) deprecations. Keep in sync with https://doc.owncloud.org/server/latest/admin_manual/installation/system_requirements.html#desktop
  • [ ] 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/download (Attention: No 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

For rc4:

  • [x] Add last updates to Changelog in the client source repository.
  • [x] Branch off a release branch called VERSION-rcX or VERSION-betaX (without v, v is for tags)
  • [x] 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
  • [x] Create build for theme 'ownCloud' using client-trigger (uncheck the "daily build" checkbox, use rcX or betaX dropdown for version suffix)
  • [x] Create build for theme 'testpilotcloud' using client-trigger (uncheck the "daily build" checkbox, use the rcX or betaX dropdown for version suffix)
  • 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.
  • [x] Check if *tar.xz.asc files are there. If not resort to https://github.com/owncloud/enterprise/wiki/Desktop-Signing-Knowledge
  • [x] Mac: Perform smoke test (Install, make sure it does not explode, and check if all version indicators are correct)
  • [x] Win: Perform smoke test (Install, make sure it does not explode, and check if all version indicators are correct)
  • [x] Linux: Smoke test of one distro package (Install, make sure it does not explode, and check if all version indicators are correct)
  • [ ] Linux: Run https://jenkins.int.owncloud.com/job/client-linux-tests/ with REPO_URL=https://download.opensuse.org/repositories/isv:/ownCloud:/desktop:/testing
  • [ ] Linux: add/remove build targets in isv:ownCloud:Qt5101 and isv:ownCloud:desktop:testing to match the list of supported platforms and announced(!) deprecations. Keep in sync with https://doc.owncloud.org/server/latest/admin_manual/installation/system_requirements.html#desktop
  • [x] 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/download (Attention: No staging!)
  • [x] Inform packagers @dragotin (openSUSE), @hefee (Debian), ??? (Fedora)
  • [x] Announce on https://central.owncloud.org
  • [x] 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

For rc:

  • [ ] 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 "daily build" checkbox, use rcX or betaX dropdown for version suffix)
  • [ ] Create build for theme 'testpilotcloud' using client-trigger (uncheck the "daily build" checkbox, use the rcX or betaX dropdown for version suffix)
  • 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.
  • [ ] Check if *tar.xz.asc files are there. If not resort to https://github.com/owncloud/enterprise/wiki/Desktop-Signing-Knowledge
  • [ ] 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 https://jenkins.int.owncloud.com/job/client-linux-tests/ with REPO_URL=https://download.opensuse.org/repositories/isv:/ownCloud:/desktop:/testing
  • [ ] Linux: add/remove build targets in isv:ownCloud:Qt5101 and isv:ownCloud:desktop:testing to match the list of supported platforms and announced(!) deprecations. Keep in sync with https://doc.owncloud.org/server/latest/admin_manual/installation/system_requirements.html#desktop
  • [ ] 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/download (Attention: No 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:

  • [x] Communicate the release schedule on mailinglist [email protected]. Give a high level overview of the upcoming new features, changes etc.
  • [x] Ensure marketing is aware ([email protected]) and prepared for the release (social, .com website, cust.communications)
  • [x] 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? (20181109jw: where? how?)
  • [ ] Run the tx.pl scripts on the final code tag (20181109jw: really? What does that test?)
  • [x] Run make test
  • [x] 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):

  • [x] Add last updates to Changelog in the client source repository.
  • [x] Branch off a release branch called VERSION (without v, v is for tags)
  • [x] Edit VERSION.cmake to set the suffix to "" etc. Commit the result to the release branch only
  • [x] Create build for theme 'ownCloud' using client-trigger (uncheck the "daily build" checkbox, use the proper dropdown for version suffix)
  • [x] Create build for theme 'testpilotcloud' using client-trigger (uncheck the "daily build" checkbox, use the proper dropdown for version suffix)
  • 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.
  • [x] Check if *tar.xz.asc files are there. If not resort to https://github.com/owncloud/enterprise/wiki/Desktop-Signing-Knowledge
  • [x] Branch isv:ownCloud:desktop to isv:ownCloud:desktop:client-X.Y.Z using https://github.com/owncloud/administration/blob/master/jenkins/obs_integration/ (the Linux packages will always land in the :testing repository)
    obs-deepcopy-prj.sh isv:ownCloud:desktop isv:ownCloud:desktop:client-2.5.1
  • [x] Re-download Mac builds and check signature. Interactive in installer window
  • [x] Re-download Win build check signature. From Mac or Linux: osslsigncode verify ownCloud-version-setup.exe
  • [x] Mac: Perform smoke test (Install, make sure it does not explode, and check if all version indicators are correct)
  • [x] Win: Perform smoke test (Install, make sure it does not explode, and check if all version indicators are correct)
  • [x] Linux: Smoke test of one distro package (Install, make sure it does not explode, and check if all version indicators are correct)
  • [x] Linux: Run https://jenkins.int.owncloud.com/job/client-linux-tests/ with REPO_URL=https://download.opensuse.org/repositories/isv:/ownCloud:/desktop:/testing
  • [x] Win/Mac Copy builds from testing to stable on download.owncloud.com, double check the download links. (make sure the .asc is there too)
  • [x] Linux: disable publishing on project isv:ownCloud:desktop
  • [x] Linux: copy from testing to released in OBS:
    obs-deepcopy-prj.sh isv:ownCloud:desktop:testing isv:ownCloud:desktop
    obs-deepcopy-prj.sh isv:ownCloud:testpilot:testing isv:ownCloud:testpilot
  • [x] Linux: Re-enable OBS publishing on the project after official release date and if all distros build (check for accidentially disabled packages too)
  • [x] Linux: Wait until everything is built and published, then disable publishing on project isv:ownCloud:desktop
  • [x] Create git signed tag in client repository using git tag -u E94E7B37 tagname (https://github.com/owncloud/enterprise/wiki/Desktop-Signing-Knowledge)
  • [x] Create same tag for MSI code
  • [x] Create same tag for Windows toolchain
  • [x] Create same tag (actually a symlink) for macOS toolchain
  • [x] Create a (draft) release on https://github.com/owncloud/client/releases
  • [x] Update https://github.com/owncloud/client/blob/master/ChangeLog
  • [ ] 1h later check https://owncloud.org/changelog/desktop-client/ -> it pulls from the master ChangeLog file hourly.
  • [x] 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.
  • [x] Update https://owncloud.com/download/#desktop-clients (both de & en, achim via #marketing)
  • [x] Announce on https://central.owncloud.org
  • [x] Announce on [email protected] Link to the central post so discussion happens there.
  • [x] Inform packagers @dragotin (openSUSE) @hefee (Debian) @Germano0 (Fedora)
  • [ ] Send out Social (tweet, blog, other)
  • [ ] Send out customer communication (if any)
  • [x] Inform GCX that the new version is released ([email protected])
  • [x] Inform [email protected]
  • [x] Ensure marketing is aware ([email protected])
  • [x] 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:

  • [x] Test all advertised download links to have the expected version
  • [x] Check for build errors in OBS, do
    obs-deepcopy-prj.sh isv:ownCloud:desktop isv:ownCloud:desktop:client-2.X.X
  • [x] disable publishing in OBS to prevent that accidential rebuilds hit the end users.
  • [x] add the previous release to https://owncloud.org/download/older-versions/

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 owncloud hosted updater according to https://github.com/owncloud/enterprise/blob/master/client_update_checker/README.md#deploy
  • [ ] Increment version number in daily 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.
Plan

Most helpful comment

Rewritten file discovery code. @ogoffart do we have benchmarks for this? Or will this only come with the parallelization?

The discovery uses a new algorithm.

Before it used the csync model: It first was discovering everything on the server. Sequentially recursing in every directory (altough there was an optimisation in which we would "read from database" for directories that were not modified at all) and build a in-memory data structure of the server side state. Then it would do the same for the local file system state. Then it would merge the two state and start the propagation.

Now, the discovery is different. Both the remote and local directory are done at the same time, and the reconciliation phase too. Also, the discovery jobs for different directory are run in parallel. There is no longer this in-memory datascructure of the whole server and client state.

This means:

  • The remote discovery (especially the initial one) is much faster, as calls are done in parallel. So it should be several times faster (up to 6 parallel jobs I think)
  • We know much earlier what to do, and this will enable us, in a future release, to start the propagation job immediately, in parallel. (but this was not implemented yet. one thing at the time)
  • The implementation is somewhat more flexible which should allow to change or implement new feature more easily in the future.

All 58 comments

2.6 branched off, dailies and transifex will be switched by @dschmidt

@jnweiger tested the wincfapi stuff and created a bunch of issues, not all are urgent since the feature is still experimental.

transifex syncing is currently broken because public jenkins was shut down. I've sent a replacement PR to translation-sync repo (https://github.com/owncloud/translation-sync/pull/17/files) but it's currently held back by https://github.com/owncloud/core/pull/34999. I've updated the PR to 2.6.

I added 2.6 dailies, currently testing if they build succesfully.

Delta Sync:
This is so far server side only in master branch unreleased..
@PVince81 is attemping to get this into 10.3 at https://github.com/owncloud/core/pull/35011
So if people want to test this, they need to be aware of that (CC @haukman )

FYI @mrow4a

@lefherz @JKawohl https://github.com/owncloud/client/blob/master/ChangeLog

Main features from user point are

  • Vfs: Introduce experimental native virtual files mode for Windows 10. maybe this could need a video for demo. Also a lot of general VFS improvements.
  • Rewritten file discovery code. @ogoffart do we have benchmarks for this? Or will this only come with the parallelization?
  • Remove support for Shibboleth auth People should use OAuth2
  • delta sync (https://owncloud.org/news/welcome-delta-sync-for-owncloud/) although this was already announced last year :(
  • As usual, ton of fixes and under the hood improvements

alpha1 is about to be released.
@jnweiger Can you double-check https://github.com/owncloud/client/releases/edit/untagged-b974afee32b9d26fdc05 ?
@jnweiger I think you also need to re-enable something in OBS and see what I wrote about the client linux tests

FYI @dragotin (openSUSE), @hefee (Debian)

Auto updater for unstable channel: https://github.com/owncloud/enterprise/pull/3294
@michaelstingl @jnweiger ideally we get this deployed before easter so people can try

Rewritten file discovery code. @ogoffart do we have benchmarks for this? Or will this only come with the parallelization?

The discovery uses a new algorithm.

Before it used the csync model: It first was discovering everything on the server. Sequentially recursing in every directory (altough there was an optimisation in which we would "read from database" for directories that were not modified at all) and build a in-memory data structure of the server side state. Then it would do the same for the local file system state. Then it would merge the two state and start the propagation.

Now, the discovery is different. Both the remote and local directory are done at the same time, and the reconciliation phase too. Also, the discovery jobs for different directory are run in parallel. There is no longer this in-memory datascructure of the whole server and client state.

This means:

  • The remote discovery (especially the initial one) is much faster, as calls are done in parallel. So it should be several times faster (up to 6 parallel jobs I think)
  • We know much earlier what to do, and this will enable us, in a future release, to start the propagation job immediately, in parallel. (but this was not implemented yet. one thing at the time)
  • The implementation is somewhat more flexible which should allow to change or implement new feature more easily in the future.

beta1 build triggered (ownCloud branding) https://jenkins.int.owncloud.com/job/client-trigger/3156/

Linux: Beta1 builds with Qt-5.12.4 -- (alpha2 was with Qt-5.12.2)

Suggested platform update: https://github.com/owncloud/docs/pull/1603

macOS is at 5.12.4 too now
https://download.owncloud.com/desktop/testing/ownCloud-2.6.0.12261beta1.pkg
Thanks @dschmidt @TheOneRing

Linux: Run https://jenkins.int.owncloud.com/job/client-linux-tests/ with REPO_URL=https://download.opensuse.org/repositories/isv:/ownCloud:/desktop:/testing

@jnweiger @dschmidt that one is throwing

ssh: Could not resolve hostname gitea.int.owncloud.com: Name or service not known

@dragotin @hefee FYI, here's the source of 2.6.0 beta1:
https://download.owncloud.com/desktop/testing/owncloudclient-2.6.0.12458-beta1.tar.xz

Beta channel auto updater: https://github.com/owncloud/enterprise/pull/3472
Please help me review / deploy this

Test builds for vanilla openSUSE without extra libs in home:kfreitag repo: https://build.opensuse.org/package/show/home%3Akfreitag/owncloud-client . Will go into KDE:Extra and Factory once released. @PVince81

@guruz: no central announcement of the RC?

@guruz: no central announcement of the RC?

I've edited the beta announcement: https://central.owncloud.org/t/desktop-sync-vfs-client-2-6-0-rc1-released/21284/2?u=guruz

Potential release blocker is https://github.com/owncloud/client/issues/7456
We're investigating...

rc2 is published.
https://github.com/owncloud/client/releases/tag/v2.6.0-rc2

Let's do some testing ourselves, then we can enable auto updater (beta channel)

CAN I PLEASE BE REMOVED FROM THE TEMPLATE? THANK YOU

@Germano0 Sorry, you are not in the template already. https://github.com/owncloud/client/blob/master/.github/release_template.md
I guess you need to click "Unsubscribe" here on the issue (right sidebar)

@guruz
* [ ] Inform packagers @dragotin (openSUSE) @hefee (Debian) @Germano0 (Fedora)

Regression test results 2.6.0 rc2, server 10.3.0 stable
Regression test desktop client 2.6.0 rc2.pdf

2.6.0-rc3 branched off
thanks a lot @HanaGemela

2.6.0-rc4 branched off, builds triggered..

ownCloud-2.6.0.12984.12659-rc4.msi
ownCloud-2.6.0.12984.12659-rc4.GPO.msi
ownCloud-qt5.10.1-2.6.0.12665rc4.pkg
ownCloud-qt5.12.5-2.6.0.12665rc4.pkg
owncloudclient-2.6.0.12984-rc4.tar.xz

fixed the pattern for the osx filenames: the final build will have

ownCloud-2.6.0.xxxxx.pkg and
ownCloud-osx10.11-2.6.0.xxxxx.pkg

ownCloud-osx10.11-2.6.0.xxxxx.pkg

@jnweiger Normally the min-OS-version is used for legacy downloads (10.10 in our case?). Here you can find an example:
https://www.omnigroup.com/download

smoke tested 2.6.0 on osx, win10, ubuntu18.04, debian8. All good, except for
https://github.com/owncloud/client/issues/7579

@michaelstingl Your comment above ist not clear to me. I only fixed a regression to re-adopt the naming that we had before. Do you suggest more changes?

copy to stable download done like this:
```
281 ~/bin/mc cp download_mirrors/dotcom/desktop/testing/testpilotcloud-2.6.0.13020.12691.msi download_mirrors/dotcom/desktop/stable/testpilotcloud-2.6.0.13020.12691.msi
282 ~/bin/mc cp download_mirrors/dotcom/desktop/testing/testpilotcloud-2.6.0.13020.12691.GPO.msi download_mirrors/dotcom/desktop/stable/testpilotcloud-2.6.0.13020.12691.GPO.msi
287 ~/bin/mc cp download_mirrors/dotcom/desktop/testing/ownCloud-2.6.0.13018.12690.msi download_mirrors/dotcom/desktop/stable/
288 ~/bin/mc cp download_mirrors/dotcom/desktop/testing/ownCloud-2.6.0.13018.12690.GPO.msi download_mirrors/dotcom/desktop/stable/
289 ~/bin/mc cp download_mirrors/dotcom/desktop/testing/testpilotcloud-client-2.6.0.1716.linux-repo.html download_mirrors/dotcom/desktop/stable/
290 ~/bin/mc cp download_mirrors/dotcom/desktop/testing/testpilotcloud-2.6.0.12705.pkg.sig download_mirrors/dotcom/desktop/stable/
291 ~/bin/mc cp download_mirrors/dotcom/desktop/testing/testpilotcloud-2.6.0.12705.pkg.tbz.sig download_mirrors/dotcom/desktop/stable/
292 ~/bin/mc cp download_mirrors/dotcom/desktop/testing/testpilotcloud-osx10.11-2.6.0.12705.pkg.sig download_mirrors/dotcom/desktop/stable/
293 ~/bin/mc cp download_mirrors/dotcom/desktop/testing/testpilotcloud-osx10.11-2.6.0.12705.pkg.tbz.sig download_mirrors/dotcom/desktop/stable/
294 ~/bin/mc cp download_mirrors/dotcom/desktop/testing/testpilotcloud-2.6.0.12705.pkg download_mirrors/dotcom/desktop/stable/
295 ~/bin/mc cp download_mirrors/dotcom/desktop/testing/testpilotcloud-2.6.0.12705.pkg.tbz download_mirrors/dotcom/desktop/stable/
296 ~/bin/mc cp download_mirrors/dotcom/desktop/testing/testpilotcloud-2.6.0.12705.pkg.tbz download_mirrors/dotcom/desktop/stable/
297 ~/bin/mc cp download_mirrors/dotcom/desktop/testing/testpilotcloud-osx10.11-2.6.0.12705.pkg.tbz download_mirrors/dotcom/desktop/stable/
298 ~/bin/mc cp download_mirrors/dotcom/desktop/testing/testpilotcloud-osx10.11-2.6.0.12705.pkg download_mirrors/dotcom/desktop/stable/
302 ~/bin/mc cp download_mirrors/dotcom/desktop/testing/testpilotcloudclient-2.6.0.13020.tar.xz.asc download_mirrors/dotcom/desktop/stable/
303 ~/bin/mc cp download_mirrors/dotcom/desktop/testing/ownCloud-2.6.0.13018.12690.GPO.msi download_mirrors/dotcom/desktop/stable/
304 ~/bin/mc cp download_mirrors/dotcom/desktop/testing/ownCloud-2.6.0.13018.12690.msi download_mirrors/dotcom/desktop/stable/
305 ~/bin/mc cp download_mirrors/dotcom/desktop/testing/owncloudclient-2.6.0.13018.tar.xz download_mirrors/dotcom/desktop/stable/
306 ~/bin/mc cp download_mirrors/dotcom/desktop/testing/ownCloud-osx10.11-2.6.0.12703.pkg.tbz download_mirrors/dotcom/desktop/stable/
307 ~/bin/mc cp download_mirrors/dotcom/desktop/testing/owncloudclient-2.6.0.13018.tar.xz.asc download_mirrors/dotcom/desktop/stable/
308 ~/bin/mc cp download_mirrors/dotcom/desktop/testing/owncloud-client-2.6.0.1714.linux-repo.html download_mirrors/dotcom/desktop/stable/
309 ~/bin/mc cp download_mirrors/dotcom/desktop/testing/ownCloud-osx10.11-2.6.0.12703.pkg download_mirrors/dotcom/desktop/stable/
310 ~/bin/mc cp download_mirrors/dotcom/desktop/testing/ownCloud-osx10.11-2.6.0.12703.pkg.tbz.sig download_mirrors/dotcom/desktop/stable/
311 ~/bin/mc cp download_mirrors/dotcom/desktop/testing/ownCloud-2.6.0.12703.pkg.tbz download_mirrors/dotcom/desktop/stable/
312 ~/bin/mc cp download_mirrors/dotcom/desktop/testing/ownCloud-osx10.11-2.6.0.12703.pkg.sig download_mirrors/dotcom/desktop/stable/
313 ~/bin/mc cp download_mirrors/dotcom/desktop/testing/ownCloud-2.6.0.12703.pkg download_mirrors/dotcom/desktop/stable/
314 ~/bin/mc cp download_mirrors/dotcom/desktop/testing/ownCloud-2.6.0.12703.pkg.tbz.sig download_mirrors/dotcom/desktop/stable/
315 ~/bin/mc cp download_mirrors/dotcom/desktop/testing/ownCloud-2.6.0.12703.pkg.sig download_mirrors/dotcom/desktop/stable/

It seems you have 2.6.0 released. Are the sources available in the public as well? :anger:

Yes, in the usual places:
https://download.owncloud.com/desktop/testing/owncloudclient-2.6.0.13018.tar.xz
Directory lising is enabled there, and the copy command above also has it.
And also in openSUSE OBS in the usual place. What was the reason for :anger: ?

Online updater and websites and announcements: TBD Monday.

@dragotin Not released yet, only after the github release is out.

Github release draft: https://github.com/owncloud/client/releases/edit/untagged-e0222ae49ebb3fa4751e

@jnweiger OBS seems quite borked https://build.opensuse.org/project/monitor/isv:ownCloud:desktop

OBS built everything except for old CentOS6 and 7. CentOS8 is there. Most error messages there are related to unused 5.12.1 dependencies. I am fixing CentOS6 and 7 and removing unused cruft.

OBS publishing done.

OBS rebuilds disabled

Linux install test results look like this:
```

|repourl| http://download.opensuse.org/repositories/isv:/ownCloud:/desktop
|package| owncloud-client
|Ubuntu_18.04| Listing...
|Ubuntu_18.04| owncloud-client/unknown,now 2.6.0+oc-1714 amd64 [installed]
|Ubuntu_18.04| owncloud-client-caja/unknown,now 2.6.0+oc-1714 all [installed]
|Ubuntu_18.04| owncloud-client-dolphin/unknown,now 2.6.0+oc-1714 all [installed]
|Ubuntu_18.04| owncloud-client-nautilus/unknown,now 2.6.0+oc-1714 all [installed]
|Ubuntu_18.04| owncloud-client-nemo/unknown,now 2.6.0+oc-1714 all [installed]
|Ubuntu_18.10| Listing...
|Ubuntu_18.10| owncloud-client-caja/unknown,now 2.6.0+oc-1714 all [installed]
|Ubuntu_18.10| owncloud-client-dolphin/unknown,now 2.6.0+oc-1714 all [installed]
|Ubuntu_18.10| owncloud-client-nautilus/unknown,now 2.6.0+oc-1714 all [installed]
|Ubuntu_18.10| owncloud-client-nemo/unknown,now 2.6.0+oc-1714 all [installed]
|Ubuntu_18.10| owncloud-client/unknown,now 2.6.0+oc-1714 amd64 [installed]
|Ubuntu_19.04| Listing...
|Ubuntu_19.04| owncloud-client-caja/unknown,now 2.6.0+oc-1714 all [installed]
|Ubuntu_19.04| owncloud-client-dolphin/unknown,now 2.6.0+oc-1714 all [installed]
|Ubuntu_19.04| owncloud-client-nautilus/unknown,now 2.6.0+oc-1714 all [installed]
|Ubuntu_19.04| owncloud-client-nemo/unknown,now 2.6.0+oc-1714 all [installed]
|Ubuntu_19.04| owncloud-client/unknown,now 2.6.0+oc-1714 amd64 [installed]
|Debian_8.0| Listing...
|Debian_8.0| owncloud-client/unknown,now 2.6.0+oc-1714 amd64 [installed]
|Debian_8.0| owncloud-client-caja/unknown,now 2.6.0+oc-1714 all [installed]
|Debian_8.0| owncloud-client-nautilus/unknown,now 2.6.0+oc-1714 all [installed]
|Debian_9.0| Listing...
|Debian_9.0| owncloud-client/unknown,now 2.6.0+oc-1714 amd64 [installed]
|Debian_9.0| owncloud-client-dolphin/unknown,now 2.6.0+oc-1714 all [installed]
|Debian_9.0| owncloud-client-nautilus/unknown,now 2.6.0+oc-1714 all [installed]
|Debian_9.0| owncloud-client-nemo/unknown,now 2.6.0+oc-1714 all [installed]
|Debian_10| Listing...
|Debian_10| owncloud-client-caja/unknown,now 2.6.0+oc-1714 all [installed]
|Debian_10| owncloud-client-dolphin/unknown,now 2.6.0+oc-1714 all [installed]
|Debian_10| owncloud-client-nautilus/unknown,now 2.6.0+oc-1714 all [installed]
|Debian_10| owncloud-client-nemo/unknown,now 2.6.0+oc-1714 all [installed]
|Debian_10| owncloud-client/unknown,now 2.6.0+oc-1714 amd64 [installed]
|Fedora_27| owncloud-client-2.6.0-1714.3.x86_64
|Fedora_27| owncloud-client-dolphin-2.6.0-1714.3.x86_64
|Fedora_27| owncloud-client-nautilus-2.6.0-1714.3.x86_64
|Fedora_27| owncloud-client-nemo-2.6.0-1714.3.x86_64
|Fedora_27| package owncloud-client-caja is not installed
|Fedora_28| owncloud-client-2.6.0-1714.3.x86_64
|Fedora_28| owncloud-client-dolphin-2.6.0-1714.3.x86_64
|Fedora_28| owncloud-client-nautilus-2.6.0-1714.3.x86_64
|Fedora_28| owncloud-client-nemo-2.4.0-2.fc28.x86_64
|Fedora_28| package owncloud-client-caja is not installed
|Fedora_29| owncloud-client-2.6.0-1714.3.x86_64
|Fedora_29| owncloud-client-dolphin-2.6.0-1714.3.x86_64
|Fedora_29| owncloud-client-nautilus-2.6.0-1714.3.x86_64
|Fedora_29| owncloud-client-nemo-2.6.0-1714.3.x86_64
|Fedora_29| package owncloud-client-caja is not installed
|Fedora_30| owncloud-client-2.6.0-1714.2.x86_64
|Fedora_30| owncloud-client-dolphin-2.6.0-1714.2.x86_64
|Fedora_30| owncloud-client-nautilus-2.6.0-1714.2.x86_64
|Fedora_30| owncloud-client-nemo-2.5.4-1.fc30.x86_64
|Fedora_30| package owncloud-client-caja is not installed
|Fedora_31| owncloud-client-2.6.0-1714.2.x86_64
|Fedora_31| owncloud-client-dolphin-2.6.0-1714.2.x86_64
|Fedora_31| owncloud-client-nautilus-2.6.0-1714.2.x86_64
|Fedora_31| owncloud-client-nemo-2.5.4-2.fc31.x86_64
|Fedora_31| owncloud-client-nemo-2.5.4-2.fc31.x86_64
|Fedora_31| package owncloud-client-caja is not installed
|CentOS_6| owncloud-client-2.6.0-1714.1.x86_64
|CentOS_6| package owncloud-client-dolphin is not installed
|CentOS_6| owncloud-client-nautilus-2.6.0-1714.1.x86_64
|CentOS_6| package owncloud-client-nemo is not installed
|CentOS_6| package owncloud-client-caja is not installed
|CentOS_7| owncloud-client-2.6.0-1714.1.x86_64
|CentOS_7| package owncloud-client-dolphin is not installed
|CentOS_7| owncloud-client-nautilus-2.6.0-1714.1.x86_64
|CentOS_7| owncloud-client-nemo-2.6.0-1714.1.x86_64
|CentOS_7| package owncloud-client-caja is not installed
|CentOS_8| owncloud-client-2.6.0-1714.2.x86_64
|CentOS_8| package owncloud-client-dolphin is not installed
|CentOS_8| package owncloud-client-nautilus is not installed
|CentOS_8| package owncloud-client-nemo is not installed
|CentOS_8| package owncloud-client-caja is not installed
|openSUSE_Leap_42.3| owncloud-client-2.6.0-1714.1.x86_64
|openSUSE_Leap_42.3| owncloud-client-dolphin-2.6.0-1714.1.x86_64
|openSUSE_Leap_42.3| owncloud-client-nautilus-2.6.0-1714.1.x86_64
|openSUSE_Leap_42.3| owncloud-client-nemo-2.6.0-1714.1.x86_64
|openSUSE_Leap_42.3| owncloud-client-caja-2.6.0-1714.1.x86_64
|openSUSE_Leap_15.1| owncloud-client-2.6.0-lp151.1714.2.x86_64
|openSUSE_Leap_15.1| owncloud-client-dolphin-2.6.0-lp151.1714.2.x86_64
|openSUSE_Leap_15.1| owncloud-client-nautilus-2.6.0-lp151.1714.2.x86_64
|openSUSE_Leap_15.1| owncloud-client-nemo-2.6.0-lp151.1714.2.x86_64
|openSUSE_Leap_15.1| owncloud-client-caja-2.6.0-lp151.1714.2.x86_64
|openSUSE_Leap_15.2| owncloud-client-2.6.0-lp152.1714.2.x86_64
|openSUSE_Leap_15.2| owncloud-client-dolphin-2.6.0-lp152.1714.2.x86_64
|openSUSE_Leap_15.2| owncloud-client-nautilus-2.6.0-lp152.1714.2.x86_64
|openSUSE_Leap_15.2| owncloud-client-nemo-2.6.0-lp152.1714.2.x86_64
|openSUSE_Leap_15.2| owncloud-client-caja-2.6.0-lp152.1714.2.x86_64

Was this page helpful?
0 / 5 - 0 ratings