<html>
<head>
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
</head>
<body bgcolor="#FFFFFF" text="#000000">
And we're off ... <br>
<br>
<b><u>Package Testing</u></b><br>
<br>
Let's start with changes I've made to the Package tracker. [1]<br>
<br>
When you visit the tracker now you will see there's a different set
of lists from last time.<br>
<br>
Regarding the two Optional groups at top - I'll not be doing much in
the way of calling for these 2 groups as a whole, if you're using
one of the packages and have time to run the test (in 14.10) -
please do so and report. <br>
<br>
So that's the first call for <u>Optionals</u> - I'll maybe do
another towards the end of the cycle. I'll maybe move something into
a different tes suite if it needs specific testing.<br>
<br>
Which leaves the much reduced mandatory groups - 4 of them.<br>
<br>
I'll give you the 'calendar' for those calls now, but will be
following along with calls as and when they're required.<br>
<br>
<blockquote>
<blockquote><b>Xubuntu A - May 19th</b><b><br>
</b><b>Xubuntu B - June 9th</b><b><br>
</b><b>Xubuntu C - June 30th</b><b><br>
</b><b>Xubuntu D - August 11th</b><br>
</blockquote>
</blockquote>
<br>
This gives us space for the milestone image testing and a gap at
cycle end which we can use for specific testing. The schedule for
milestones can be found here [2] - that's not be finalised at the
moment, but I doubt much will change with that, it will certainly be
final long before a call from me.<br>
<br>
<b><u>Image Testing</u></b><br>
<br>
Not much to say or that could be said - the images still need
testing as always, the Daily tests can be found here [3]<br>
<br>
Milestone image testing will as always take place when it's
required, typically I will let you know once the url for the
testpage is either published, or I've brow beaten someone into
telling me it early :)<br>
<br>
<u><b>Testing PPAs</b></u><br>
<br>
Just a fyi - we are looking at creating 2 'team' PPA for people to
use to test bug fixes for us and one for new landing apps/packages.
This should enable us to get better testing of these things. Calls
for that, and more information about them, will happen - again - as
and when. If you're interested in covering that I would suggest
using a virtual machine that you can leave with the PPAs in place. <br>
<br>
Finally - I would urge people, that are able to, to use 14.10 daily
- when you are using an application - check the testcase, if what
you've been doing covers, or more than covers it - then report it :)
The more reports we get the better. Obviously, if you've been using
something and have found a bug - report it.<br>
<br>
As always - <u><b>only reported results count</b></u> - and if
you've seen the blog post [4] recapping what we did in the last
cycle, you'll see that not only do they count for us - but I do in
fact count them ;) <br>
<br>
As an extra reward, though I'm sure you don't need more than knowing
that you helped the Xubuntu community - you'll get named :)<br>
<br>
Elfy<br>
<br>
<br>
[1] <a class="moz-txt-link-freetext"
href="http://packages.qa.ubuntu.com/qatracker/milestones/316/builds/67147/testcases">http://packages.qa.ubuntu.com/qatracker/milestones/316/builds/67147/testcases</a><br>
[2] <a class="moz-txt-link-freetext"
href="https://wiki.ubuntu.com/UtopicUnicorn/ReleaseSchedule">https://wiki.ubuntu.com/UtopicUnicorn/ReleaseSchedule</a><br>
[3] <a class="moz-txt-link-freetext" href="http://iso.qa.ubuntu.com/qatracker/milestones/315/builds">http://iso.qa.ubuntu.com/qatracker/milestones/315/builds</a><br>
[4] <a class="moz-txt-link-freetext"
href="http://xubuntu.org/news/xubuntu-14-04-qa-recap/">http://xubuntu.org/news/xubuntu-14-04-qa-recap/</a><br>
<pre class="moz-signature" cols="72">--
Ubuntu Forum Council Member
Xubuntu QA Lead</pre>
</body>
</html>