Release criteria checklist - Release E

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 E release highlights = high-level release notes" in E release (Dec 2021)) as per copy of (b) per-component release notes (see 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 2021-12-03, there were no security bugs 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): 11 open bug reports since D release ((I assume the ones that are closed are handled well). All 11 have been discussed in the project meeting. RIC-861 to RIC-865 have been raised this week and I (Thoralf) am the reporter, and as PTL I promise I have acknowledged them to the reporter. 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 updated here under "New feature requests": 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). Note we address some "blocker bugs" that Sonartype complained about: RIC-802, RIC-863. Other somewhat-security-related fixes: RIC-858, RIC-828. OK (4) code coverage report from last meeting minutes - meeting minutes from 2021-11-23 contain the summary. The report snapshots are in version 4 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 2021-11-23, 2021-11-09, 2021-10-12, 2021-09-28, 2021-09-04, 2021-08-17, 2021-07-06
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 4 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/e-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 (E release)