On Tue, Apr 7, 2020 at 12:35 PM Lukas Ruzicka <lruzi...@redhat.com> wrote:
> Hello friends, > yesterday, during the Blocker Review Meeting we decided to suggest a > blocking criterion for suspending the system, because it would clarify the > situations where to accept a blocker like the one from yesterday > https://bugzilla.redhat.com/show_bug.cgi?id=1816621. > Some of our team, me included, believe that it should be an *independent* > criterion (not part of Login, Reboot, Power Off) and it should be targeted > to *Final*. > > This is the suggestion of the criterion, please comment if you like to > patch it or have other suggestions, too. > > ==== Criterion ==== > Suspend to RAM > > Suspending the machine must work using the standard console commands and > the mechanisms offered by all release-blocking desktops. > > Work? > The machine must be able to suspend, keeping the current state of all > running applications and the operating system itself. When awoken, > everything must be restored to its original state. Suspend must work > repetitiously. > The problem with this is how do you answer the question on which hardware? Suspend is very hardware dependent and even to the point of what devices are plugged into it could affect it's ability to suspend. So would that be just a requirement for suspend work on a VM, or a particular set of hardware? Peter
_______________________________________________ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@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
