On 01.10.2014 04:06, Adam Williamson wrote:
On Mon, 2014-09-29 at 17:19 -0700, Adam Williamson wrote:
Hi, folks. So, I drew up a rough draft of the Server release criteria for Beta and Final as I suggest they might be. We could kick it around at tomorrow's meeting if desired. Here we go:
So, here's the second draft of the Beta criteria, with input from today's meeting incorporated. TC1 is rolling now or soon, so I'd like to put these into effect ASAP - if no-one has objections, I'll probably push them out live tomorrow.
For now I suggest we stuff the FreeIPA requirements into the criteria explicitly denoted as a temporary measure, and for Final or F22 we implement the plan to have role requirements defined somewhere else for the criteria to reference.
------------- CUT HERE ---------------
=== Remote logging ===
It must be possible to forward system logs to a remote system using Server packages.
=== Firewall configuration ===
Release-blocking roles must be able to report their status in regard to the system firewall as described in the [[Server/Technical_Specification#Firewall|technical specification]].
=== Roles ===
Release-blocking roles and the supported role configuration interfaces must meet the core functional [[Server/Technical_Specification#Role_Definition_Requirements|Role Definition Requirements]] to the extent that supported roles can be successfully started, stopped, brought to a working configuration, and queried.
=== Cockpit management interface ===
It must be possible to log in to the default Cockpit instance and use it to:
- View the system's logs
- View the system's running services
- Enrol the system to a FreeIPA or Active Directory domain
I checked with the Cockpit guys, and we're fine not adding any further criteria here for Fedora 21. We will obviously make an effort to have functionality well beyond the above, but bugs would not be blockers.
Cheers,
Stef