Release criteria checklist - Release H
- Thoralf Czichy
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 (a) release summary. Committers: (b) check that release notes are updated in RST file in gerrit. | OK PTL created this (a) summary (under "Achieved F release highlights = high-level release notes" in F release) as per copy of (b) per-component release notes (see version 1 of attachment to this page) and as per JIRA items that we marked as "done" (link). |
| RC-2: Check that we have all fixed security bugs listed in release notes | OK As of 2023-06-13, there was no new security bug reported as per this filter. |
| RC-3: Save one-time snapshots of some reports | OK (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): 14 bug reports since G release (I assume the 10 that are closed are handled well). The four open ones have been discussed in the project meeting. OK (2) The project SHOULD respond to a majority (>50%) of enhancement requests in the last 2-12 months (inclusive): link. I am not aware of external feature request raised towards near-RT RIC. Instructions are available under "New feature requests" in Tools (mailing list, JIRA, Gerrit) OK (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: no vulnerability reports received (see filter). OK (4) The report snapshots and the code coverage report (text file) are in version 7 of coverage.zip in the attachments of this wiki page: Code coverage reports |
| RC-4: Check (from meeting notes) that we checked for all L and XL commits that they include unit tests | OK This was done on 2023-05-23, 2023-05-09, 2023-04-09, 2023-03-28, 2023-02-28 |
| RC-5: Check that "blocker" code smells in Sonartype have been addressed | OK Check Sonartype report export and store that export into wiki page: The report snapshots are in version 7 of coverage.zip in the attachments of this wiki page: Code coverage reports |
| RC-6: Check that all components have a release branch created. | OK Check done ("git branch --list -a" → ... remotes/origin/f-release ...) |
| RC-7: Check that image list has been created and same images are referred to in ric-dep RECIPE_EXAMPLE | OK Near-RT RIC (H release) |
| RC-8: do we have a demo video on deploying RIC and a demo xapp? | OK see at the top (or end) of the demo page |