On 01/28/2015 09:41 AM, Matthias Clasen wrote:
On Wed, 2015-01-28 at 07:51 -0500, Kamil Paral wrote:
Hello,
we're discussing a release criterion which is tightly related to GNOME and KDE environments. Could your teams please provide some feedback on the proposed criterion update, see below? Is user switching something you believe should be working (and in which milestone?), or should we rather de-emphasize/remove that function?
Please respond to the test@ list, if possible, to avoid fragmenting the discussion.
Thanks!
----- Original Message -----
Hello,
yesterday we have discussed whether user switching should be included in our
criteria. We agreed that Beta is a good target for it, and accepted this bug
as a blocker:
https://bugzilla.redhat.com/show_bug.cgi?id=1184933
https://bugzilla.gnome.org/show_bug.cgi?id=719418
Now we need to adjust this criterion:
https://fedoraproject.org/wiki/Fedora_22_Beta_Release_Criteria#Shutdown.2C_reboot.2C_logout
Shutting down, logging out and rebooting must work using standard console
commands and the mechanisms offered (if any) by all release-blocking
desktops.
Work? [hide]
Similar to the Alpha criterion for shutting down, shutdown and reboot
mechanisms must take storage volumes down cleanly and correctly request a
shutdown or reboot from the system firmware. Logging out must return the
user to the environment from which they logged in, working as expected.
I propose this change:
title: Shutdown, reboot, logout, switch
Shutting down, rebooting, logging out and user switching must work using
standard console commands and the mechanisms offered (if any) by all
release-blocking desktops.
Work? [hide]
Similar to the Alpha criterion for shutting down, shutdown and reboot
mechanisms must take storage volumes down cleanly and correctly request a
shutdown or reboot from the system firmware. Logging out must return the
user to the environment from which they logged in, working as expected. User
switching must allow multiple users to perform live switching between their
sessions, working as expected.
What do you think?
I think user switching is much less important than the other things on
your list (login, shutdown, reboot) - if user switching is broken, the
majority of our users won't even notice because they are on single-user
systems.
Testing it is fine of course, but I don't really think we should block
on this. Also worth considering: user switching has never worked 100%
reliably, so increased qa focus may just uncover old heisenbugs, and
turn them into blocking issues.
I use user switching frequently on my in-law's laptop. What is not
reliable about it?
_______________________________________________
kde mailing list
kde@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/kde
New to KDE4? - get help from http://userbase.kde.org
begin:vcard
fn:Patrick Boutilier
n:Boutilier;Patrick
org:;Nova Scotia Department of Education
adr:;;2021 Brunswick Street;Halifax;NS;B3K 2Y5;Canada
email;internet:boutilpj@xxxxxxxxxxx
title:WAN Communications Specialist
tel;work:902-424-6800
tel;fax:902-424-0874
version:2.1
end:vcard
_______________________________________________
kde mailing list
kde@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/kde
New to KDE4? - get help from http://userbase.kde.org
