RC2 is depend on Functest what is continously updated to support the latest version of Kubernetes and OpenStack in this sense the RC2 specific criteria from M2 and M3 is not needed.
David McBride agrees that changing the milestones is okay to optimize the process, but competly remove them is not correct.
In this way the Anuket release procedure has no more quality gate on RC2 completness
Even in CI/CD environment a quality gate is needed
Kenny Paul asks if there is still credibility of the Anuket artifacts if there is no traceability to what was tested in the specific releases
M2
No new issues found for Kuberef and Barometer
RC2 provides no traceability to RA2
RA2 provides traceability to the needed Kubernetes features
TSC Conditionally Approves Nile M2 with the condition that the Kuberef and Barometer issues are added to Jira and with the exception of RA2 traceability in RC2
No objection, approved
Community release manager. Scot Steele and David McBride will have discussion about the release manager process