2.3.0 release

[guruz]

Release-1 Week:

• 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
• 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.
• 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
• Communicate the release schedule on mailinglist release-coordination@owncloud.com. Give a high level overview of the upcoming new features, changes etc.
• Make sure to have client/ChangeLog updated
  • use git log --format=oneline v<lastrelease>...master if your memory fails you
• Ensure marketing is aware and prepared for the release (social, .com website, cust. communications)
• Inform GCX knows the next version is about 1 week out (gcx@owncloud.com)

beta1:

• Branch off a release branch called -rcX or -betaX
• 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 both themes 'ownCloud' and 'testpilotcould' (this magically interacts with the ownCloud-client-source job)
• Copy builds from daily to testing on download.owncloud.com, double check the download links.
• Update the owncloud.org webpage, section testing, by providing a pull request to the https://github.com/owncloud/owncloud.org github repository.
• Inform community mailinglists devel@owncloud.org and testpilots@owncloud.org and packaging@owncloud.org
• Inform internal mailinglist release-coordination@owncloud.com
• Create a signed tag using git tag -u E94E7B37 tagname
• Check crash reporter

rc1

• Branch off a release branch called -rcX or -betaX
• 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 both themes 'ownCloud' and 'testpilotcould' (this magically interacts with the ownCloud-client-source job)
• Copy builds from daily to testing on download.owncloud.com, double check the download links.
• Update the owncloud.org webpage, section testing, by providing a pull request to the https://github.com/owncloud/owncloud.org github repository.
• Inform community mailinglists devel@owncloud.org and testpilots@owncloud.org and packaging@owncloud.org
• Inform internal mailinglist release-coordination@owncloud.com
• Create a signed tag using git tag -u E94E7B37 tagname
• Check crash reporter

rc2

• Branch off a release branch called -rcX or -betaX
• 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 both themes 'ownCloud' and 'testpilotcould' (this magically interacts with the ownCloud-client-source job)
• Copy builds from daily to testing on download.owncloud.com, double check the download links.
• Update the owncloud.org webpage, section testing, by providing a pull request to the https://github.com/owncloud/owncloud.org github repository.
• Inform community mailinglists devel@owncloud.org and testpilots@owncloud.org and packaging@owncloud.org
• Inform internal mailinglist release-coordination@owncloud.com
• Create a signed tag using git tag -u E94E7B37 tagname
• Check crash reporter

rc3

• Branch off a release branch called -rcX or -betaX
• 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 both themes 'ownCloud' and 'testpilotcould' (this magically interacts with the ownCloud-client-source job)
• Copy builds from daily to testing on download.owncloud.com, double check the download links.
• Update the owncloud.org webpage, section testing, by providing a pull request to the https://github.com/owncloud/owncloud.org github repository.
• Inform community mailinglists devel@owncloud.org and testpilots@owncloud.org and packaging@owncloud.org
• Inform internal mailinglist release-coordination@owncloud.com
• Create a signed tag using git tag -u E94E7B37 tagname
• 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.
• check if enterprise issues are fixed

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
• Double check VERSION.cmake: Check the version number settings and suffix (beta etc.) to be removed. Commit change to release branch only!
• Add last updates to Changelog in the client source repository.
• Create tar ball (automated by ownCloud-client-source jenkins job) and immediately sign it (asc file).
• Copy the source tarball from the daily to the stable dir on download.o.o
• Announce the source tarball on the packaging mailing list packaging@owncloud.org
• Announce on https://central.owncloud.org
• Build Windows packages
• Build Mac OS X packages
• Build Linux packages by running the jenkins job ownCloud-client-linux with proper parameters
  • Update OBS repository isv:ownCloud:desktop (or isv:ownCloud:community:testing for RC/Beta)
  • Check if patches still apply in the linux packages
• Update the testing repository to the latest stable version.
• Inform GCX that a new tarball is available.
• 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) and the changelog on owncloud.org. 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)
• Update ASCII Changelog on http://download.owncloud.com/download/changelog-client
• Keep the packaging mailinglist packaging@owncloud.org informed and announce the final sources.
• Create git signed tag in github 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)
• Take pride and celebrate!
• Days later: Update the updater script clientupdater.php
• 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

[SamuAlfageme]

🆕 QA over Testing Scenarios 2.3

• Application Password
• Share Dialog mailto: option
• Backup restore options
• External Storage Exclusion
• Sync same local folder with multiple servers
• Conflict files: use timestamp in filenames
• New actions
  • Sync now
  • New account...
• New WebDAV endpoint
• Sync scheduling:
  • Include unavailable local sync folders when they are available again.
  • Pause synchronization doesn't pause the synchronization
  • Logged out accounts stay "Waiting" if unpaused
• Do not trigger syncs if files under hidden directories are modified
• Shibboleth bugfixes
  • Shibboleth accounts don't work after restart
  • The username in SAML logins doesn't appear next to the URL in the account tab
  • Shibboleth accounts don't need the credentials to log in after wiping its keychain entry
  • Cookies: Use different DB for different accounts
• HTTP Redirections
• Remove all cookies when logging out
• Overlay improvements
• 🚫Do not blacklist 507 InsufficientStorage -> Reverted in Make insufficient storage errors visible without attempting too frequent uploads #5537

---

💥 Regression test on the whole client

• Installer/Uninstaller
• Setup
• Syncing
  • User stop syncing
  • Test resuming of uploads
  • Test resuming download
  • Modifying files when the sync is running
  • Test shared folder (see Note below)
• 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:

#5553 :

HTTP Redirections after #4905

Using the example redirection server I'm not being able to connect, getting the not successful with code 200 in the logs:

OCC::PropfindJob::finished: PROPFIND request *not* successful, http result code is 200 ""

Test shared folder: Adding a file there should cause an error. The error should be blacklisted after a few sync.

These kind of errors are not being blacklisted anymore?

Command Line Client - Check that no username/password is logged in cleartext during operation.

owncloudcmd ./ https://demo.owncloud.org
Error receiving trust for a CA certificate
...
Error receiving trust for a CA certificate
Please enter user name: test
Password for user test:

The user name is, of course, present either in the username:pass owncloudcmd form or the interactive one. (Wiki entry should be updated?)

[guruz]

@jturcotte @ogoffart @ckamm @SamuAlfageme OK with an 2.3.1 early next week with crash fixes?
Then we don't enable the auto updater for 2.3.0 but only for 2.3.1

I'll also refrain from posting on more announcement mailing lists

[guruz]

One crash fix is here #5579

More fixes to come from @ogoffart (see discussions on IRC)