I just updated, "proposed" updates disabled. It looks like I'm now in too:
I'm not so much in a rush about updates, and I won't go overboard in the bleeding edge PPA's and packages. But I do think Canonical knows that the "rolling release" model has gotten popular enough in the linux community that they might make the development branch stabler. The success of my theory will be if my computer survives this release cycle from start to finish.Quote:
~$ cat /etc/os-release
VERSION="13.10, Saucy Salamander"
PRETTY_NAME="Ubuntu Saucy Salamander (development branch)"
I felt that the rolling release model is the most daunting - but very idealized - model in the linux world. Many linux users desire this model to point that they use Arch and other distros regardless of the hours they have to maintain them. If Canonical really thinks they can make their development release better and stabler than those alternatives, this cycle will be judgment of that. Don't get me wrong though - I'm still here to test this new release nonetheless.
Just my thoughts...
All this saucy talk has got me all of a dither. Before I knew it I was entering those 3 commands. I just could not help it. I don't know what came over me. :)
i plan to test the first Milestone Mainline Kernel that comes out for Saucy as well.
And I did NOT say, "read your schedule"! I said, "Look at the release notes", which indicates that the toolchain comes up May 2nd followed by, "Look at your calendar", meaning that it's not yet May 2nd.
But if some of you want to be deluded thinking you're using an early Saucy just knock yourselves out. OTOH I'd ask what you were doing when a few of us were sweating blood testing the final iso images and upgrades?