English Spanish
There are also some other reasons why installing automatic updates without testing may be a bad idea. A few such reasons are:
The need to back up your configuration files before an update. Even the best package spec files can have mistakes. If you have modified a file which is not flagged as a configuration file, then you might lose your configuration changes. Or an update may have a different format of configuration file, requiring a manual reconfiguration. It is often best to back up your configuration files before doing updates on critical packages such as mail, web, or database server packages.
The main advantage of automating the updates is that machines are likely to get updated more quickly, more often, and more uniformly than if the updates are done manually. We see too many compromised machines on the internet which would have been safe if the latest updates where installed in a timely way.
The machine is not critical and occasional unplanned downtime is acceptable.
systemctl list-timers dnf-*
systemctl enable --now dnf-automatic.timer 
sudo dnf install auter
So while you should still be cautious with any automated update solution, in particular on production systems, it is definitely worth considering, at least in some situations.
Some things which might make your machine be a bad candidate for automatic updates are:
Some things which might make your machine a good candidate for automatic updates are:
Scheduling updates
Run dnf-automatic
Reasons FOR using automatic updates
Reasons AGAINST using automatic updates
Other methods of protection
Once you are finished with the configuration, execute:
On a fresh install of Fedora 22 with default options, the dnf-automatic RPM is not installed. The first command below installs this RPM:
# Name of the host to connect to to send email messages.
email_host = localhost
# List of addresses to send messages to.
email_to = root