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 | OK. As of 2021-06-24, there were no security bugs reported as per this filter. |
RC-3: Save one-time snapshots of some reports | (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). 7 items open (I assume the ones that are closed are handled well). RIC-799, RIC-772, RIC-653, RIC-634 are all raised from within the project (and therfore implicitly acknoledged. For RIC-757, RIC-570 I asked for further information. (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 |