On 10/23/2015 04:42 PM, Simo Sorce wrote:
On 22/10/15 14:35, Stephen Gallagher wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Recently, we discovered a bug in gnutls that caused Cockpit to be
> unreachable by recent versions of Google Chrome. It was ambiguous what
> the release criteria actually means, since it didn't specify which
> browser applications were blocking. I'd like to propose the following
> additional wording for Cockpit criteria:
>
> * All Cockpit functional criteria must be satisfied when the user is
> running any of the following blocking browsers:
> - Mozilla Firefox as shipped in the same Fedora release
> - Mozilla Firefox of the latest available version on Windows at
> compose time.
> - Mozilla Firefox of the latest available version on OSX at compose
> time.
> - Google Chrome of the latest available version on Fedora at compose
> time.
> - Google Chrome of the latest available version on Windows at compose
> time.
> - Google Chrome of the latest available version on OSX at compose time.
>
>
> Alternately, we could decide that it's only *blocking* if the above
> browsers work with Cockpit when the browser is running on Fedora, but
> that is somewhat at odds with our reasoning for having a management
> console as a web UI in the first place: that it is accessible
> regardless of the client system.
>
> Comments welcome, but please keep replies on the
> test(a)lists.fedoraproject.org list, as that's where criteria decisions
> are made.
although I totally understand the reason I am against a release criteria
*for Fedora* that forces a tester to install non-free Software (both OS
*and* Browser).
Simo.
I'm with Simo. I *DO NOT* want to place a burden on a FOSS operating
system to be 100% compatible with non-FOSS software.
--
Dan Mossor, RHCSA
Systems Engineer
Fedora Server WG | Fedora KDE WG | Fedora QA Team
Fedora Infrastructure Apprentice
FAS: dmossor IRC: danofsatx
San Antonio, Texas, USA