Final Handover

[cgi1]

• Full Access to Repository (Admin Rights)
• Outcome of Project Kickoff #7 => Agree on input set for acceptance test
• Test files to be uploaded to the testing branch (@tschmidtb51 / @mfd2007)
• Communicate Release Candidate commit number (target date: 2022-02-25, latest 2022-02-28; @cgi1)
• Test by customer (30 day timespan)
  • Checking Conformance Targets for CVRF CSAF Converter from CSAF 2.0 specification
  • Convert agreed set of input files and validate output files
  • Document/Communicate problems/findings in GitHub Issues
• Agree on test outcome, possible defects and issues that cannot be fixed in project time/budget ("Abnahmeprotokoll")
• Fix defects as agreed
• Document issues that cannot be fixed in project time/budget
• Project closing

[pixelkunst-net]

I would suggest that all test files for acceptance must be in a defined folder in the repository at a defined time (transparent documentation for all what has been tested). Such a folder could be https://github.com/csaf-tools/CVRF-CSAF-Converter/tree/main/examples/1.2 or a newly created folder, but needs to be documented.

[pixelkunst-net]

following issues have been picked for prioritized implementation in the last status call before release candidate:

• Validate CSAF 2.0 6.1.26 Document Category special case #13 - to be fixed as part of the "turvallisuusneuvonta" (mandatory tests) integration
• Encode HTML in JSON output #5 - this is a "great to have" feature

[cgi1]

@sustefil: Please create git tag -a 1.0.0-rc1 today and annotate it to the project. Afterwards, we inform @tschmidtb51 and @mfd2007 via mail.

[sustefil]

Hi @cgi1 @tschmidtb51 @mfd2007

Release candidate is here:

https://github.com/csaf-tools/CVRF-CSAF-Converter/releases

And also on PyPI:

https://pypi.org/project/cvrf2csaf/