Release files_antivirus 1.1.0

[phil-davis]

Reason

• issue Advanced settings (list of rules) is not displayed #477 PR Fix #477 #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 Advanced settings (list of rules) is not displayed #477

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

• issue Encapsulated type count is wrong in ICAPClient #472 @s-englert ??

• issue ICAP Response Modification Mode is missing #473 @s-englert ??

• issue Add ICAP Scanner for FortiSandbox #488

• issue Add ICAP Scanner for McAfee Web Gateway 10.x #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) -> [QA] 1.1.0 Testplan #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

• Changes in the docs needed? If so create issue in owncloud/docs-server. -> [QA] Two new virus scanners added to files_antivirus docs-server#471

Marketing

• Ping @owncloud/marketing
• Update https://confluence.owncloud.com/display/PROD/Upcoming+Releases
• Request a screenshot if the app is new or changed fundamentally

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

• Add a new 'Unreleased' section in CHANGELOG.md (and also update links at the bottom!)
• Create PR to merge changes back to the master branch with description "Closes #XYZ" with the release ticket number
• Rename QA milestone to $version and close the milestone
• Update https://confluence.owncloud.com/display/PROD/Upcoming+Releases
• Ensure release template is up to date
• Ensure the testplan template (community or enterprise) is up to date
• Close the testplan issue

[pmaier1]

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.

[pmaier1]

cc @s-englert

[prsnbrg]

Is there a timetable for the release?

[jnweiger]

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.

[jnweiger]

Issues seen while testing

• [QA] Regression: AV-Failed error with clamav #491
• [QA] doc link for executable and params point to the wrong doc #455 (old issue, still unfixed)
• [QA] Daemon and Executable mode are specific to ClamAV #496
• [QA] Fortinet (ICAP) backend somtimes fails to detect a zipped eicar test virus #499
• Another attempt to fix the ICAP encapsulation #500
• [QA] duplicate UI elements when switching from fortinet to mcafee #501
• [QA] McAfee Webgateway causes a 60 seconds delay on each upload #502
• [QA] Virus message from McAfee Webgateway overwrites text in texteditor #503
• [QA] failing upload misses error messages from virus scanner web#7432

[jnweiger]

1.1.0 RC2 is ready for QA: https://github.com/owncloud/files_antivirus/releases/tag/v1.1.0-rc.2

[jnweiger]

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

[jnweiger]

RC3 passed QA with several defects. Most noticably #502

[jnweiger]

Release done, branch merged back to master.