Merge lp:~flocculant/xubuntu-docs/upgrade into lp:xubuntu-docs/xenial

Proposed by Kev Bowring
Status: Merged
Merged at revision: 530
Proposed branch: lp:~flocculant/xubuntu-docs/upgrade
Merge into: lp:xubuntu-docs/xenial
Diff against target: 80 lines (+22/-9)
1 file modified
contributor-docs/C/qa-testing.xml (+22/-9)
To merge this branch: bzr merge lp:~flocculant/xubuntu-docs/upgrade
Reviewer Review Type Date Requested Status
Pasi Lallinaho Pending
Review via email:

Description of the change

added section to qa-testing for upgrades

To post a comment you must log in.

Preview Diff

[H/L] Next/Prev Comment, [J/K] Next/Prev File, [N/P] Next/Prev Hunk
1=== modified file 'contributor-docs/C/qa-testing.xml'
2--- contributor-docs/C/qa-testing.xml 2015-11-22 14:44:04 +0000
3+++ contributor-docs/C/qa-testing.xml 2016-02-28 10:23:03 +0000
4@@ -1,5 +1,5 @@
5 <?xml version="1.0" encoding="UTF-8"?>
6-<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN"
7+<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN"
8 "" [
9 <!ENTITY % xubuntu-common SYSTEM "../../libs-common/xubuntu-common.ent">
10 %xubuntu-common;
11@@ -13,7 +13,7 @@
13 <chapter id="qa-testing">
14 <title>Package and ISO Testing</title>
17 <section id="qa-testing-exploratory">
18 <title>Exploratory Testing</title>
20@@ -30,13 +30,13 @@
21 <title>Using Development PPAs</title>
23 <para>We have 3 PPAs which we use regularly to test packages. These are:</para>
26 <itemizedlist>
27 <listitem><para>Shimmer Themes for daily builds of the Shimmer Project’s projects</para></listitem>
28 <listitem><para>Xubuntu Staging for packages and package versions that are being prepared for inclusion in Xubuntu</para></listitem>
29 <listitem><para>Xubuntu daily builds for daily Git and Bzr builds for packages related to Xubuntu and/or Xfce4</para></listitem>
30 </itemizedlist>
33 <para>Installing these three PPAs means that you will be using and testing packages that developers are currently working with, this means that regressions found by you will not be present once they are released.</para>
35 <para>At times it is useful to remove a PPA. Using ppa-purge causes apt to disable a PPA source list and then change affected packages back to the default versions.</para>
36@@ -48,18 +48,18 @@
38 <para>Reporting bugs with PPAs can be problematic, please see further information on reporting bugs with PPAs in <xref linkend="qa-bugs-ppa" />.</para>
39 </section>
42 <section id="qa-testing-static">
43 <title>Static Testing</title>
46 <para>Testing the development versions of Xubuntu and packages in it helps keep up the every day quality. If you have spare hardware resources or are able to run a virtualized testing environment, you can help.</para>
49 <itemizedlist>
50 <listitem><para>Check the devel mailing list close to the start of the cycle, where the decision as to which milestones we will participate in will be discussed.</para></listitem>
51 <listitem><para>While milestone testing is in progress, please watch for rebuilds. These will take place either when we have reason to rebuild, eg following a bug fix landing, or more likely when the Ubuntu Release Team have cause to do so.</para></listitem>
52 </itemizedlist>
53 </section>
56 <section id="qa-testing-milestone">
57 <title>Milestone Testing</title>
59@@ -80,7 +80,20 @@
60 <listitem><para>Live Session: Boot with the image and ensure that basic application testing (open, close, saving etc.) passes.</para></listitem>
61 <listitem><para>Installation tests required pass. These test only the installation.</para></listitem>
62 </itemizedlist>
63- </section>
64+ </section>
66+ <section id="qa-testing-upgrade">
67+ <title>Upgrade Testing</title>
69+ <para>About half way through any development cycle (the Beta milestone(s)) we need to test upgrades from the previous release to the new development version. When the development version is intended to be the next LTS release, we need to test both upgrade paths - LTS to LTS and normal to LTS.
71+ <para>The iso tracker has a section for upgrade tests, this does not change daily, but runs from Friday to Friday. This enables us to test upgrades for a week rather than a day. During these tests it is preferred that the image used for testing is the one built on the first Friday, except where bugs (and a land of it's fix) are reported.</para>
73+ <itemizedlist>
74+ <listitem><para>Upgrade: tested using the update-manager</para></listitem>
75+ <listitem><para>Upgrade(Image): tested using the daily image</para></listitem>
76+ </itemizedlist>
79 <section id="qa-testing-package">
80 <title>Package Testing</title>


People subscribed via source and target branches