Now the tech spec has been updated, we could look at this (release criteria are meant to be directly downstream of the tech spec). At a quick look, the changes don't seem to affect the blocking requirements much, so I'm not sure we need to change the criteria too much. Once the FreeIPA and database server roles are actually ansiblized, we can change the wording "using the official deployment tools provided in the distribution packages" from the criteria - https://fedoraproject.org/wiki/Basic_Release_Criteria#Server_Edition_requirements - to refer to the new ansible roles instead, but until that actually happens we can't really change the criteria as they have to reflect current reality, not future goals :D

Did I miss anything else in the new tech spec that might require changes to the criteria? The current criteria can be seen at https://fedoraproject.org/wiki/Basic_Release_Criteria#Server_Edition_requirements , https://fedoraproject.org/wiki/Fedora_39_Beta_Release_Criteria#Server_Product_requirements , and https://fedoraproject.org/wiki/Fedora_39_Final_Release_Criteria#Server_Edition_requirements .

Of course, if we decide we want to extend the criteria to cover more things - e.g. make more roles release-blocking and hence add them to the criteria, or be more specific about what Cockpit functionality we consider release-blocking and extend that criterion - we can absolutely do that too. That kinda has to be a collective discussion, though, and scoped so that the work to update the criteria and test cases, and automate the tests, is manageable.