On 02/28/2014 06:53 PM, Tim wrote:
On 01/03/14 11:23, Erick Brunzell
wrote:
On 02/28/2014 05:48 PM, Tim wrote:
On 28/02/14 20:55, Erick Brunzell
wrote:
On 02/28/2014 01:28 AM,
Ali/amjjawad wrote:
I would respectfully disagree. With a six month release
cycle and a nine month support cycle I'd very much
appreciate some help testing the 'release-upgrader'
properly. Properly is a key word, eg;
I agree with Lance here... and wonder here did the whole
"fresh install" obsession for linux come from? the debian
packaging system is generally very good at handling upgrades!
While the milestone testing is largely about testing the
images, we also need to test upgrades. If there are bugs that
only occur after upgrading, we still need to know about them!
To upgrade Ubuntu GNOME Saucy to Ubuntu GNOME Trusty Beta 1
simply execute the command "update-manager -d" in the
terminal. No sudo is required, nor is it preferred!
To upgrade Ubuntu GNOME Saucy to Ubuntu GNOME Trusty Daily
simply execute the command "update-manager -d -c" in the
terminal. Again no sudo is required, nor is it preferred!
I don't think its actually possible to upgrade to "Beta 1"
using update-manager, both those commands will actually do the
same thing, and upgrade you to Trusty Daily.
You know I'm going to have to install Ubuntu GNOME Saucy and
check this out now.
"-c" checks for an actual release, so:
on Saucy it will do nothing
on Raring it will find "Saucy"
on Precise it will find "Quantal"
I'm anal like that, must know, that's how I roll ;^)
Lance
You're right - I was wrong.
I should have just linked the QA Tracker test-case:
http://iso.qa.ubuntu.com/qatracker/testcases/1310/info
There it calls for using "update-manager -d -c" for testing
purposes, and I'd love to see more people testing both those
standard upgrade tests as well as the "Upgrade (image)" tests.
The more testers we have the more likely we are to produce a super
sweet final release.
Lance
|