On Thu, Mar 12, 2020 at 2:58 PM Kamil Paral wrote:
> The adjusted criterion seems to affect only this test case:
> https://fedoraproject.org/wiki/QA:Testcase_desktop_menus
>
> My current plan is to redo it somewhat. I want to:
>
> 1. Drop all instructions to run applications from Testcase_desktop
On Mon, Mar 23, 2020 at 8:04 PM Kamil Paral wrote:
> On Thu, Mar 12, 2020 at 10:59 AM Kamil Paral wrote:
>
>> It has been 7 days since the last response to the thread and I received
>> no further complaints, so I've put the criterion into effect:
>>
>> https://fedoraproject.org/w/index.php?title
On Thu, Mar 12, 2020 at 10:59 AM Kamil Paral wrote:
> It has been 7 days since the last response to the thread and I received no
> further complaints, so I've put the criterion into effect:
>
> https://fedoraproject.org/w/index.php?title=Fedora_32_Final_Release_Criteria&type=revision&diff=568145&
On Thu, 2020-03-12 at 14:58 +0100, Kamil Paral wrote:
> On Thu, Mar 12, 2020 at 10:59 AM Kamil Paral wrote:
>
> > It has been 7 days since the last response to the thread and I received no
> > further complaints, so I've put the criterion into effect:
> >
> > https://fedoraproject.org/w/index.ph
On Thu, Mar 12, 2020 at 2:58 PM Kamil Paral wrote:
> Note: In point 2), we don't actually need 10 different test cases
> (templated or not). We might just create Testcase_desktop_app_single
> instead of those 10 and differentiate them on the matrix level the same way
> as we do with e.g. "Testcas
On Thu, Mar 12, 2020 at 3:01 PM Jared K. Smith
wrote:
> On Mon, Feb 17, 2020 at 9:31 AM Kamil Paral wrote:
>
>> There are some high-profile types of applications that I considered
>> including in the list above, but didn’t in the end:
>>
>> * word editor (e.g. libreoffice-writer)
>>
>> * sprea
On Mon, Feb 17, 2020 at 9:31 AM Kamil Paral wrote:
> There are some high-profile types of applications that I considered
> including in the list above, but didn’t in the end:
>
> * word editor (e.g. libreoffice-writer)
>
> * spreadsheet editor (e.g. libreoffice-calc)
>
> * video player (e.g
On Thu, Mar 12, 2020 at 10:59 AM Kamil Paral wrote:
> It has been 7 days since the last response to the thread and I received no
> further complaints, so I've put the criterion into effect:
>
> https://fedoraproject.org/w/index.php?title=Fedora_32_Final_Release_Criteria&type=revision&diff=568145&
It has been 7 days since the last response to the thread and I received no
further complaints, so I've put the criterion into effect:
https://fedoraproject.org/w/index.php?title=Fedora_32_Final_Release_Criteria&type=revision&diff=568145&oldid=564126
I've done slight tweaks compared to the original
On Wed, Mar 4, 2020 at 9:28 PM Ben Cotton wrote:
> On Wed, Mar 4, 2020 at 1:55 PM Kamil Paral wrote:
> >
> > """
> > If there are multiple applications of the same type (e.g. several web
> browsers), the primary/default one must satisfy the requirements. If the
> primary/default application can'
On Wed, Mar 4, 2020 at 1:55 PM Kamil Paral wrote:
>
> """
> If there are multiple applications of the same type (e.g. several web
> browsers), the primary/default one must satisfy the requirements. If the
> primary/default application can't be determined, only one of said
> applications must sa
On Tue, Mar 3, 2020 at 2:43 PM Kamil Paral wrote:
> I haven't received much feedback on this proposal. On test list and kde
> list, there was a short follow-up regarding the list of release-blocking
> applications. On kde list, Kevin disagreed because it lowers the guaranteed
> quality bar for KD
On Tue, Mar 3, 2020 at 2:44 PM Kamil Paral wrote:
> On Mon, Feb 17, 2020 at 3:20 PM Kamil Paral wrote:
>
>> This proposal intends to reduce the scope of the “*Default application
>> functionality*” release criterion [0]:
>>
>> All applications that can be launched using the standard graphical
>>
On Mon, Feb 17, 2020 at 3:20 PM Kamil Paral wrote:
> This proposal intends to reduce the scope of the “*Default application
> functionality*” release criterion [0]:
>
> All applications that can be launched using the standard graphical
>> mechanism of a release-blocking desktop after a default in
On Mon, Feb 24, 2020 at 7:19 PM Geoffrey Marr wrote:
> >
> > *= Proposal =*
> >
> > Change the criterion to something along these lines:
> >
> > All applications that can be launched using the standard graphical
> >
> > As you can see, the original criterion was kept for Fedora’s flagship
> > des
> This proposal intends to reduce the scope of the “*Default application
> functionality*” release criterion [0]:
>
> All applications that can be launched using the standard graphical
>
> *= Background =*
>
> The area which QA is responsible for has been growing and growing in recent
> years. W
On Mon, Feb 17, 2020 at 3:20 PM Kamil Paral wrote:
> Change the criterion to something along these lines:
>
>> All applications that can be launched using the standard graphical
>> mechanism after a default installation of Fedora Workstation on x86_64
>> architecture must start successfully and w
is email have subject "proposal: Default application
functionality criterion reduction"? It that an accident, or is there some
reason behind it? Can we please do not reply to this thread any further, so
that it doesn't confuse people who want to read and reply to the actual
proposal (
In the test list at:
https://fedoraproject.org/wiki/Test_Results:Fedora_32_Branched_20200212.n.1_Desktop
There are 27 rows of things to test on between 1 and five platforms.
Even given that much of the testing is automated. You still need test
engineers to keep that all updated, running, and c
This proposal intends to reduce the scope of the “*Default application
functionality*” release criterion [0]:
All applications that can be launched using the standard graphical
> mechanism of a release-blocking desktop after a default installation of
> that desktop must start successfully and with
20 matches
Mail list logo
