Related to a recently proposed blocker [1][2], I propose a new release criterion which would cover such cases. Here it is: ~~~~~~~~~~~~ The desktop environment must work correctly when displaying common application content - that includes regular application windows, video output, games and possibly other common content. Regular operations like windows close/resize/maximize/minimize/fullscreen (when supported/applicable), windows switching, using windows on virtual workspaces, and similar common operations must behave as expected. Footnote - "What does this cover?": A small number of misbehaving applications is not a violation of this criterion. The goal of this criterion is to ensure general functionality for different types of applications and their operations. An example of a violation would be e.g. if a significant number of QT applications couldn't be resized (but they should be), or if all Java applications failed to display any content. ~~~~~~~~~~~~~ I think this criterion could target F38 Beta Release Criteria [3] or Basic Release Criteria [4]. Please tell me your thoughts, thanks! Kamil [1] https://pagure.io/fedora-qa/blocker-review/issue/1102 [2] https://bugzilla.redhat.com/show_bug.cgi?id=2178167 [3] https://fedoraproject.org/wiki/Fedora_38_Beta_Release_Criteria [4] https://fedoraproject.org/wiki/Basic_Release_Criteria

On Fri, Mar 17, 2023 at 5:48 AM Kamil Paral <kparal(a)redhat.com&gt; wrote: > > The desktop environment must work correctly when displaying common application content - that includes regular application windows, video output, games and possibly other common content. Regular operations like windows close/resize/maximize/minimize/fullscreen (when supported/applicable), windows switching, using windows on virtual workspaces, and similar common operations must behave as expected. Thinking like an editor for a moment, this feels a little redundant in places. I agree with the general concept, so this is entirely a presentation issue and I will not push back if you disagree. :But how about something more like: The desktop environment must perform regular operations like windows close/resize/maximize/minimize/fullscreen (when supported/applicable), windows switching, using windows on virtual workspaces, and similar common operations as expected. Common application content such as regular application windows, video output, and games must be displayed correctly. > Footnote - "What does this cover?": > A small number of misbehaving applications is not a violation of this criterion. The goal of this criterion is to ensure general functionality for different types of applications and their operations. An example of a violation would be e.g. if a significant number of QT applications couldn't be resized (but they should be), or if all Java applications failed to display any content. I'd also add something that makes it clear if it's the application not displaying the content correctly, that's out of scope for this criterion. I can't think of a good way to phrase that. But I wouldn't want someone to think Joe's Fancy Pew Pew Pew Game having a glitchy display would violate this. > I think this criterion could target F38 Beta Release Criteria [3] or Basic Release Criteria [4]. Definitely Basic for the same reason as Neal gave. -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis _______________________________________________ test mailing list -- test(a)lists.fedoraproject.org To unsubscribe send an email to test-leave(a)lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue

On 3/22/23 03:57, Kamil Paral wrote: > Here's a second draft. I took feedback here and also from the QA meeting > [1]. The split between the milestones makes this harder to read and > compare. If you have better ideas on how to do it, please tell me :-) > The only suggestion I have is for the foot notes under Final. Combine the second note into the first.

Here's a second draft. I took feedback here and also from the QA meeting [1]. The split between the milestones makes this harder to read and compare. If you have better ideas on how to do it, please tell me :-) ~~~~~~~~~~~~ == Basic milestone == For each release-blocking desktop, the desktop environment must perform regular operations like windows close/resize/maximize/minimize/fullscreen (when supported/applicable), windows switching, and similar common operations as expected. Common application content such as regular application windows, video output, and games must be displayed correctly. In this milestone, only pre-installed applications are considered. Footnote - "What does this cover?": The goal of this criterion is to ensure general desktop-related functionality for different types of applications. A small number of non-working applications (caused by applications themselves or the desktop environment) is not a violation of this criterion. == Final milestone == For each release-blocking desktop, the desktop environment must perform regular operations like windows close/resize/maximize/minimize/fullscreen (when supported/applicable), windows switching, using windows on virtual workspaces, and similar common operations as expected. Common application content such as regular application windows, video output, and games must be displayed correctly. Footnote - "What does this cover?": The goal of this criterion is to ensure general desktop-related functionality for different types of applications. A small number of non-working applications (caused by applications themselves or the desktop environment) is not a violation of this criterion. An example of a violation would be e.g. if a significant number of QT applications couldn't be resized (but they should be), or if all Java applications failed to display any content. Footnote - "Difference from the Basic criterion?": Compared to the similar [Basic criterion](link), this covers all applications (including third-party ones), not just pre-installed ones. More window operations are required to work, e.g. the explicitly-stated virtual workspaces workflows. ~~~~~~~~~~~~ [1] https://meetbot.fedoraproject.org/fedora-meeting/2023-03-20/fedora-qa.202...

On Mon, Apr 3, 2023 at 5:34 PM Kamil Paral <kparal(a)redhat.com&gt; wrote: > At today's QA meeting, nobody had any further objections. If there's no > additional feedback, I'll push it live tomorrow. > This is now live: https://fedoraproject.org/w/index.php?title=Basic_Release_Criteria&ty... https://fedoraproject.org/w/index.php?title=Fedora_38_Final_Release_Crite...

On Tue, Apr 4, 2023 at 6:05 PM Adam Williamson <adamwill(a)fedoraproject.org&gt; wrote: > On Tue, 2023-04-04 at 15:21 +0200, Kamil Paral wrote: > > On Mon, Apr 3, 2023 at 5:34 PM Kamil Paral <kparal(a)redhat.com&gt; wrote: > > > > > At today's QA meeting, nobody had any further objections. If there's no > > > additional feedback, I'll push it live tomorrow. > > > > > > > This is now live: > > > https://fedoraproject.org/w/index.php?title=Basic_Release_Criteria&ty... > > > https://fedoraproject.org/w/index.php?title=Fedora_38_Final_Release_Crite... > > Thanks! > > Do you plan to write a test case? > Never propose a criterion, kids, you'll get even more work :-) There: https://fedoraproject.org/wiki/QA:Testcase_window_manager https://fedoraproject.org/w/index.php?title=Template%3ADesktop_test_matri...