Giters

owncloud / files_antivirus

:space_invader: virus scanner for ownCloud

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Release files_antivirus 1.1.0

phil-davis opened this issue · comments

commented

Reason

  • issue #477 PR #478 fixes the problem with Advanced rules not displaying in the UI

    • It was broken in v1.0.0-beta2 but not noticed - see my comments in issue #477

  • Issue #479 could also be looked into and fixed for a patch release. (And review other open issues)

  • issue #472 @s-englert ??

  • issue #473 @s-englert ??

  • issue #488

  • issue #489

Using issue template from /home/testy/src/github/owncloud/QA/tools/release/templates/server_app_release_template.md

Product approval

  • Verify transifex commits are in master: If a folder https://github.com/owncloud//tree/master/l10n exists, then https://drone.owncloud.com/owncloud/ should receive nightly '[tx] updated from transifex` ...
  • Ping pmaier to check info.xml description and screenshot
  • Get approval on translations from pmaier - send the date of the last tx commit from drone to Patrick

QA

  • Create QA Milestone and set the description to $version
  • Move tickets from milestone development to qa (testplan and tickets mentioned in release ticket)
  • Create release branch with the format "release-$version"
  • Create "$version Testplan" (QA templates or Enterprise) -> #490
  • copy new/reopened issues from the previous release ticket as 'Issues to review' below.
  • check if Non-normal Release Process applies, and adapt this checklist.

Documentation

Marketing

Build

All actions to be done on the release branch from here:

  • Bump version in info.xml (no version suffix)
  • Bump "sonar.projectVersion=" in sonar-project.properties (no version suffix)
  • Check php version dependency in info.xml
  • Check minimum ownCloud version dependency in info.xml
  • Change CHANGELOG.md 'Unreleased' to '$version' (today's date)

Beta/RC

  • Ping product owner to create github tag for v${version}-rc1 on release branch (see https://confluence.owncloud.com/display/EN/Product+Owners+List)
  • Build and sign RC tarball from github tag v${version}-rc1 (see handbook for how to build)
  • Upload as Github release using changelog entries
  • Test and document in testplan + manual explorative testing:
    • If this is an enterprise app: Enabling the app must start the grace period
    • Add section "Changlog Testing" using github releases text or CHANGELOG.md from release branch
    • Do changelog tests
    • Do regression tests
    • => Final "Go" from QA (set 'QA-ready' label) => else do another RC after fixing issues in the "release-$version" branch

Final

  • Check that no documentation issues are pending
  • Rename last RC tarball to final
  • Create github tag for final v${version} on release branch
  • Upload as Github release using changelog entries

Publishing

  • Upload tarball to marketplace (see handbook in confluence for details)
  • Publish tarball for customers - old 10, old 10.0 and new portal (see handbook for details)
  • Send mail to release-coordination with link to this ticket and to the changelog
  • Copy email to rocket chat #updates channel

Post-release

commented

There's also another new feature pending for release. I'd keep this open for it. Is the version number 1.0.0 correct/intended? I think it should be 1.1.0 Changing.

commented

Is there a timetable for the release?

commented

Is there a timetable for the release?

Ah, sorry for the delay. We wanted to combine this with other features that are not yet ready. I'll check with engineering, how we can push forward best.

commented

Issues seen while testing

commented

Release is blocked by #491 (comment)

We need to add some logic. The current code can only support two out of three virus scanner backends either way.
Suggested fix: #500

commented

RC3 passed QA with several defects. Most noticably #502

commented

Release done, branch merged back to master.