[ubuntu-studio-devel] 14.10 Release Candidate Testing in progress
Kaj Ailomaa
zequence at mousike.me
Fri Oct 17 16:42:13 UTC 2014
Hello fellow Ubuntu Studio enthusiasts and developers.
If you'd like to join in testing the final release candidate, and learn
how it's done, please follow these guidelines:
* First off, if you have any kind of question, big or small, or get
stuck - don't hesitate to write to this mail list, or contact us at our
IRC channel #ubuntustudio-devel at irc.freenode.net
(https://help.ubuntu.com/community/UbuntuStudio/IRC) - please be aware
that you may need to wait several hours for an answer on either.
* Make sure to have a launchpad account, as you'll need it when
reporting results from the tests as well as reporting bugs. If you
don't have an account, head to http://launchpad.net and create one.
* Current builds of all 14.10 RC Utopic ISOs can be found here
http://iso.qa.ubuntu.com/qatracker/milestones/325/builds. Ubuntu Studio
has two ISOs, 32 and 64 bits. Click on each to to see the test cases.
* Each ISO has three tests. This is one for the amd64 ISO
http://iso.qa.ubuntu.com/qatracker/milestones/325/builds/82016/testcases/1300/results
(all remaining pointer refer to this page). Follow the link "Detailed
information on the testcase" to read more about performing the test.
* If you found a bug, create a bug report in launchpad. - You can do
that from the terminal in the live session you are running with the
terminal command: ubuntu-bug <packagename>. Replace <packagename> with
the package you are reporting the bug against. (For reference, the name
of the package for the installer is "ubiquity").
* If you were able to complete a test, with or without bugs, mark it
"passed". If the test failed, mark it "failed". In any case, if there
were bugs, add the bug numbers under "bugs" or "critical bugs" (a
criticial bug is something similar to not being able to boot a system -
in other words, something really serious).
* Does this seem as much - yes, it probably is if you are new to this.
But, once you get a hang of it, it takes no time at all and is a great
way to get introduced to some of the infrastructure we use for our
development process, so please do dig in.
That's all. Again, if you have any questions, please write.
/Kaj Ailomaa - Ubuntu Studio Project LEad
More information about the ubuntu-studio-devel
mailing list