[F24 Criteria Change] Cockpit Release Criteria

Simo Sorce simo at redhat.com
Tue Nov 3 15:30:39 UTC 2015


On 02/11/15 08:31, Stephen Gallagher wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 11/01/2015 04:23 AM, Chris Murphy wrote:
>> On Wed, Oct 28, 2015 at 5:11 PM, Dan Mossor <danofsatx at gmail.com>
>> wrote:
>>
>>> 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.
>>
>> OK well seeing as we even have some issues with FOSS software A
>> not getting along with FOSS software B and there's no burden...
>>
>> The question is: should Cockpit have a bug that prevents it from
>> being functional with OSX+Chrome, should it be blocking? What if
>> it's OSX+Firefox?
>>
>> I would say a more practical, and permissive policy would be:
>> should Cockpit have a bug that prevents it from being functional
>> with OSX or Windows using any (Chrome, FireFox, or OS default) then
>> it's a blocking bug. The point is to make sure a Cockpit bug
>> doesn't prevent people on other OS's from using Cockpit and thus
>> benefiting.
>>
>
> That's a fairly reasonable statement. So something like:
>
> * 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
>   - At least one of a) Mozilla Firefox or b) Google Chrome of the latest
>     available version on Windows at compose time.
>   - At least one of a) Mozilla Firefox or b) Google Chrome of the latest
>     available version on OSX at compose time.
>
>
> Would that be satisfactory to everyone?

As long as this does not mean people have to go out and find those 
platforms for testing.

I think it is reasonable to state that there shouldn't be known blocker 
bugs for those platforms, but the onus of testing is on those that like 
them and check on their own. A release criteria must not force anyone to 
test proprietary platforms if there are no know bugs for them, and a bug 
resolution from upstream should be sufficient for us to call it done 
without required testing by Fedora QA or other volunteers.

Simo.

-- 
Simo Sorce * Red Hat, Inc * New York


More information about the server mailing list