[ubuntu-studio-devel] Ubuntu Studio Trusty (LTS) ISO Testing
retail at the-gammons.net
Sun Feb 14 18:10:28 UTC 2016
As threatened yesterday, 14.04.4 is due to be released, most probably on
Thu, 18 Feb 2016.
If you would like to participate in testing 14.04.4, this is what you
need to do:
# Get a Launchpad account
Get yourself a launchpad account, if you haven't already, at
Q: Why do I need it?
A: without it you won't be able to mark a test done.
# Head to the QA testing website
Then, head to the website for reporting test results, at
http://iso.qa.ubuntu.com and login in order to be able to do any
reporting. You will see which releases are currently being tested there,
as they will have the status "testing" (scroll to the bottom of the
Follow the link for Trusty 14.04.4, and you will find two ISO builds for
Ubuntu Studio 14.04.4.
Each build has its own download information and test cases.
# Download the ISO
To download and test an ISO, click on the download information link, and
download using any of the methods available (zsync is the most
practical, since you may need to update a previously downloaded ISO, and
zsync only downloads what was changed - not the whole ISO).
To use zsync, first install it (in a terminal):
sudo apt-get install zsync
Then, to download an ISO, use this command for the 64bit version (also,
in a terminal):
# Completing a test case
Either complete only one, or all three test cases for each build (this
is entirely up to you).
To complete a test case, follow the instructions for it (like this one,
for the amd64 image
If you were able to complete the test, mark it done
If the test was not possible to complete, due to a serious bug, mark the
Also, add the numbers for any bugs you encountered during the test.
# Reporting bugs
Bug reporting may be time consuming, especially for beginners, so please
have patience. If you ever do want to help developing Ubuntu Studio in
any way in the future, you will need to learn how to make use of this
fundamental part of software development.
If you found a bug of any kind, please report them while still in the
session where you encountered it, if possible.
If you are at a total loss, you may do a simpler bug report at the
Ubuntu Studio LP page https://bugs.launchpad.net/ubuntustudio/+filebug.
Else, use the Ubuntu terminal tool, ubuntu-bug.
It may difficult to know which package to blame for the bug, but do your
best guess, and in a terminal, use the command (replace <packagename>
with the name of the package):
# Any Questions?
Don't hesitate to ask them. Either on this list, or on our IRC channel,
#ubuntustudio-devel at freenode.net.
How to use IRC - https://help.ubuntu.com/community/UbuntuStudio/IRC.
Ross - Ubuntu Studio Testing lead
More information about the ubuntu-studio-devel