On Tue, May 12, 2020 at 5:56 PM Adam Williamson <adamwill@xxxxxxxxxxxxxxxxx> wrote:
I think we don't need the weasel form in this criterion as we actually
do want to block on user switching *fully working*. So I think I'd
agree with Lukas (and Brandon) that this can be changed to "perform",
but keeping the reference to conditional violations if you like - but
I'd change the link to this part of the blocker bug FAQ:
https://fedoraproject.org/wiki/Blocker_Bug_FAQ#What_about_hardware_and_local_configuration_dependent_issues.3F
which is what we usually use as the target for such references.
Thanks, Adam. That link is much better, and I'm happy to follow your advice on wording as you're our number one criterion lawyer ;-)
Here's an updated criterion proposal. I marked adjusted parts with an asterisk.
~~~~~~~~~~~~~~~~~~~~~
User switching
User switching must work using the mechanisms offered (if any) by all release-blocking desktops in their default configuration.
What is user switching?
User switching is a process of changing the currently presented desktop session between concurrent sessions of two or more different users. The user sessions keep running in the background, and users can switch between them repeatedly without losing any running application state.
For the purpose of this criterion, user switching doesn't include switching between different sessions of the *same* user.
Work?
The switching mechanism must correctly perform* the requested operation. If the operation doesn't succeed* on a subset of graphical drivers, the release blocking decision should be based on the number of affected users, the problem severity and available workarounds (as is our [standard procedure](Blocker_Bug_FAQ#What about hardware and local configuration dependent issues?)*).
Default configuration?*
This is supposed to cover only cases where the system hasn't been modified in a substantial (and relevant) way. This excludes cases where people e.g. install multiple desktop environments, replace their display manager for a different one, tweak relevant systemd settings, or install a non-default graphics driver.
~~~~~~~~~~~~~~~~~~~~~~
* denotes a change in wording
User switching
User switching must work using the mechanisms offered (if any) by all release-blocking desktops in their default configuration.
What is user switching?
User switching is a process of changing the currently presented desktop session between concurrent sessions of two or more different users. The user sessions keep running in the background, and users can switch between them repeatedly without losing any running application state.
For the purpose of this criterion, user switching doesn't include switching between different sessions of the *same* user.
Work?
The switching mechanism must correctly perform* the requested operation. If the operation doesn't succeed* on a subset of graphical drivers, the release blocking decision should be based on the number of affected users, the problem severity and available workarounds (as is our [standard procedure](Blocker_Bug_FAQ#What about hardware and local configuration dependent issues?)*).
Default configuration?*
This is supposed to cover only cases where the system hasn't been modified in a substantial (and relevant) way. This excludes cases where people e.g. install multiple desktop environments, replace their display manager for a different one, tweak relevant systemd settings, or install a non-default graphics driver.
~~~~~~~~~~~~~~~~~~~~~~
* denotes a change in wording
_______________________________________________ kde mailing list -- kde@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to kde-leave@xxxxxxxxxxxxxxxxxxxxxxx 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/kde@xxxxxxxxxxxxxxxxxxxxxxx
