Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

files_antivirus 1.0.0 #385

Closed
27 of 32 tasks
jnweiger opened this issue Nov 24, 2020 · 15 comments · Fixed by #447
Closed
27 of 32 tasks

files_antivirus 1.0.0 #385

jnweiger opened this issue Nov 24, 2020 · 15 comments · Fixed by #447
Assignees
Milestone

Comments

@jnweiger
Copy link
Contributor

jnweiger commented Nov 24, 2020

Reason

Product approval

QA

  • Generate Changelog
  • Create QA Milestone and set the description to $version
  • Move items from development to qa
  • Create release branch with the format "release-$version"
  • Create "$version Testplan" [QA] 1.0.0 Testplan #391

Documentation

  • Changes in the docs needed? If so create issue in owncloud/docs.

Marketing

  • Ping @owncloud/marketing

Build

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

  • Bump version in info.xml (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

  • Create github tag for v${version}RC1 on release branch
  • 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 => 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 (see handbook in confluence for details) - https://customer.owncloud.com and https://portal.owncloud.com
  • Send mail to release-coordination with link to this ticket and to the changelog
  • Copy email to rocket chat #updates channel

Post-release

  • Rename QA milestone to $version
  • 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
  • Close the milestone
  • Ensure release template is up to date
@jnweiger jnweiger added the orga label Nov 24, 2020
@davitol davitol pinned this issue Nov 24, 2020
@jnweiger jnweiger changed the title file_antivirus 0.16.0 files_antivirus 0.16.0 Jan 10, 2021
@jnweiger jnweiger added this to the QA milestone Jan 10, 2021
@jnweiger
Copy link
Contributor Author

jnweiger commented Feb 4, 2021

Issues opened while testing 0.16.0

@jnweiger
Copy link
Contributor Author

jnweiger commented Feb 10, 2021

tested with 0.16.0RC1: installed sucessfully at oc10.6.0

Setup done for

  • internal clamav
  • Clamav c-icap (docker deepdiver/icap-clamav-service)
  • Kaspersky Scan engine 2.0.0.1157 (./install with GUI)
    via hetzner-deploy/setup_icap_kaspersky.sh

@jnweiger
Copy link
Contributor Author

jnweiger commented Feb 15, 2021

Testplan #391 completed with issues.
See the lists in #385 (comment) and https://github.com/owncloud/icap/issues/5#issuecomment-777289481
I recommed that at least #395, #400 and https://github.com/owncloud/icap/issues/22, https://github.com/owncloud/icap/issues/23 should be addressed for the release.

@DeepDiver1975
Copy link
Member

we just merged #413 into master
this adds McAfee support - we might want to add this to docs, release notes as well as app description

@hodyroff @pmaier1 @micbar

@jnweiger
Copy link
Contributor Author

jnweiger commented Apr 6, 2021

Back to dev. 0.16.0 will not happen like this. A 1.0.0 beta is under way.

@pmaier1
Copy link
Contributor

pmaier1 commented Apr 6, 2021

Info.xml update #415

@jnweiger jnweiger changed the title files_antivirus 0.16.0 files_antivirus 1.0.0 Apr 8, 2021
@micbar
Copy link
Contributor

micbar commented May 3, 2021

@VicDeo

This comment has been minimized.

@C0rby
Copy link

C0rby commented May 3, 2021

https://gitea.owncloud.services/security/files_antivirus/pulls/1 also needs to be included to the release.

@jnweiger
Copy link
Contributor Author

@VicDeo
Copy link
Member

VicDeo commented May 20, 2021

@jnweiger if i'm not mistaken https://github.com/owncloud/icap/commit/a2995f22937d7c98015dfb4a2dde36cf00bb8a6a was merged as #415

#442 is critical for release as it is port of https://gitea.owncloud.services/security/files_antivirus/pulls/1 to the app code base

also Beta 3 has the following fixes for ICAP feature in addition to listed in the release:
#438 (fixed with #441)
#433 (fixed with #440)

@jnweiger
Copy link
Contributor Author

jnweiger commented May 21, 2021

Changlog Testing with 1.0.0-rc2

@jnweiger
Copy link
Contributor Author

jnweiger commented May 21, 2021

Issues opened while testing 1.0.0

20210520

@mmattel
Copy link

mmattel commented Jun 3, 2021

  • As we have now updated docs reflecting the changes, you should rethink if you want to describe settings in the UI or pointing to docs. Atm, the text looks akward as is is multiline and has a non professional look.
  • The Mcafee setting was taking all values to work, not only the particular highlighted one.

For both, there was a chat discussion with @jnweiger during writing the docs.

@pmaier1
Copy link
Contributor

pmaier1 commented Jun 7, 2021

Screenshot from 2021-06-07 11-11-00

I guess you are referring to this one. I agree that we should remove the specific configuration hints and point to the docs. Anyway, this is cosmetic, not a blocker for the release. Let's fix it afterwards.

  • Remove "possible values..."
  • Add link to docs

@jnweiger jnweiger mentioned this issue Jun 7, 2021
@jnweiger jnweiger unpinned this issue Jun 7, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

8 participants