Release criteria checklist template
This page contains a table with criteria and some notes on what the PTL and commiters need to check as part of release preparation. It is influenced by CII badging criteria CII status: near-RT RIC.
Release Criteria (RC) headline | Criteria details/references |
---|---|
RC-1 PTL: Check that we have a release summary. Committers: check that release notes are updated in RST file in gerrit. | Did every component update their rst release notes & did PTL summarized those on one wiki page? See CII criteria [release_notes] |
RC-2: Check that we have all fixed security bugs listed in release notes | For own source-code bugs this can be handled manually as part of release checklist (If JIRA based security bug has been created) But for containers we should find a technical solution (automated) involving some tool e.g. docker image scanning tool (LFN provided preferred). See also CII criterium [release_notes_vulns] |
RC-3: Save one-time snapshots of some reports | Store a snapshot copy of the reports of the following three criteria into wiki page: (1) The project MUST acknowledge a majority of bug reports submitted in the last 2-12 months (inclusive); the response need not include a fix (link). and (2) The project SHOULD respond to a majority (>50%) of enhancement requests in the last 2-12 months (inclusive). (3) The project's initial response time for any vulnerability report received in the last 6 months MUST be less than or equal to 14 days. (4) code coverage report from last meeting minutes |
RC-4: Check (from meeting notes) that we checked for all L and XL commits that they include unit tests | Copy from meeting minutes the section that talks about all L or XL commits of the last two weeks have also new unit tests. This is our policy. link-to-reviews (gerrit filter instructions // gerrit t-shirt-sizing). |
RC-5: Check that "blocker" code smells in Sonartype have been addressed | Check Sonartype report export and store that export into wiki page |
RC-6: Check that all components have a release branch created. | use "git branch --list -a" to check |
RC-7: Check that image list has been created and same images are referred to in ric-dep RECIPE_EXAMPLE | refer to image list similar to this one: Near-RT RIC (E release) |
RC-8: do we have a demo video on deploying RIC and a demo xapp? |