Client: 2.5.1

Created on 19 Oct 2018  路  12Comments  路  Source: owncloud/client

rc1
Aborted, missed 62252d0012c00dbba64dbe3210f104f7ee58434c

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 "nightly build" checkbox, use the proper dropdown for version suffix) EDIT: specify 'proper'
  • [ ] Create build for theme 'testpilotcloud' using client-trigger (uncheck the "nightly build" checkbox, use the proper dropdown for version suffix) EDIT: specify 'proper'
  • [x] 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.
  • [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 client-linux-tests ob for @SamuAlfageme 's magic Linux-test-all-packages-script
  • [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 EDIT: take care: no more staging
  • [x] Inform packagers @dragotin (openSUSE), @hefee (Debian), ??? (Fedora)
  • [ ] 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

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 EDIT: 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 "nightly build" checkbox, use the proper dropdown for version suffix) EDIT: specify 'proper'
  • [x] Create build for theme 'testpilotcloud' using client-trigger (uncheck the "nightly build" checkbox, use the proper dropdown for version suffix) EDIT: specify 'proper'
  • [x] 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.
  • [x] 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)
  • [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 @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)
  • [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: 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
  • [x] check osc meta prj for needed updates between :desktop:testing and :desktop
  • [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 a (draft) release on https://github.com/owncloud/client/releases
  • [x] Update https://owncloud.org/changelog/desktop-client/
  • [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] 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])
  • [ ] 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:

  • [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.

A few days after the release (for final release)

Most helpful comment

All 12 comments

Checked some of the checkmarks, that I could do or know are done. Most of the others, I cannot. Please help!
I've added several EDIT remarks. These should be corporated into the template.

virustotal report

  • ownCloud-2.5.1.10928.10812-daily20181029.msi 0/70
  • ownCloud-2.5.1.10928.10812-daily20181029.en-US.msi 0/70
  • testpilotcloud-2.6.0.10562-daily20181029-setup.exe 0/64
  • testpilotcloud-2.6.0.10931.10815-daily20181029.msi 0/55
    -> great!

ChangeLog so far: https://github.com/owncloud/client/blob/2.5/ChangeLog (Still WiP if we get more in)

@jnweiger I did my part for now, you can take over with files moving, OBS stuff and owncloud.org, then I can do the mailings.. (but reply to my question about the @SamuAlfageme distro tests first, I didn't run them yet)
Pre-release on https://github.com/owncloud/client/releases/edit/untagged-79b1d48dc598227c1da4

Samuels distro test succeeded now. There was a typo in the Ubuntu 17.10 test.

@dragotin (openSUSE) @hefee (Debian) ^^

thanks @guruz, the openSUSE package is already here:
https://software.opensuse.org//download.html?project=KDE%3AExtra&package=owncloud-client
and on it's way to Tumbleweed:
https://build.opensuse.org/request/show/647667
@PVince81 :)

online updater: https://github.com/owncloud/enterprise/pull/2981

Deployed:
```
sh /srv/www/updates.owncloud.com/client/scripts/check_update_checker.sh
Platform linux : ownCloud Client 2.5.1
Platform macos : ownCloud Client 2.5.1 (build 10818)
Platform win32 : ownCloud Client 2.4.3 (build 10188)
Platform win32 -d msi=true : ownCloud Client 2.5.1 (build 10807)

Was this page helpful?
0 / 5 - 0 ratings