The Fedora distribution is often on the cutting-edge of technology and a test bed for new features. One change in the distribution's development branch which has stirred up debate among testers is an experimental feature which causes a suspended computer to automatically switch into hibernation mode after three hours. The feature is designed to save battery power, but introduces increased risk of data loss and will make computers wake up more slowly. LWN reports: "The addition of this feature to Fedora came about in two steps. The first was addition of a suspend-to-hibernate command (later renamed suspend-then-hibernate) to systemd. The GNOME developers noticed this feature, and added a patch to automatically use it, instead of ordinary suspend, when it is available. Since GNOME chose to start using this feature, and since GNOME provides the control interface that users see, it seems natural to think that GNOME's interface should provide control over whether suspend-then-hibernate is used. But, it appears, the GNOME developers disagree with that idea. In particular, two GNOME developers, Bastien Nocera and Clasen, argued that if this particular systemd feature does not work reliably, it should be disabled in systemd rather than in GNOME. Neither seems to see any other reason why users might want to disable its use or have any control over it in general." Kamil Paral and Adam Williamson have posted comments on situations where using a suspend-then-hibernate feature could cause problems for users. At the time of writing, it is unclear whether Fedora will adopt the feature in a future stable release.