Client 2.3.3 release

[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
• 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/mirall/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

One week before the release:

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

For all Betas and RCs:

• 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
• Create build for Windows using rotor job owncloud-client-win32 (uncheck the "nightly build" checkbox, check the "sign package" checkboxes) both themes 'ownCloud' and 'testpilotcould'
• Create build for Mac using rotor, job owncloud-client-osx (uncheck the "nightly build" checkbox, check the "sign package" checkboxes) both themes 'ownCloud' and 'testpilotcould'
• Create the beta tarball using Jenkins job ownCloud-client-source
• Create Linux builds using rotor job owncloud-client-linux building (this magically interacts with the ownCloud-client-source job)
  • theme 'ownCloud' -> isv:ownCloud:community:testing
  • theme 'testpilotcould' -> isv:ownCloud:testpilot:testing
• Copy builds from daily to testing on download.owncloud.com, double check the download links.
• Create a pull request to the owncloud.org repository to update the install page (strings.php, page-desktop.php). From now on download packages from the staging webserver.
• Inform community mailinglists devel@owncloud.org and testpilots@owncloud.org
• Announce on https://central.owncloud.org
• Create a signed tag using git tag -u E94E7B37 tagname (https://github.com/owncloud/enterprise/wiki/Desktop-Signing-Knowledge)
• Check crash reporter

For first Beta of a Major or Minor release:

• branch off master to new version branch (e.g. master -> 2.1, when releasing 2.1)
• Adjust VERSION.cmake in master and count up (e.g. 2.2)
• Adjust translation jobs for client and NSIS 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.

Day before Release:

• Check the translations coming from transifex: All synchronized?
• Run the tx.pl scripts on the final code tag
• Run make test
• Run smashbox on the final code tag
• Inform product management and marketing that we are 1 day out

On Release Day (for final release):

• Branch off a release branch called like the version (without v, v is for tags)
• Double check VERSION.cmake: Check the version number settings and suffix (beta etc.) to be removed. Commit change to 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
• Add last updates to Changelog in the client source repository.
• Stop publishing on OBS https://build.opensuse.org/project/show/isv:ownCloud:testpilot https://build.opensuse.org/project/show/isv:ownCloud:desktop
• 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
• Check download mirrors for sufficient free disk space (jw,tsgebert)
• Run https://jenkins.int.owncloud.com/view/client/job/official-client-trigger with (uncheck the "nightly build" checkbox, check the "sign package" checkboxes) both themes 'ownCloud' and 'testpilotcould' this does all of the following (except for signing the sources):
  • Create tar ball (https://jenkins.int.owncloud.com/view/client/job/official-client-source/) and immediately sign it (asc file). (https://github.com/owncloud/enterprise/wiki/Desktop-Signing-Knowledge)
  • Create build for Windows using jenkins.int job official-client-win32 (uncheck the "nightly build" checkbox, check the "sign package" checkboxes) both themes 'ownCloud' and 'testpilotcould'
  • Create build for Mac using jenkins.int, job official-client-osx (uncheck the "nightly build" checkbox, check the "sign package" checkboxes) both themes 'ownCloud' and 'testpilotcould'
  • Create Linux builds using rotor job owncloud-client-linux (this magically interacts with the ownCloud-client-source job)
    • Check if patches still apply in the linux packages
  • Update OBS repository isv:ownCloud:desktop
    • theme 'ownCloud' -> isv:ownCloud:desktop
    • theme 'testpilotcloud' -> isv:ownCloud:testpilot
  • Linux: Update the testing repository to the latest stable version.
• check remaining free disk space on the mirrors.
• immediately sign the sources (asc file). (https://github.com/owncloud/enterprise/wiki/Desktop-Signing-Knowledge)
• Linux: Create submitrequests in obs
  See https://github.com/owncloud/enterprise/wiki/Client-release-with-jenkins#final-release
• Inform GCX that a new tarball is available. Inform QA...
• Copy builds and source tar ball from testing to stable on download.owncloud.com, double check the download links.
• Check if the following packages are on download.owncloud.com/desktop/stable:
  • Windows binary package
  • Mac binary package
  • source tarballs
• Create a pull request to the owncloud.org repository to update the install page (strings.php, page-desktop.php) for variables and changelog. From now on download packages from the staging webserver.
• 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
• Linux: Re-enable OBS publishing
• Announce on https://central.owncloud.org
• Announce on announcements@owncloud.org
• Create git signed tag in client repository using git tag -u E94E7B37 tagname
• Send out Social (tweet, blog, other)
• Send out customer communication (if any)
• Inform GCX that the new version is released (gcx@owncloud.com)
• Inform release-coordination@owncloud.com
• Ensure marketing is aware (marketing@owncloud.com)
• Take pride and celebrate!
• Also update the testpilotcloud builds for that release version and make sure they show up on the download page
• 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

A few days after the release

• Update the updater script clientupdater.php (check the crash reporter if auto update is a good idea or we need a new release) https://github.com/owncloud/enterprise/pull/2246
• 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.
  Update VERSION.cmake #6001

[guruz]

FYI @michaelstingl @jnweiger @SamuAlfageme

[guruz]

Changelog is up: https://github.com/owncloud/client/blob/2.3/ChangeLog

[SamuAlfageme]

@guruz updated w/ some more refs. Can't find the issues/PRs for:

• https://github.com/owncloud/client/blob/2.3/ChangeLog#L10
• https://github.com/owncloud/client/blob/2.3/ChangeLog#L12

Could you ref. them?

[guruz]

Blocked by the APFS gold ticket (research) and on https://github.com/owncloud/enterprise/issues/2151

[SamuAlfageme]

🚧 Blockers

• [macOS] Check file system unicode normalization is correct [OS X] [APFS] Make sure our file system unicode normalization will be correct #5650 ~~~> macOS 10.13
• "Open in browser" / "Open folder" doesn't work on some KDE distros: https://github.com/owncloud/enterprise/issues/2151
• Multiple Linux Platforms fail to compile with 2.3.3 - Multiple Linux Platforms fail to compile with master branch #5915
  • affected: CentOS_7, Debian_7, Fedora_24, openSUSE_13.1

🆕 QA over new (patch-version specific) Testing Scenarios 2.3.3

• Chunking NG: Don't use old chunking on new DAV endpoint (Client uses old chunking protocol with new DAV endpoint "Precondition failed" "An If-Match header was specified and the resource did not exist" #5855)
• Selective Sync: Skip excluded folders when reading DB, don't let them show errors (Selective sync: Skip excluded folders when reading db #5772)
• Settings: Make window bigger so Qt version is always visible ([Linux] Display build number and runtime dependencies on "About" section #5760)
• Share links: Show warning that public link shares are public (Sharing: Show warning that link shares are public #5785 #5747 #5786)
• Notifications: Make close/dismiss button in the Activity tab match server's logic ([Notifications] Make close/dismiss button in the Activity tab match server's logic #5922)
• (❓) Downloads: Re-trigger folder discovery on HTTP 404 (Download: Retrigger folder discovery on 404 #5799)
• SyncJournalDB: Don't use ._ as filename pattern if that does not work because of SMB storage settings (Journal: Don't use a ._ path if it won't work #5633 #5844)
• SyncJournalDB: Log reason for sqlite3 opening errors
• Switch Linux build also to Qt 5.6.2 (Qt-5.6.2 everywhere #5470)

---

💥 Regression test on the whole client

Target: Kubuntu 17.04, Windows 10, macOS Sierra 10.12.5

• Installer/Uninstaller
• Setup
• Syncing
  • User stop syncing
  • Test resuming of uploads
  • Test resuming download
  • Modifying files when the sync is running ~> see Note below
  • Test shared folder
• Network-related
• Crash Recovery
• Server interaction checks
• Upgrade (where applicable)
  • Upgrade from Previous Client Version
  • Upgrade from previous server version
• Credential Management
  • First startup
  • Update
  • Password change, without URL change.
  • Password change, with URL change
  • Wrong password
  • Shibboleth
• Multiple folders
• Activity log (Including 2.3's Open folder from activity tab #5306)
• Quota
• Windows Office Files
• Big File modified during Upsync
• Command Line Client

---

📃 Notes:

• Resuming a paused sync that was uploading a bunch of files and were moved in the client is duplicating one file in both locations - Resuming a paused sync that was uploading a bunch of files and were moved in the client is duplicating one file in both locations #5949

[SamuAlfageme]

@guruz @michaelstingl all release blockers cleared out; I'm starting with the regression scenarios.

[guruz]

We have some builds in https://download.owncloud.com/desktop/testing/ and https://software.opensuse.org//download.html?project=isv%3AownCloud%3Acommunity%3Atesting&package=owncloud-client

We will publish them after testing

[guruz]

PR for website: owncloud-archive/owncloud.org#1250

[guruz]

Posting for central and mailing list: https://gist.github.com/guruz/29cb937de7d5fdeb360da75c7ae20b94

[SamuAlfageme]

@guruz other than #5949 I found no issues on the regression tests. We can announce the RC1 now 👍

[guruz]

Waiting for deployment of owncloud-archive/owncloud.org#1250 then announcing

[guruz]

https://central.owncloud.org/t/desktop-sync-client-2-3-3-rc1-release-candidate-released/8967

[guruz]

Linking https://github.com/owncloud/enterprise/issues/2151

[guruz]

Starting build of rc2 with latest changes of @jnweiger in OBS

[guruz]

rc2 @ https://download.owncloud.com/desktop/testing/ https://software.opensuse.org//download.html?project=isv%3AownCloud%3Acommunity%3Atesting&package=owncloud-client

[guruz]

rc2 PR @ owncloud-archive/owncloud.org#1256

[jnweiger]

Triggered 2.3.3 final builds for ownCloud-client and testpilotcloud-client:

• https://jenkins.int.owncloud.com/view/client/job/official-client-trigger/244/
• https://jenkins.int.owncloud.com/view/client/job/official-client-trigger/245/

OBS submits from *:testing to final

• https://build.opensuse.org/request/show/519940
• https://build.opensuse.org/request/show/519957

@SamuAlfageme @mstingl
everyhting is at https://download.owncloud.com/desktop/testing/?C=M;O=D

• owncloudclient-2.3.3.tar.xz is there, but I cannot sign it. @guruz your help needed here, I am afraid.

[jnweiger]

owncloud.org website updates for staging owncloud-archive/owncloud.org#1273
@michaelstingl Please review the changelog and double check the deprecation warnings.
https://staging.owncloud.org/changelog/desktop/

[guruz]

Downloaded and installed macOS and Windows versions, they work for me.
I didn't check Linux

[SamuAlfageme]

@jnweiger all linux installations and basic sync runs I did went fine 👍

[jnweiger]

I am doing one more rebuild in OBS: renaming all xUbuntu* to Ubuntu* -- that is how it was with 2.3.2 -- we don't want to break update repos.

[jnweiger]

Rebuilds done. All fine. Let's publish!

[guruz]

@jnweiger Cool! Any way to redirect the Qt562 OBS repo somehow to make people get automated update there? I think @dragotin mentioned that..

[jnweiger]

Hmm. Not sure what @dragotin wanted to achieve. We'll update the qt562 libs together with the clients anyway -- security and bugfix that is. The versiion is fixed at 562 until we decide for 58x or so.

[glannes31]

Hello , 2.3.3 is not publish on owncloud.org . A problem with that ?

[SamuAlfageme]

@glannes31 you're right, looks like https://staging.owncloud.org/install/#install-clients hasn't gone live yet - PR with the changes was merged in owncloud-archive/owncloud.org#1273. I'll ask the admins around.

[jnweiger]

2.3.3 is live:

• OBS pushed
• https://owncloud.org/install/#install-clients pushed
• announcement on https://central.owncloud.org/t/desktop-sync-client-2-3-3-released/8967

[jnweiger]

update the updater: https://github.com/owncloud/enterprise/pull/2246

[guruz]

Closing issue.
We still have pending things in milestone: https://github.com/owncloud/client/milestone/41

[tripplex95]

cant change the "connect to ownCloud on the application windows and connect to ownCloud server"