On 18.06.2014 01:48, Stephen John Smoogen wrote:
On 17 June 2014 16:02, Adam Williamson <awilliam(a)redhat.com
<mailto:awilliam@redhat.com>> wrote:
I've revised the release criteria draft again, with reference to the
useful discussions both on-list and at this morning's meeting:
https://fedoraproject.org/wiki/User:Adamwill/Draft_server_release_criteria
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!
OK. First of all, where could I 'test' any of these things on a Fedora
20 system. I haven't seen a lot of discussion on list about how someone
could see current code and I am always leery of hail-mary code drops
where developers being the overly optimistic people they are don't see
that the real deadline coming up until its 23:59.
Good point.
Here's how to test Cockpit. We try to do releases one or two times a
week into both Rawhide and Fedora 20 updates testing.
Fedora Rawhide:
$ sudo yum install cockpit
$ sudo iptables -F # [0]
->
http://localhost:1001
Fedora 20:
$ sudo yum install --enablerepo=updates-testing cockpit
$ sudo iptables -F # [0]
$ sudo setenforce 0 # fixed in rawhide
->
http://localhost:1001
Cheers,
Stef
[0]
https://bugzilla.redhat.com/show_bug.cgi?id=1110711