On Tue, 2014-06-17 at 15:02 -0700, Adam Williamson wrote:
I've revised the release criteria draft again, with reference to
useful discussions both on-list and at this morning's meeting:
I added the firewall exception for the Cockpit web interface, clarified
the issue about role deployment "at install time", and added new
criteria for the cockpit management interface to be running OOTB and for
roles to meet their "functional requirements, as defined in their role
specification documents" - role specification documents being something
I invented out of my ass at the meeting this morning. View that one as a
trial balloon. :)
As always, thoughts / comments welcome!
Today I've added a Server-specific variant of the 'post-install boot'
requirements criterion from the 'generic' Alpha criteria:
it basically trims out the stuff that doesn't apply to Server.
I'm still thinking about exactly how to present the Product-specific and
generic criteria for F21 as a whole, but for now I'm including all
things that differ at all from the 'generic' criteria on the
Product-specific draft pages I'm working on (I've just started working
on the Workstation criteria).
I also added a criterion requiring user creation to work in scripted
it seems natural to me to include requirements relating to scripted
installation as part of the Server criteria, though they could *perhaps*
go into the generic criteria instead...but it seems like Server is by
far the most likely use case for them. We kind of need a whole set of
kickstart criteria, but we've always kind of punted on creating them, as
it's a big area to try and define...but now might be the time.
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net