<html> <head> <meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type"> </head> <body text="#000000" bgcolor="#FFFFFF"> Elfy, The test cases documented a) Execute `update-manager -d -c` from a terminal (<a href="http://iso.qa.ubuntu.com/qatracker/testcases/1310/info">http://iso.qa.ubuntu.com/qatracker/testcases/1310/info</a>) b) ISO-based upgrade (<a href="http://iso.qa.ubuntu.com/qatracker/testcases/1498/info">http://iso.qa.ubuntu.com/qatracker/testcases/1498/info</a>) apply to at least 4 distinct upgrade scenarios: 1. 12.04 occupies a full HDD or SSD. 2. 12.04 is dual-booted with Windows. (Dual-booting and Windows should still function as before after the upgrade of 12.04 to 14.04) 3. 12.04 is dual booted with another Linux distribution (E.g. fedora). (Dual-booting and the other Linux should still function as before after the upgrade of 12.04 to 14.04) 4. 12.04 is dual booted with Unix (E.g. netbsd). (Dual-booting and Unix should still function as before after the upgrade of 12.04 to 14.04) #1 is probably the most common scenario. #2 is unique because of the requirement to coexist with the Microsoft boot-loader. #3 and #4 are different from #1 because of potential boot-loader and grub version differences (potential conflicts). NOTE: I left out Android because the probability of someone dual-booting Android (Linux kernel but yet another boot-loader scenario) and Xubuntu 12.04 at the moment is not significant. Other opinions? However, next time (16.04?) could be a different matter. #2 can be set-up by downloading a legal evaluation copy of Windows 8.1 from here: <a href="http://technet.microsoft.com/en-us/evalcenter/default">http://technet.microsoft.com/en-us/evalcenter/default</a> Note that you will be prompted my Microsoft to login or register if you are not already logged in. Registering is legally cost-free. Please do not use illegal bitorrent methodologies. I'll do all 4x2=8 cases as soon as all of my "day jobs" permit, in the above priority order (other opinions about order?). I am downloading W-oink as I type. Someone else PLEASE do as much as possible of the same as I my test-rig is still an Intel-abandoned Intel CedarTrail/PowerVR motherboard (D2550MUD2). Yes, I am going to get rid of it during 1Q2014 since nothing fully makes use of the hardware including Windows. Still kicking myself for poor research 12 months ago! (-: Richard <a href="https://launchpad.net/%7Etexadactyl">https://launchpad.net/~texadactyl</a> <div class="moz-cite-prefix">On 01/29/2014 06:11 AM, Elfy wrote: </div> <blockquote cite="mid:52E8EFD5.1000207@btinternet.com" type="cite"> <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1"> <div id="selectable">In a few months time we will be releasing 14.04 Trusty Tahr LTS. Up to now we have been concentrating on package and image testing for Trusty. Now, we need to start running upgrade tests, most importantly the LTS to LTS upgrades (from 12.04 to 14.04) and as usual, the regular upgrades (from 13.10 to 14.04). Testcases are present for both 64 and 32 bit at <blockquote> <blockquote><a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://iso.qa.ubuntu.com/qatracker/milestones/308/builds/57247/testcases">http://iso.qa.ubuntu.com/qatracker/milestones/308/builds/57247/testcases</a> <a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://iso.qa.ubuntu.com/qatracker/milestones/308/builds/57248/testcases">http://iso.qa.ubuntu.com/qatracker/milestones/308/builds/57248/testcases</a> </blockquote> </blockquote> As there is no specific testcase available at present for the LTS to LTS upgrade - please use the comment area of the tracker report to note which type of upgrade you tested - LTS or non-LTS It would be infinitely better to be have upgrades tested with real data, but at worst tests via Virtual Machines will check the basic upgrade path. <big>NOTE: If you are testing with real data, please make backups first!</big> regards Elfy </div> <pre class="moz-signature" cols="72">-- Ubuntu Forum Council Member Xubuntu QA Lead</pre> <fieldset class="mimeAttachmentHeader"></fieldset> </blockquote> </body> </html>