release template updated.

@guruz some items are marked with 20181109jw -- these are unclear to me. Please help.

1 files changed, 27 insertions, 27 deletions

diff --git a/.github/release_template.md b/.github/release_template.md
index f803d574c..acbaa388f 100644
--- a/.github/release_template.md
+++ b/.github/release_template.md
@@ -1,6 +1,7 @@
 <!--
 This is the template for new release issues.
 (originated from https://github.com/owncloud/client/wiki/Release%20Checklist%20Template)
+(20181109jw: One of these two should be deleted. They will never be in sync otherwise.)
 -->
 
 Copy below text into a task and tick the items:
@@ -13,14 +14,13 @@ Some weeks before the release:
 * [ ] Ensure up-to-date dependencies (e.g. [latest Qt version](http://qt-project.org/downloads#qt-lib) 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
+* [ ] Ensure Windows Overlay DLLs are rebuilt. Why? How?
+* [ ] 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.
+* [ ] 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)
-* [ ] Upload a nightly build of the windows version to virustotal.com
+* [ ] 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/1.X/
+* [ ] 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
 * [ ] Make sure to have `client/ChangeLog` updated
  * use `git log --format=oneline v<lastrelease>...master` if your memory fails you
@@ -29,6 +29,8 @@ Some weeks before the release:
 For first Alpha/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)
+* [ ] Add the new branch v2.X.X for the new version to gitea/jw/client-linux-build
+* [ ] 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](https://ci.owncloud.org/view/translation-sync/job/translation-sync-client/) and [NSIS](https://ci.owncloud.org/view/translation-sync/job/translation-sync-client-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 e.g. http://doc.owncloud.org/desktop/1.X/ exists
@@ -38,17 +40,17 @@ For all alphas, betas and RCs (Copy this section for each alpha/beta/rc):
 * [ ] 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. 
+* [ ] 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 client-linux-tests ob for @SamuAlfageme 's magic Linux-test-all-packages-script
+* [ ] 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 (20180719 jw: FIXME: clarify, no more staging??)
+* [ ] 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 devel@owncloud.org and testpilots@owncloud.org (make sure to mention it is an rc). Link to the central post so discussion happens there.
@@ -56,12 +58,12 @@ For all alphas, betas and RCs (Copy this section for each alpha/beta/rc):
 
 One week before the final 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)
+* [ ] 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)
 
 Day before final Release:
-* [ ] Check the translations coming from transifex: All synchronized?
-* [ ] Run the tx.pl scripts on the final code tag
+* [ ] 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?)
 * [ ] Run ```make test```
 * [ ] Run smashbox (20180719 jw: FIXME: add details, how?)
 * [ ] Inform product management and marketing that we are 1 day out
@@ -70,25 +72,23 @@ 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)
+* [ ] Create build for theme 'ownCloud' using client-trigger (uncheck the "daily build" checkbox, use the proper dropdown for version suffix)
+* [ ] 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. 
-* [ ] 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)```
+* [ ] Check if *tar.xz.asc files are there. If not resort to https://github.com/owncloud/enterprise/wiki/Desktop-Signing-Knowledge
+* [ ] 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```
 * [ ] 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)
+* [ ] Linux: Run https://jenkins.int.owncloud.com/job/client-linux-tests/ with REPO_URL=https://download.opensuse.org/repositories/isv:/ownCloud:/desktop:/testing
 * [ ] 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
+* [ ] 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```
-* [ ] 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)
@@ -112,12 +112,12 @@ On Release Day (for final release):
 * [ ] 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.
+* [ ] 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 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.
+* [ ] 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.
 
 ```