On Thu, Mar 15, 2018 at 5:49 PM, Matthias Clasen <mclasen@xxxxxxxxxx> wrote:
I don't know what to think here. Is this thread a demonstration of QA not paying attention? If you feel that there's an area where we're not paying enough attention, why don't you talk to us?I disagree. This was not quickly committed without thinking, and I think that is a somewhat insulting thing to say.
It wasn't meant to be insulting, but you also cut my sentence short. The other part was "or testing it in a real-world usage for some time". I honestly believed that none of the core developers who decided about this change had auto-suspend enabled, because otherwise the inhibitor bug [1] would be considered a blocker for that change. But different people have different opinions and priorities, and maybe you're running with auto-suspend enabled, and maybe don't mind auto-suspending after having watched a TV episode and think it's not a problem. That's exactly why I reached out to this list.
I don't personally need to know your opinions on this. You (the SIG) decide what feature to put it, what to leave out, whether to re-evaluate it. I'm simply notifying you of a potentially annoying issue for our userbase. I wouldn't want to hear in the future that QA missed this.
[1] https://bugzilla.gnome.org/show_bug.cgi?id=705942
I don't personally need to know your opinions on this. You (the SIG) decide what feature to put it, what to leave out, whether to re-evaluate it. I'm simply notifying you of a potentially annoying issue for our userbase. I wouldn't want to hear in the future that QA missed this.
[1] https://bugzilla.gnome.org/show_bug.cgi?id=705942
Why do you list a long thing of things that need to work anyway, since wehave a suspend option in the UI for users to turn on. Do you seriously thinkwe just ignore all these things because the option was off by default ?
I don't know, that's why I asked. Do they all work?
My assumption is that the apps developers didn't need to care much about suspend, because it was off by default. When manually suspending, the user makes sure no important task gets cancelled or jeopardised (downloading a file, running a dnf operation). Surely there is a small percentage of users who turned autosuspend on, but many of those might feel like "I know what I'm doing, and if some task gets aborted due to autosuspend, it's my fault, because this was off by default". With autosuspend suddenly on by default, the perception changes - the system now should guarantee everything works fine, because it's the default setting. At least that's my understanding, you probably have a different one.
If turning suspend on by default is what it takes to get qa to pay attention,then so be it. Lets turn it on...
More importantly, is this feature being turned on in order to "get QA attention", or to improve the experience for our users?
_______________________________________________ desktop mailing list -- desktop@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to desktop-leave@xxxxxxxxxxxxxxxxxxxxxxx
