nextcloud-desktop/.github/release_template.md

Open an issue called 'Release 2.x.0' in client repository and copy below text into a task and tick the items:

---

Major/Minor release template. Enter here, when we have three estimated dates:

• Date of feature freeze
• Date of QA start
• Date of final

Before Branching Off:

• Dev: Make sure previous minor/major version's branch is merged into current master branch e.g. 2.6 into master "one flow" - @TheOneRing @guruz
• Dev: Check dependencies for updates - @TheOneRing @guruz
• Dev: Update ChangeLog - @TheOneRing @guruz
• QA: Update Test Plans - @HanaGemela @jnweiger
• QA: Review list of supported platforms - @HanaGemela @jnweiger @TheOneRing @guruz
• QA: Update documentation - @HanaGemela @jnweiger
• QA: Check Sprint Board for remaining issues - @HanaGemela @jnweiger

On the Day of the First Daily Build of the New Branch:

• Dev: Internally announce it feature freeze - @TheOneRing @guruz
• Dev: Edit VERSION.cmake - @TheOneRing @guruz
• QA: Adjust Linux Templates - @HanaGemela @jnweiger
• QA: Adjust ownBrander - @HanaGemela @jnweiger
• QA: Adjust AppVeyor - @HanaGemela @jnweiger
• QA: Adjust drone - @HanaGemela @jnweiger
• QA: Adjust translation jobs - @HanaGemela @jnweiger
• QA: Use obs-copyprj.sh to backup the desktop project to desktop:client-2.6.x (unless already done) - @HanaGemela @jnweiger
• Dev: Start running automated tests on the dailies - @TheOneRing @guruz

After the First Daily Build of the New Branch:

• Announce the new branch to community and advertise dailies for public testing - marketing
• QA: Antivirus scan - @HanaGemela @jnweiger

For All Sprint Builds:

• Add latest 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 in the release branch
• (TODO: move to patch-release checklist) 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 builds for theme 'ownCloud' and 'testpilotcloud' @jnweiger @hvonreth
• Check if *tar.xz.asc files are there. If not follow the instructions
• Run the smoke test
• Linux: Run test with repo=https://download.opensuse.org/repositories/isv:/ownCloud:/desktop:/testing
• Linux: add/remove build targets @hvonreth @jnweiger
• Create a signed tag using git tag -u E94E7B37 tagname @guruz @jnweiger (TODO: is this still needed?)
• Update the wordpress content at owncloud.org/download @florian - marketing
• Inform packagers: @dragotin (openSUSE) - marketing
• Announce on central (copy old announcement, link to changelog, download links etc) TODO: itemize what goes into the announcement: deprecation warnings. ... - marketing
• 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. - marketing
• Check crash reporter after some days @guruz @hvonreth
• Update unstable channel in the owncloud hosted auto updater. Instructions here and here @hgemela @jnweiger

One Week Before the Final Release (Skip this section for patch releases):

• Communicate the release schedule on rocket-chat #release-coordination and 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) - 1 week before minor, 2 weeks before major (minor/major is about impact)
• Inform Achim (ageissel@owncloud.com) and GCX that the next version will be in 1 week (gcx@owncloud.com) - marketing

One Day Before the Final Release:

• Check crash reporter for bad crashes of this RC (same crash happening to many users) @guruz @hvonreth
• Check the translations coming from transifex: All synchronized? TODO: (20181109jw: where? how?)
• Review drone results: make test TODO: Mac, Lin, Win?
• Run smashbox (20180719 jw: FIXME: add details, how?) (ask @dschmidt, put link to smashbox results here)
• Inform product management and marketing and #general channel in rocker chat that we are 1 day out

On Release Day (for the Final Release):

For major, minor, and patch releases, but skip this section for ALPHA/BETA

• Add last updates to Changelog in the client source repository @hvonreth @hgemela
• Branch off a release branch once QA is done, tag with a release vA.B.C (with v, as v is for tags) @hvonreth @guruz
• Edit VERSION.cmake hange suffix from 'git' or 'rc' to empty string "". Commit the result to the release branch only @hvonreth @guruz
• Create builds for theme 'ownCloud' and 'testpilotcloud' @jnweiger @hvonreth
• Check if *tar.xz.asc files are here. If not follow the instructions
• Branch isv:ownCloud:desktop to isv:ownCloud:desktop:client-X.Y.Z using obs_integration the Linux packages will always land in the :testing repository - @jnweiger obs-deepcopy-prj.sh isv:ownCloud:desktop isv:ownCloud:desktop:client-2.5.1
• Run the smoke test
• Linux: Run test repo=https://download.opensuse.org/repositories/isv:/ownCloud:/desktop:/testing - @jnweiger
• 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: also copy the *.linux-repo.html files from testing to stable and edit away the :testing strings.
• Linux: disable publishing on project 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
• Linux: Re-enable OBS publishing on the project after official release date and if all distros build (check for accidentially disabled packages too)
• Test all advertised download links to have the expected version
• 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
• 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.
• Create same tag for MSI code - @dschmidt
• Create same tag for Windows toolchain - @dschmidt
• Create same tag (actually a symlink) for macOS toolchain - @dschmidt
• Create a (draft) release here
• 1h later check changelog on website -> it pulls from the master branch ChangeLog file hourly. - @jnweiger
• Update org website -> Download ownCloud -> click open 'Desktop Client', edit win/mac/lin, each all three tabs "Production", "Technical Preview" [disabled], "Test pilot" enabled, edit the links.
• Add the previous release to older version @jnweiger + fwittek
• Ping marketing to do their actions
• Take pride and celebrate!
• Tell GCX to increment the minimum supported version for enterprise customers - @mstingl
• Check if minimum.supported.desktop.version needs to be updated in server
• Ensure that the client release template is up to date
• After OBS built everything, disable publishing in OBS to prevent that accidential rebuilds hit the end users.- @jnweiger

A few days after the release (for final release)

• Check the crash reporter if auto update is a good idea or we need a new release
• Update the owncloud hosted auto updater