<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Now that we have usable iso's we can start making moves on testing.<br>
<br>
This cycle we will be testing iso's - of course - but we will be
pushing that to testers less frequently. At the moment, that is
likely to happen at milestones or when we need something specific
testing affecting the iso.<br>
<br>
<blockquote>
<blockquote>
<blockquote>
<blockquote>
<blockquote><big><big><b> This cycle the focus will be on
packages. </b></big></big><br>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<br>
So, to deal with the simplest part first, the tracker [1]<br>
<br>
That is now set up with 3 sections:<br>
<br>
<ul>
<li>Xubuntu LTS A Priority : packages that we will be asking to be
tested often <br>
</li>
</ul>
<ul>
<li>Xubuntu LTS Mandatory : packages that we will be asking to be
tested less often, but more often than </li>
</ul>
<ul>
<li>Xubuntu LTS Run Once/Optional : which are set at run-once or
optional</li>
</ul>
<p><br>
Mails will be sent to the -devel mailing list as normal for those
calls, in addition developers will also be calling, as
appropriate, for testing of packages when fixes are landing -
often these will need you to enable one of our PPAs. Of course
there is no need to wait for a mail from us to test them ;)<br>
</p>
<p>There is a section on our website [2] which deals with PPAs and
much more beside.<br>
</p>
<p>You can add the ppa to xenial and wily and be using the package
the developer is close to releasing.<br>
</p>
<p>This early in the cycle it isn't quite so easy to run the dev
version as your daily machine, but certainly by mid-cycle we get
very little breakage. Though during the last cycle I don't
remember one instance where I was left with an unusable
installation and I run a day or two after the last dev gets
released.<br>
</p>
<p>Given that we are leading up to the next LTS we're particularly
looking, in addition to normal bugs, for <i>usability</i> bugs.
So if you daily use something and think that, for example<br>
</p>
<ul>
<li>That icon looks odd amongst the others</li>
</ul>
<ul>
<li>The way I have to use this breaks my workflow</li>
</ul>
<ul>
<li>Why doesn't this do that instead? <br>
</li>
</ul>
<p>Please report them, we do read bug reports - it might get marked
Won't Fix, Opinion - but the important thing is that it's been
thought of and acted on. <br>
</p>
<blockquote>
<p><i>We do want people, where it is at all possible, to run the
dev version somehow, be that with a dual-boot or a vm (where
you can snapshot) as much as you can. But a </i><i><u>very
useful</u></i><i> second place goes to running wily with the
3 development PPAs, in fact the majority of the development
work will be done on wily. </i> </p>
</blockquote>
<p>We are looking forward to releasing another well tested Long Term
Support [3] release.<br>
</p>
<br>
[1]
<a class="moz-txt-link-freetext"
href="http://packages.qa.ubuntu.com/qatracker/milestones/350/builds/105268/testcases">http://packages.qa.ubuntu.com/qatracker/milestones/350/builds/105268/testcases</a><br>
[2] <a class="moz-txt-link-freetext"
href="http://xubuntu.org/contribute/qa/">http://xubuntu.org/contribute/qa/</a><br>
[3] <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>
</body>
</html>