However in looking up the description of what "rolling releases" actually means on wikipedia, I'm now more educated on the subject. a rolling release or rolling update development model refers to a continually developing software system; this is instead of a standard release development model which uses software versions that must be reinstalled over the previous version.
(See Specifying package names for more information) If the packages or globs specified match to packages which are not currently installed then update will not install them.
update operates on groups, files, provides and filelists just like the "install" command.
You can click the notification to launch the GNOME Software app. Choose the tab in GNOME Software and you should see a window like this: If you don’t see anything on this screen, try using the reload tool at the top left.
It may take some time after release for all systems to be able to see an upgrade available. You can continue working until you reach a stopping point, and the download is complete.
Generally, when going to a new version, I'll generally do a full re-install of the system.
I have found updating packages in place to be quite problematic and the amount of time spent in debugging the problems there are more complex than doing a reinstall. Now, the message has disappeared, and I cannot find it, not any software it might have been connected with. None of the Red Hat distros prior to Fedora 17 included the ability to do dist-upgrades as you've asked. I dismissed it, as the only option it had presented me with was "Install updates", and I wasn't quite sure what would that do.Rolling release = no versions, packages are just dumped into the distro from the upstream ASAP, right? The level of testing that would go into a package being placed in one of these branches is less stringent than say when a package shows up as an update in a true "rolling release" distro such as Arch Linux (would be my expectation).So Debian is the complete opposite of a rolling release, Ubuntu as well. Here's the section of the wikipedia page that covers the use of development branches for standard release distros: The distinction between rolling release software distributions and development branches of standard release software distributions is often overlooked by users inexperienced with rolling distributions.Additionally having maintained RHEL, Fedora & Cent OS systems for over the past decade, I would never even consider using this method for anything. So typically people would do one of the following: Use the Rawhide release, which is the bleeding edge version, similar to how Sid is in Debian.