Merge lp:~alourie/ubuntu-qa-website/fix_bug_663124 into lp:~ubuntu-qa-website-devel/ubuntu-qa-website/trunk

Proposed by Alex Lourie on 2010-10-19
Status: Rejected
Rejected by: Nicholas Skaggs on 2014-05-07
Proposed branch: lp:~alourie/ubuntu-qa-website/fix_bug_663124
Merge into: lp:~ubuntu-qa-website-devel/ubuntu-qa-website/trunk
Diff against target: 813 lines (+809/-0)
1 file modified
pages.xml (+809/-0)
To merge this branch: bzr merge lp:~alourie/ubuntu-qa-website/fix_bug_663124
Reviewer Review Type Date Requested Status
Ara Pulido (community) 2010-10-19 Disapprove on 2010-10-19
Review via email: mp+38806@code.launchpad.net

Description of the change

This fixes the LP bug 663124

To post a comment you must log in.
Ara Pulido (ara) wrote :

Alex, thanks for suggestion. The bug report is correct, I agree that pages shouldn't

But this change should be made in the theme, and not the content. If we change the content to do that, and then we add a new page, it will add the comments for that page.

I have to reject this change, but feel free to propose a merge to the theme that solves this issue.

Thanks!

review: Disapprove

Unmerged revisions

2. By Alex Lourie on 2010-10-19

Removing comments under static pages

1. By Ara Pulido on 2010-10-14

First commit

Preview Diff

[H/L] Next/Prev Comment, [J/K] Next/Prev File, [N/P] Next/Prev Hunk
1=== added file 'pages.xml'
2--- pages.xml 1970-01-01 00:00:00 +0000
3+++ pages.xml 2010-10-19 07:32:46 +0000
4@@ -0,0 +1,809 @@
5+<?xml version="1.0" encoding="UTF-8"?>
6+<!-- This is a WordPress eXtended RSS file generated by WordPress as an export of your blog. -->
7+<!-- It contains information about your blog's posts, comments, and categories. -->
8+<!-- You may use this file to transfer that content from one site to another. -->
9+<!-- This file is not intended to serve as a complete backup of your blog. -->
10+
11+<!-- To import this information into a WordPress blog follow these steps. -->
12+<!-- 1. Log in to that blog as an administrator. -->
13+<!-- 2. Go to Tools: Import in the blog's admin panels (or Manage: Import in older versions of WordPress). -->
14+<!-- 3. Choose "WordPress" from the list. -->
15+<!-- 4. Upload this file using the form provided on that page. -->
16+<!-- 5. You will first be asked to map the authors in this export file to users -->
17+<!-- on the blog. For each author, you may choose to map to an -->
18+<!-- existing user on the blog or to create a new user -->
19+<!-- 6. WordPress will then import each of the posts, comments, and categories -->
20+<!-- contained in this file into your blog -->
21+
22+<!-- generator="WordPress/2.9.2" created="2010-10-14 14:41"-->
23+<rss version="2.0"
24+ xmlns:excerpt="http://wordpress.org/export/1.0/excerpt/"
25+ xmlns:content="http://purl.org/rss/1.0/modules/content/"
26+ xmlns:wfw="http://wellformedweb.org/CommentAPI/"
27+ xmlns:dc="http://purl.org/dc/elements/1.1/"
28+ xmlns:wp="http://wordpress.org/export/1.0/"
29+>
30+
31+<channel>
32+ <title>Ubuntu QA Website</title>
33+ <link>http://qa.ubuntu.com</link>
34+ <description>Blog about the QA activities around Ubuntu: bug triaging, testing and tools</description>
35+ <pubDate>Wed, 13 Oct 2010 11:42:24 +0000</pubDate>
36+ <generator>http://wordpress.org/?v=2.9.2</generator>
37+ <language>en</language>
38+ <wp:wxr_version>1.0</wp:wxr_version>
39+ <wp:base_site_url>http://qa.ubuntu.com</wp:base_site_url>
40+ <wp:base_blog_url>http://qa.ubuntu.com</wp:base_blog_url>
41+ <wp:category><wp:category_nicename>10-04</wp:category_nicename><wp:category_parent></wp:category_parent><wp:cat_name><![CDATA[10.04]]></wp:cat_name></wp:category>
42+ <wp:category><wp:category_nicename>advocacy</wp:category_nicename><wp:category_parent></wp:category_parent><wp:cat_name><![CDATA[advocacy]]></wp:cat_name></wp:category>
43+ <wp:category><wp:category_nicename>apple</wp:category_nicename><wp:category_parent></wp:category_parent><wp:cat_name><![CDATA[apple]]></wp:cat_name></wp:category>
44+ <wp:category><wp:category_nicename>big-bang-theory</wp:category_nicename><wp:category_parent></wp:category_parent><wp:cat_name><![CDATA[big bang theory]]></wp:cat_name></wp:category>
45+ <wp:category><wp:category_nicename>books</wp:category_nicename><wp:category_parent></wp:category_parent><wp:cat_name><![CDATA[books]]></wp:cat_name></wp:category>
46+ <wp:category><wp:category_nicename>browsing</wp:category_nicename><wp:category_parent></wp:category_parent><wp:cat_name><![CDATA[browsing]]></wp:cat_name></wp:category>
47+ <wp:category><wp:category_nicename>canonical</wp:category_nicename><wp:category_parent></wp:category_parent><wp:cat_name><![CDATA[canonical]]></wp:cat_name></wp:category>
48+ <wp:category><wp:category_nicename>commands</wp:category_nicename><wp:category_parent></wp:category_parent><wp:cat_name><![CDATA[commands]]></wp:cat_name></wp:category>
49+ <wp:category><wp:category_nicename>community</wp:category_nicename><wp:category_parent></wp:category_parent><wp:cat_name><![CDATA[community]]></wp:cat_name></wp:category>
50+ <wp:category><wp:category_nicename>dell</wp:category_nicename><wp:category_parent></wp:category_parent><wp:cat_name><![CDATA[dell]]></wp:cat_name></wp:category>
51+ <wp:category><wp:category_nicename>desktop</wp:category_nicename><wp:category_parent></wp:category_parent><wp:cat_name><![CDATA[desktop]]></wp:cat_name></wp:category>
52+ <wp:category><wp:category_nicename>desktop-testing</wp:category_nicename><wp:category_parent></wp:category_parent><wp:cat_name><![CDATA[desktop testing]]></wp:cat_name></wp:category>
53+ <wp:category><wp:category_nicename>developerweek</wp:category_nicename><wp:category_parent></wp:category_parent><wp:cat_name><![CDATA[developerweek]]></wp:cat_name></wp:category>
54+ <wp:category><wp:category_nicename>free-software</wp:category_nicename><wp:category_parent></wp:category_parent><wp:cat_name><![CDATA[free software]]></wp:cat_name></wp:category>
55+ <wp:category><wp:category_nicename>freescale</wp:category_nicename><wp:category_parent></wp:category_parent><wp:cat_name><![CDATA[freescale]]></wp:cat_name></wp:category>
56+ <wp:category><wp:category_nicename>funny</wp:category_nicename><wp:category_parent></wp:category_parent><wp:cat_name><![CDATA[Funny]]></wp:cat_name></wp:category>
57+ <wp:category><wp:category_nicename>gadgets</wp:category_nicename><wp:category_parent></wp:category_parent><wp:cat_name><![CDATA[gadgets]]></wp:cat_name></wp:category>
58+ <wp:category><wp:category_nicename>general</wp:category_nicename><wp:category_parent></wp:category_parent><wp:cat_name><![CDATA[General]]></wp:cat_name></wp:category>
59+ <wp:category><wp:category_nicename>globaljam</wp:category_nicename><wp:category_parent></wp:category_parent><wp:cat_name><![CDATA[globaljam]]></wp:cat_name></wp:category>
60+ <wp:category><wp:category_nicename>hardware</wp:category_nicename><wp:category_parent></wp:category_parent><wp:cat_name><![CDATA[hardware]]></wp:cat_name></wp:category>
61+ <wp:category><wp:category_nicename>hardy</wp:category_nicename><wp:category_parent></wp:category_parent><wp:cat_name><![CDATA[hardy]]></wp:cat_name></wp:category>
62+ <wp:category><wp:category_nicename>iso-testing</wp:category_nicename><wp:category_parent></wp:category_parent><wp:cat_name><![CDATA[iso testing]]></wp:cat_name></wp:category>
63+ <wp:category><wp:category_nicename>kids</wp:category_nicename><wp:category_parent></wp:category_parent><wp:cat_name><![CDATA[Kids]]></wp:cat_name></wp:category>
64+ <wp:category><wp:category_nicename>launchpad</wp:category_nicename><wp:category_parent></wp:category_parent><wp:cat_name><![CDATA[launchpad]]></wp:cat_name></wp:category>
65+ <wp:category><wp:category_nicename>ldtp</wp:category_nicename><wp:category_parent></wp:category_parent><wp:cat_name><![CDATA[ldtp]]></wp:cat_name></wp:category>
66+ <wp:category><wp:category_nicename>linux</wp:category_nicename><wp:category_parent></wp:category_parent><wp:cat_name><![CDATA[linux]]></wp:cat_name></wp:category>
67+ <wp:category><wp:category_nicename>listening</wp:category_nicename><wp:category_parent></wp:category_parent><wp:cat_name><![CDATA[listening]]></wp:cat_name></wp:category>
68+ <wp:category><wp:category_nicename>logiciel-libre</wp:category_nicename><wp:category_parent></wp:category_parent><wp:cat_name><![CDATA[logiciel libre]]></wp:cat_name></wp:category>
69+ <wp:category><wp:category_nicename>logitech</wp:category_nicename><wp:category_parent></wp:category_parent><wp:cat_name><![CDATA[logitech]]></wp:cat_name></wp:category>
70+ <wp:category><wp:category_nicename>lucid</wp:category_nicename><wp:category_parent></wp:category_parent><wp:cat_name><![CDATA[lucid]]></wp:cat_name></wp:category>
71+ <wp:category><wp:category_nicename>mago</wp:category_nicename><wp:category_parent></wp:category_parent><wp:cat_name><![CDATA[mago]]></wp:cat_name></wp:category>
72+ <wp:category><wp:category_nicename>monitoring</wp:category_nicename><wp:category_parent></wp:category_parent><wp:cat_name><![CDATA[monitoring]]></wp:cat_name></wp:category>
73+ <wp:category><wp:category_nicename>motu</wp:category_nicename><wp:category_parent></wp:category_parent><wp:cat_name><![CDATA[motu]]></wp:cat_name></wp:category>
74+ <wp:category><wp:category_nicename>multitouch</wp:category_nicename><wp:category_parent></wp:category_parent><wp:cat_name><![CDATA[multitouch]]></wp:cat_name></wp:category>
75+ <wp:category><wp:category_nicename>networking</wp:category_nicename><wp:category_parent></wp:category_parent><wp:cat_name><![CDATA[networking]]></wp:cat_name></wp:category>
76+ <wp:category><wp:category_nicename>opensource</wp:category_nicename><wp:category_parent></wp:category_parent><wp:cat_name><![CDATA[opensource]]></wp:cat_name></wp:category>
77+ <wp:category><wp:category_nicename>planet-ubuntu</wp:category_nicename><wp:category_parent></wp:category_parent><wp:cat_name><![CDATA[planet-ubuntu]]></wp:cat_name></wp:category>
78+ <wp:category><wp:category_nicename>qa</wp:category_nicename><wp:category_parent></wp:category_parent><wp:cat_name><![CDATA[QA]]></wp:cat_name></wp:category>
79+ <wp:category><wp:category_nicename>security</wp:category_nicename><wp:category_parent></wp:category_parent><wp:cat_name><![CDATA[security]]></wp:cat_name></wp:category>
80+ <wp:category><wp:category_nicename>setup</wp:category_nicename><wp:category_parent></wp:category_parent><wp:cat_name><![CDATA[setup]]></wp:cat_name></wp:category>
81+ <wp:category><wp:category_nicename>sql</wp:category_nicename><wp:category_parent></wp:category_parent><wp:cat_name><![CDATA[SQL]]></wp:cat_name></wp:category>
82+ <wp:category><wp:category_nicename>stable</wp:category_nicename><wp:category_parent></wp:category_parent><wp:cat_name><![CDATA[stable]]></wp:cat_name></wp:category>
83+ <wp:category><wp:category_nicename>stable-releases</wp:category_nicename><wp:category_parent></wp:category_parent><wp:cat_name><![CDATA[Stable Releases]]></wp:cat_name></wp:category>
84+ <wp:category><wp:category_nicename>testing</wp:category_nicename><wp:category_parent></wp:category_parent><wp:cat_name><![CDATA[Testing]]></wp:cat_name></wp:category>
85+ <wp:category><wp:category_nicename>twitter</wp:category_nicename><wp:category_parent></wp:category_parent><wp:cat_name><![CDATA[Twitter]]></wp:cat_name></wp:category>
86+ <wp:category><wp:category_nicename>ubiquity</wp:category_nicename><wp:category_parent></wp:category_parent><wp:cat_name><![CDATA[ubiquity]]></wp:cat_name></wp:category>
87+ <wp:category><wp:category_nicename>ubuntu</wp:category_nicename><wp:category_parent></wp:category_parent><wp:cat_name><![CDATA[ubuntu]]></wp:cat_name></wp:category>
88+ <wp:category><wp:category_nicename>ubuntu-testing</wp:category_nicename><wp:category_parent></wp:category_parent><wp:cat_name><![CDATA[ubuntu testing]]></wp:cat_name></wp:category>
89+ <wp:category><wp:category_nicename>ubuntu-testing-team</wp:category_nicename><wp:category_parent></wp:category_parent><wp:cat_name><![CDATA[ubuntu testing team]]></wp:cat_name></wp:category>
90+ <wp:category><wp:category_nicename>ubuntu-qc</wp:category_nicename><wp:category_parent></wp:category_parent><wp:cat_name><![CDATA[ubuntu-qc]]></wp:cat_name></wp:category>
91+ <wp:category><wp:category_nicename>uds</wp:category_nicename><wp:category_parent></wp:category_parent><wp:cat_name><![CDATA[uds]]></wp:cat_name></wp:category>
92+ <wp:category><wp:category_nicename>uncategorized</wp:category_nicename><wp:category_parent></wp:category_parent><wp:cat_name><![CDATA[Uncategorized]]></wp:cat_name></wp:category>
93+ <wp:category><wp:category_nicename>unity</wp:category_nicename><wp:category_parent></wp:category_parent><wp:cat_name><![CDATA[unity]]></wp:cat_name></wp:category>
94+ <wp:category><wp:category_nicename>upgrade</wp:category_nicename><wp:category_parent></wp:category_parent><wp:cat_name><![CDATA[upgrade]]></wp:cat_name></wp:category>
95+ <wp:category><wp:category_nicename>upstream</wp:category_nicename><wp:category_parent></wp:category_parent><wp:cat_name><![CDATA[upstream]]></wp:cat_name></wp:category>
96+ <wp:category><wp:category_nicename>uupc</wp:category_nicename><wp:category_parent></wp:category_parent><wp:cat_name><![CDATA[uupc]]></wp:cat_name></wp:category>
97+ <wp:category><wp:category_nicename>wilhelm</wp:category_nicename><wp:category_parent></wp:category_parent><wp:cat_name><![CDATA[Wilhelm]]></wp:cat_name></wp:category>
98+ <wp:category><wp:category_nicename>windows-integration</wp:category_nicename><wp:category_parent></wp:category_parent><wp:cat_name><![CDATA[Windows integration]]></wp:cat_name></wp:category>
99+ <wp:category><wp:category_nicename>zoho</wp:category_nicename><wp:category_parent></wp:category_parent><wp:cat_name><![CDATA[zoho]]></wp:cat_name></wp:category>
100+ <wp:tag><wp:tag_slug>bugs</wp:tag_slug><wp:tag_name><![CDATA[Bugs]]></wp:tag_name></wp:tag>
101+ <wp:tag><wp:tag_slug>kernel</wp:tag_slug><wp:tag_name><![CDATA[kernel]]></wp:tag_name></wp:tag>
102+ <wp:tag><wp:tag_slug>triage</wp:tag_slug><wp:tag_name><![CDATA[triage]]></wp:tag_name></wp:tag>
103+ <item>
104+<title>ISO Testing</title>
105+<link>http://qa.ubuntu.com/testing/iso-testing/</link>
106+<pubDate>Fri, 20 Aug 2010 14:49:00 +0000</pubDate>
107+<dc:creator><![CDATA[apulido]]></dc:creator>
108+
109+ <category><![CDATA[Uncategorized]]></category>
110+
111+ <category domain="category" nicename="uncategorized"><![CDATA[Uncategorized]]></category>
112+
113+<guid isPermaLink="false">https://newqa.ubunut.com/?page_id=4</guid>
114+<description></description>
115+<content:encoded><![CDATA[<strong>What’s ISO Testing?</strong>
116+
117+Ubuntu has a fixed 6-month release cycle, which means that every 6 months we have a new Ubuntu release, ready to install.
118+
119+The good thing about software fixed cycles is that you can schedule anything you want. In fact, for Ubuntu, we schedule just at the beginning of the cycle up to 7 development releases. You can check at the <a href="https://wiki.ubuntu.com/LucidReleaseSchedule/">Lucid Schedule</a> that there was an Alpha 1, Alpha 2, Alpha 3, Beta1, Beta2 and Final Release. Those milestones need to be tested properly, because we release CDs for people to test on their hardware, and we have to make sure that everything is more or less OK. (with “more or less” I mean that these milestones are still software in development, so you have to be careful, anyway).
120+
121+<strong>How do we track milestone testing?</strong>
122+
123+So, here it is how the tracker appears in the show. Milestone releases happen normally on Thursdays. On Monday, in scheduled milestone weeks, testers start looking at the tracker looking for the candidate images: the ISOs that might be announced as the "Karmic Alpha something". But these images need to be tested before they get announced.
124+
125+<strong>How is the test tracker structured?</strong>
126+
127+At Ubuntu, we produce builds for many different *buntu flavours. In the ISO Tracker we have a category for each of them. You can filter by category using the "Filter" menu in the bottom left of the page. That would allow you to concentrate in the flavour you want to test.
128+
129+[caption id="attachment_124" align="alignnone" width="194" caption="Filter by category"]<img class="size-full wp-image-124" title="Filter" src="http://ubuntutesting.wordpress.com/files/2009/09/filter.png" alt="Filter by category" width="194" height="409" />[/caption]
130+
131+Once you select a category, you will be able to select an image to download for that category. A category like "Kubuntu" may have different images: i386 Live CD, amd64 alternate, etc., and all of them need to be tested before releasing a milestone.
132+
133+[caption id="attachment_127" align="alignnone" width="499" caption="Kubuntu Karmic Alpha 6 images"]<img class="size-full wp-image-127" title="Kubuntu Karmic Alpha 6" src="http://ubuntutesting.wordpress.com/files/2009/09/kubuntualpha6.png" alt="Kubuntu Karmic Alpha 6 images" width="499" height="340" />[/caption]
134+
135+If you click now in any of those images, you will have access to a direct link of the ISO to download and a selection of tests that you may run for that image. For every test, there is a link to the test case description in the <a href="http://testcases.qa.ubuntu.com">test case wiki</a>. The test cases are easy to follow when running any of them.
136+
137+So, to sum up, every category contains a set of ISO images and every image contains at least one test case.
138+
139+[caption id="attachment_132" align="alignnone" width="500" caption="Iso Tracker structure"]<img class="size-full wp-image-132" title="iso_tracker_diagram" src="http://ubuntutesting.wordpress.com/files/2009/09/iso_tracker_diagram.png" alt="Iso Tracker structure" width="500" height="353" />[/caption]
140+
141+<strong>How do I help?</strong>
142+
143+As I wrote before, the week of the release of a milestone we need a lot of help testing the candidate images. If we want full coverage we need to run more than 150 test cases. If you have a spare machine or a virtual machine installed, you can help making Ubuntu better by running the untested test cases during the week of the release of a milestone.
144+
145+First thing, you will need an account in the ISO tracker. Unfortunately, your Launchpad Open ID won't work for this site (indeed something that needs to be improved). Click on "Log in" and fill the requested data. As the page explains, if you already have an account in <a href="http://brainstorm.ubuntu.com/">Ubuntu Brainstorm</a>, you can use it for the <a href="http://iso.qa.ubuntu.com">ISO Testing Tracker</a>.
146+
147+[caption id="attachment_135" align="alignnone" width="499" caption="Create a QA account"]<img class="size-full wp-image-135" title="create_account" src="http://ubuntutesting.wordpress.com/files/2009/09/create_account.png" alt="Create a QA account" width="499" height="505" />[/caption]
148+
149+Once you have an account just select the image you want to test, choose a test case for that image, start running the installation in a virtual machine or a spare machine and report any bugs you may find in Launchpad.
150+
151+Once finished, you have to report back in the <a href="http://iso.qa.ubuntu.com">ISO Testing Tracker</a>. Click on the test case you have run and report Pass/Fail depending on your success. You can also add the bug numbers of the bugs you found. They will be linked to the Launchpad bug and it will help the release team to track them.
152+
153+[caption id="attachment_138" align="alignnone" width="500" caption="Please, report back!"]<img class="size-full wp-image-138" title="submit" src="http://ubuntutesting.wordpress.com/files/2009/09/submit.png" alt="Please, report back!" width="500" height="585" />[/caption]
154+
155+<strong>Screencast</strong>
156+<div id="ISOTracker"><object classid="clsid:d27cdb6e-ae6d-11cf-96b8-444553540000" width="100%" height="100" codebase="http://download.macromedia.com/pub/shockwave/cabs/flash/swflash.cab#version=6,0,40,0"><param name="src" value="http://blip.tv/play/ge9BgaK2CAA" /><param name="allowfullscreen" value="true" /><embed type="application/x-shockwave-flash" width="100%" height="100" src="http://blip.tv/play/ge9BgaK2CAA" allowfullscreen="true"> </embed></object></div>]]></content:encoded>
157+<excerpt:encoded><![CDATA[]]></excerpt:encoded>
158+<wp:post_id>4</wp:post_id>
159+<wp:post_date>2010-08-20 14:49:00</wp:post_date>
160+<wp:post_date_gmt>2010-08-20 14:49:00</wp:post_date_gmt>
161+<wp:comment_status>closed</wp:comment_status>
162+<wp:ping_status>open</wp:ping_status>
163+<wp:post_name>iso-testing</wp:post_name>
164+<wp:status>publish</wp:status>
165+<wp:post_parent>19</wp:post_parent>
166+<wp:menu_order>0</wp:menu_order>
167+<wp:post_type>page</wp:post_type>
168+<wp:post_password></wp:post_password>
169+<wp:is_sticky>0</wp:is_sticky>
170+<wp:postmeta>
171+<wp:meta_key>_edit_lock</wp:meta_key>
172+<wp:meta_value>1285794879</wp:meta_value>
173+</wp:postmeta>
174+<wp:postmeta>
175+<wp:meta_key>_edit_last</wp:meta_key>
176+<wp:meta_value>20</wp:meta_value>
177+</wp:postmeta>
178+<wp:postmeta>
179+<wp:meta_key>_wp_page_template</wp:meta_key>
180+<wp:meta_value>default</wp:meta_value>
181+</wp:postmeta>
182+<wp:comment>
183+<wp:comment_id>2</wp:comment_id>
184+<wp:comment_author><![CDATA[Maverick Release Candidate Testing &laquo; Marjo Mercado&#39;s Blog]]></wp:comment_author>
185+<wp:comment_author_email></wp:comment_author_email>
186+<wp:comment_author_url>http://marjomercado.wordpress.com/2010/09/27/maverick-release-candidate-testing/</wp:comment_author_url>
187+<wp:comment_author_IP>66.135.48.209</wp:comment_author_IP>
188+<wp:comment_date>2010-09-27 17:27:52</wp:comment_date>
189+<wp:comment_date_gmt>2010-09-27 17:27:52</wp:comment_date_gmt>
190+<wp:comment_content><![CDATA[[...] If you would like more information about ISO testing is, you can review the documentation at: http://qa.ubuntu.com/testing/iso-testing/ [...] ]]></wp:comment_content>
191+<wp:comment_approved>1</wp:comment_approved>
192+<wp:comment_type>pingback</wp:comment_type>
193+<wp:comment_parent>0</wp:comment_parent>
194+<wp:comment_user_id>0</wp:comment_user_id>
195+</wp:comment>
196+ </item>
197+<item>
198+<title>Desktop Testing Program</title>
199+<link>http://qa.ubuntu.com/testing/desktop-testing-program/</link>
200+<pubDate>Fri, 20 Aug 2010 14:58:38 +0000</pubDate>
201+<dc:creator><![CDATA[apulido]]></dc:creator>
202+
203+ <category><![CDATA[Uncategorized]]></category>
204+
205+ <category domain="category" nicename="uncategorized"><![CDATA[Uncategorized]]></category>
206+
207+<guid isPermaLink="false">https://newqa.ubunut.com/?page_id=15</guid>
208+<description></description>
209+<content:encoded><![CDATA[For every milestone of the development release of Ubuntu, we will be providing a series of testcases for you to run in that milestone. As soon as the milestone is officially released, you will be able to complete the tests in the following two weeks (although we encourage you to run them as soon as possible, to allow enough time to developers to fix the bugs).
210+
211+One of the good things about this program is that you, as testers, will be able to know every time what to test, you will be able to check the new features before anybody else, and you will gain experience on the Ubuntu development process. Also, there will be a mailing list to share your experiences, bugs and to have direct feedback from the developers.
212+<h2 id="Setting Up Instructions">Setting Up Instructions</h2>
213+<ol type="1">
214+ <li>You have to have an account in our tracking system. We are going to use it to generate data (it will be publicly available).
215+<ol type="1">
216+ <li>Go to <a href="http://desktop.qa.ubuntu.com/">http://desktop.qa.ubuntu.com</a>.</li>
217+ <li>Click on "Log In" and "Create New Account"</li>
218+</ol>
219+</li>
220+ <li>Once you're done with the tracker, add yourself to the <a href="https://launchpad.net/%7Edesktop-testing-team">Desktop Testing Team</a> in Launchpad and subscribe to the mailing list.</li>
221+ <li>Send an email to the mailing list introducing yourself.</li>
222+ <li>You're all set!</li>
223+</ol>
224+<h2 id="Testing Instructions">Testing Instructions</h2>
225+Every milestone (see <a href="https://wiki.ubuntu.com/Testing/DesktopTestingProgram#Calendar">Calendar</a>), we will be starting a new testing cycle. The tests will appear in the tracker and everybody is free to submit their results any time during the following two weeks. The following milestone a new cycle will start, and results will be fresh again.
226+
227+Every week, you will see the tracker (<a href="http://desktop.qa.ubuntu.com/">http://desktop.qa.ubuntu.com</a>) reset. You need to click on an application to see the list of testcases:
228+
229+<img title="applications.png" src="https://wiki.ubuntu.com/Testing/DesktopTestingProgram?action=AttachFile&amp;do=get&amp;target=applications.png" alt="applications.png" />
230+
231+The list of testcases appear, with a summary on how many results have been reported:
232+
233+<img title="list.png" src="https://wiki.ubuntu.com/Testing/DesktopTestingProgram?action=AttachFile&amp;do=get&amp;target=list.png" alt="list.png" />
234+
235+To read the instructions on how to perform the testing, and report your result, click on any of them. The testcase view will show a form to report your result and a link to the testcase wiki, to guide you through the process:
236+
237+<img title="testcase.png" src="https://wiki.ubuntu.com/Testing/DesktopTestingProgram?action=AttachFile&amp;do=get&amp;target=testcase.png" alt="testcase.png" />]]></content:encoded>
238+<excerpt:encoded><![CDATA[]]></excerpt:encoded>
239+<wp:post_id>15</wp:post_id>
240+<wp:post_date>2010-08-20 14:58:38</wp:post_date>
241+<wp:post_date_gmt>2010-08-20 14:58:38</wp:post_date_gmt>
242+<wp:comment_status>closed</wp:comment_status>
243+<wp:ping_status>open</wp:ping_status>
244+<wp:post_name>desktop-testing-program</wp:post_name>
245+<wp:status>publish</wp:status>
246+<wp:post_parent>19</wp:post_parent>
247+<wp:menu_order>0</wp:menu_order>
248+<wp:post_type>page</wp:post_type>
249+<wp:post_password></wp:post_password>
250+<wp:is_sticky>0</wp:is_sticky>
251+<wp:postmeta>
252+<wp:meta_key>_edit_lock</wp:meta_key>
253+<wp:meta_value>1284460158</wp:meta_value>
254+</wp:postmeta>
255+<wp:postmeta>
256+<wp:meta_key>_edit_last</wp:meta_key>
257+<wp:meta_value>2</wp:meta_value>
258+</wp:postmeta>
259+<wp:postmeta>
260+<wp:meta_key>_wp_page_template</wp:meta_key>
261+<wp:meta_value>default</wp:meta_value>
262+</wp:postmeta>
263+ </item>
264+<item>
265+<title>Testing</title>
266+<link>http://qa.ubuntu.com/testing/</link>
267+<pubDate>Mon, 23 Aug 2010 09:35:26 +0000</pubDate>
268+<dc:creator><![CDATA[apulido]]></dc:creator>
269+
270+ <category><![CDATA[Uncategorized]]></category>
271+
272+ <category domain="category" nicename="uncategorized"><![CDATA[Uncategorized]]></category>
273+
274+<guid isPermaLink="false">https://newqa.ubunut.com/?page_id=19</guid>
275+<description></description>
276+<content:encoded><![CDATA[<h3>We cannot leave quality to good luck. We cannot rely in having millions of users who will find bugs as they use the applications. Our users want to use the software, not to find bugs and report them. FOSS projects in general and Ubuntu in particular need a new way of rethinking testing as a skilled activity (communication skills, technical writing skills, software architecture knowledge, a critical mindset...) and an opportunity to contribute to the project.</h3>
277+<h4>Open Projects</h4>
278+If you want to start helping, these are the open testing projects:
279+<ul>
280+ <li><a href="http://qa.ubuntu.com/testing/desktop-testing-program/">Desktop Testing Program</a>. Test your favourite desktop applications and file useful bugs.</li>
281+ <li><a href="http://qa.ubuntu.com/testing/iso-testing/">ISO Testing</a>. Every Ubuntu milestone needs to be tested to check that it installs correctly in every flavour and every installation option.</li>
282+ <li><a href="http://qa.ubuntu.com/testing/multitouch-testing/">Multitouch Testing</a>. Do you have MT hardware? Help us testing it to make it work with Ubuntu!</li>
283+</ul>
284+<h4>Regular Activities</h4>
285+Once you have started testing Ubuntu and know the basics, you can start with more regular activities, that require some commitment with the Ubuntu QA team.
286+<ul>
287+ <li><strong>Stable Release Update (SRU) Testing</strong></li>
288+</ul>
289+<p style="padding-left: 30px;">All <a href="https://wiki.ubuntu.com/StableReleaseUpdates">stable release updates</a> are first uploaded to the <em>Proposed</em> repository before they are released live. An important principle behind Ubuntu is that we should never make a working system worse; stable release updates need to be extensively tested to make sure that there are no regressions.</p>
290+<p style="padding-left: 30px;">If you are interested in this kind of testing, there is a public Launchpad <a href="https://launchpad.net/%7Esru-verification">SRU verification</a> team that you can join as well as a <a href="https://wiki.ubuntu.com/QATeam/PerformingSRUVerification">fantastic wiki page</a> with helpful tools for finding bugs to work on.</p>
291+
292+<ul>
293+ <li><strong>General Testing</strong></li>
294+</ul>
295+<p style="padding-left: 30px;">Ubuntu is more than its default installation and basic tasks - it's an entire repository of software and possible configurations. We need to test as much of it as possible, and some things aren't well covered by established test cases and procedures. General testing is as simple as attempting to use the development release and reporting whatever problems you run into.</p>
296+
297+<ul>
298+ <li><strong>Laptop Testing</strong></li>
299+</ul>
300+<p style="padding-left: 30px;">Laptop Testing is about the manual testing of specific things (<em>test cases</em>) mainly related to laptops hardware, using milestone releases of the development version (alphas, betas and release candidates). The goal is to get Ubuntu to work great on as many different makes and models of laptops as possible and this can be done knowing which hardware works straight off the install CD and which hardware needs configuring or is poorly supported.</p>
301+<p style="padding-left: 30px;">If you are interested in this kind of testing, head to the <a href="https://wiki.ubuntu.com/Testing/Laptop">https://wiki.ubuntu.com/Testing/Laptop</a> Wiki page.</p>
302+
303+<h4 id="Bugs">Bugs</h4>
304+Any bugs found during testing should be filed in Launchpad. Please refer to <a href="https://wiki.ubuntu.com/ReportingBugs">ReportingBugs</a> and <a href="https://wiki.ubuntu.com/DebuggingProcedures">DebuggingProcedures</a> for guidance on filing useful bug reports. During validation testing we also check that previously fixed bugs on <a href="https://wiki.ubuntu.com/Testing/FixesToVerify">Testing/FixesToVerify</a> are indeed fixed and have not resurfaced.
305+
306+It is especially important that Bugs found in the development release be <a href="https://wiki.ubuntu.com/Bugs/Upstream">upstreamed</a> so that their upstream authors can see them. Often we are using the latest, unmodified alpha code for various projects during the development release, so the odds of it being fixed are much greater if they can be reported to the upstream developers making the changes.]]></content:encoded>
307+<excerpt:encoded><![CDATA[]]></excerpt:encoded>
308+<wp:post_id>19</wp:post_id>
309+<wp:post_date>2010-08-23 09:35:26</wp:post_date>
310+<wp:post_date_gmt>2010-08-23 09:35:26</wp:post_date_gmt>
311+<wp:comment_status>closed</wp:comment_status>
312+<wp:ping_status>open</wp:ping_status>
313+<wp:post_name>testing</wp:post_name>
314+<wp:status>publish</wp:status>
315+<wp:post_parent>0</wp:post_parent>
316+<wp:menu_order>0</wp:menu_order>
317+<wp:post_type>page</wp:post_type>
318+<wp:post_password></wp:post_password>
319+<wp:is_sticky>0</wp:is_sticky>
320+<wp:postmeta>
321+<wp:meta_key>_edit_lock</wp:meta_key>
322+<wp:meta_value>1285088234</wp:meta_value>
323+</wp:postmeta>
324+<wp:postmeta>
325+<wp:meta_key>_edit_last</wp:meta_key>
326+<wp:meta_value>2</wp:meta_value>
327+</wp:postmeta>
328+<wp:postmeta>
329+<wp:meta_key>_wp_page_template</wp:meta_key>
330+<wp:meta_value>default</wp:meta_value>
331+</wp:postmeta>
332+ </item>
333+<item>
334+<title>Multitouch Testing</title>
335+<link>http://qa.ubuntu.com/testing/multitouch-testing/</link>
336+<pubDate>Mon, 30 Aug 2010 11:46:14 +0000</pubDate>
337+<dc:creator><![CDATA[apulido]]></dc:creator>
338+
339+ <category><![CDATA[Uncategorized]]></category>
340+
341+ <category domain="category" nicename="uncategorized"><![CDATA[Uncategorized]]></category>
342+
343+<guid isPermaLink="false">https://newqa.ubunut.com/?page_id=89</guid>
344+<description></description>
345+<content:encoded><![CDATA[As <a href="http://www.markshuttleworth.com/archives/455">announced</a>, gestures with multitouch are landing in Maverick with the utouch stack. We need to fully test the MT environment with different hardware and also check if the changes have introduce any regressions in the X input system.
346+
347+If you have MT device we are looking forward to get your feedback. Even, if you have any input device (mouse, trackpad, tablet...) we are also gathering results for those, to track possible regressions.
348+<h3 id="Setting Up Instructions">Setting Up Instructions</h3>
349+<ol type="1">
350+ <li>You have to have an account in our tracking system.
351+<ol type="1">
352+ <li>Go to <a href="http://multitouch.qa.ubuntu.com/">http://multitouch.qa.ubuntu.com</a>.</li>
353+ <li>Click on "Log In" and "Create New Account"</li>
354+</ol>
355+</li>
356+ <li>Once you're done with the tracker, subscribe the <a href="https://launchpad.net/%7Emulti-touch-dev">Ubuntu Multitouch dev mailing list</a>, where you will be able to contact the developers in case you face any problem.</li>
357+ <li>If you want, send an email to the mailing list introducing yourself.</li>
358+ <li>You're all set!</li>
359+</ol>
360+<h3>Testing Instructions</h3>
361+We will be announcing new testing cycles in the mailing list. The tests will appear in the tracker and everybody is free to submit their results any time, while the testing cycle is opened.
362+
363+Every testing cycle, you will see the tracker (<a href="http://multitouch.qa.ubuntu.com/">http://multitouch.qa.ubuntu.com</a>) reset. You need to click on a set of testcases to see the list:
364+
365+<img title="applications.png" src="https://wiki.ubuntu.com/Multitouch/Testing/Tracker?action=AttachFile&amp;do=get&amp;target=applications.png" alt="applications.png" />
366+
367+The list of testcases appear, with a summary on how many results have been reported:
368+
369+<img title="list.png" src="https://wiki.ubuntu.com/Multitouch/Testing/Tracker?action=AttachFile&amp;do=get&amp;target=list.png" alt="list.png" />
370+
371+To read the instructions on how to perform the testing, and report your result, click on any of them. The testcase view will show a form to report your result and a link to the testcase wiki, to guide you through the process.
372+<div>
373+<table>
374+<tbody>
375+<tr>
376+<td><img title="/!\" src="https://wiki.ubuntu.com/htdocs/ubuntu/img/alert.png" alt="/!\" width="15" height="15" /> <strong>Please note that the link "Additional instructions are available" is actually the link to the testcase description.</strong> This is a wrong wording of the link and we will fix it in the next roll out of the tracker.</td>
377+</tr>
378+</tbody>
379+</table>
380+</div>
381+<img title="testcase.png" src="https://wiki.ubuntu.com/Multitouch/Testing/Tracker?action=AttachFile&amp;do=get&amp;target=testcase.png" alt="testcase.png" />
382+
383+If the testcase passed, just mark it as passed.
384+<h3 id="Filing bugs">Filing bugs</h3>
385+Utouch packages come with <a href="https://wiki.ubuntu.com/Apport">Apport</a> hooks, that will make it easy to file bugs with the relevant information for the developers. To file a new bug please, open a terminal window and type:
386+<pre>$ ubuntu-bug utouch</pre>
387+After the relevant information has been collected, it will be sent to Launchpad, where you will be able to describe your problem. As easy as that! You have to love Apport!
388+
389+You can also point to bugs that have been already reported.]]></content:encoded>
390+<excerpt:encoded><![CDATA[]]></excerpt:encoded>
391+<wp:post_id>89</wp:post_id>
392+<wp:post_date>2010-08-30 11:46:14</wp:post_date>
393+<wp:post_date_gmt>2010-08-30 11:46:14</wp:post_date_gmt>
394+<wp:comment_status>closed</wp:comment_status>
395+<wp:ping_status>open</wp:ping_status>
396+<wp:post_name>multitouch-testing</wp:post_name>
397+<wp:status>publish</wp:status>
398+<wp:post_parent>19</wp:post_parent>
399+<wp:menu_order>0</wp:menu_order>
400+<wp:post_type>page</wp:post_type>
401+<wp:post_password></wp:post_password>
402+<wp:is_sticky>0</wp:is_sticky>
403+<wp:postmeta>
404+<wp:meta_key>_edit_lock</wp:meta_key>
405+<wp:meta_value>1285060160</wp:meta_value>
406+</wp:postmeta>
407+<wp:postmeta>
408+<wp:meta_key>_edit_last</wp:meta_key>
409+<wp:meta_value>2</wp:meta_value>
410+</wp:postmeta>
411+ </item>
412+<item>
413+<title>Reports</title>
414+<link>http://qa.ubuntu.com/report-list/</link>
415+<pubDate>Wed, 08 Sep 2010 10:37:01 +0000</pubDate>
416+<dc:creator><![CDATA[apulido]]></dc:creator>
417+
418+ <category><![CDATA[Uncategorized]]></category>
419+
420+ <category domain="category" nicename="uncategorized"><![CDATA[Uncategorized]]></category>
421+
422+<guid isPermaLink="false">https://newqa.ubunut.com/?page_id=136</guid>
423+<description></description>
424+<content:encoded><![CDATA[<h3>Ubuntu is a huge project and sometimes is difficult to get the right information for each situation. Luckily, there are a lot of reports that can help you finding what you're looking for.</h3>
425+<h4><a href="http://qa.ubuntu.com/reports/ogasawara/weatherreport.html">Weather Report</a></h4>
426+<p style="padding-left: 30px;">The Weather Report is like the landing page for useful information about the development release. You can get the high and critical bugs, the differences between the latest ISOs and the archive, the uninstallable packages and much more information.</p>
427+
428+<h4><a href="http://status.qa.ubuntu.com/">Packages Status</a></h4>
429+<p style="padding-left: 30px;">Package status pages are intended to help package maintainers, developers, and other interested parties measure the current state of a package. Selecting the package you are interested in, you will get bug statistics for that package, including graphs. This is a very interesting way to start working on a particular package.</p>
430+
431+<h4><a href="http://people.canonical.com/~ubuntu-archive/pending-sru.html">Pending SRU</a></h4>
432+<p style="padding-left: 30px;">The list for <a href="https://wiki.ubuntu.com/StableReleaseUpdates">Stable Release Updates</a> that require testing. These are bugs in the stable release that are candidates for getting fixed in -updates. The fixes need to be tested before they reach the major audience. Help us testing them!</p>
433+
434+<h4>Upgrade Automated Testing</h4>
435+<p style="padding-left: 30px;">As you know, upgrades from one release to the next one is a very error-prone activity and it requires a lot of testing. Michael Vogt maintains some automated tests for upgrades:</p>
436+
437+<ul>
438+ <li> <a href="http://people.canonical.com/~mvo/automatic-upgrade-testing/current/">From release to release</a>: This report contains the results of automated testing of upgrades of different flavours between two releases.</li>
439+ <li><a href="http://people.canonical.com/~mvo/automatic-upgrade-testing/current-stable/">From stable to -updates</a>: This report contains the results of upgrading the stable release CD to the contents of the -updates repository.</li>
440+</ul>
441+<h4>Launchpad Data Reports</h4>
442+<p style="padding-left: 30px;">We all know that Launchpad contains a lot of useful information. Some times we think that it has so much information we can hardly find anything useful. Untrue. There are a lot of useful reports based on Launchpad data that will help you finding the information you were looking for:<a href="http://qa.ubuntu.com/reports/launchpad-database/bugs-with-branches.html"></a></p>
443+
444+<ul>
445+ <li><a href="http://qa.ubuntu.com/reports/launchpad-database/bugs-with-branches.html">Bugs with branches:</a> These bug reports have a branch attached to them.</li>
446+ <li><a href="http://qa.ubuntu.com/reports/launchpad-database/bugs-with-most-duplicates.html">Bugs with most duplicates:</a> Ubuntu bug reports with the greatest number of duplicates.</li>
447+ <li><a href="http://qa.ubuntu.com/reports/launchpad-database/bugs-with-most-users-affected.html">Bugs with most users affected:</a> Ubuntu bugs with highest user affected count (at least 5).</li>
448+ <li><a href="http://qa.ubuntu.com/reports/launchpad-database/bugs-with-unmarked-patches.html">Bugs with unmarked patches:</a> Open bugs with possible patches attached that are not flagged (attachments with diff or patch on them).</li>
449+ <li><a href="http://qa.ubuntu.com/reports/launchpad-database/oldest-confirmed-ubuntu-bug-tasks.html">Oldest Confirmed Ubuntu bug tasks: </a>The 25 oldest bug tasks with status: Confirmed.</li>
450+ <li><a href="http://qa.ubuntu.com/reports/launchpad-database/oldest-fix-committed-ubuntu-bug-tasks.html">Oldest Fix Committed Ubuntu bug tasks:</a> The 25 oldest bug tasks with status: Fix Committed.</li>
451+ <li><a href="http://qa.ubuntu.com/reports/launchpad-database/oldest-in-progress-ubuntu-bug-tasks.html">Oldest In Progress Ubuntu bug tasks</a>: The 25 oldest bug tasks with status: In Progress.</li>
452+ <li><a href="http://qa.ubuntu.com/reports/launchpad-database/oldest-incomplete-ubuntu-bug-tasks.html">Oldest Incomplete Ubuntu bug tasks</a>: The 25 oldest bug tasks with status: Incomplete.</li>
453+ <li><a href="http://qa.ubuntu.com/reports/launchpad-database/oldest-new-ubuntu-bug-tasks.html">Oldest New Ubuntu bug tasks:</a> The 25 oldest bug tasks with status: New.</li>
454+ <li><a href="http://qa.ubuntu.com/reports/launchpad-database/oldest-triaged-ubuntu-bug-tasks.html">Oldest Triaged Ubuntu bug tasks:</a> The 25 oldest bug tasks with status: Triaged.</li>
455+ <li><a href="http://qa.ubuntu.com/reports/launchpad-database/open-bugs-with-inactive-milestones.html">Open bugs with inactive milestones:</a> Bugs that are open, but targeted to a milestone that already passed.</li>
456+ <li><a href="http://qa.ubuntu.com/reports/launchpad-database/private-apport-crashes.html">Private Apport crashes:</a> Apport crashes that are still private.</li>
457+ <li><a href="http://qa.ubuntu.com/reports/launchpad-database/unfixed-bugs-with-patches.html">Unfixed bugs with patches:</a> Open bugs with attachments flagged as patches.</li>
458+ <li><a href="http://qa.ubuntu.com/reports/launchpad-database/unlinked-bugwatch.html">Unlinked Bugwatch:</a> Bugs that need a bug watch.</li>
459+</ul>
460+<h4><a href="http://qa.ubuntuwire.org/ftbfs/">FTBFS</a></h4>
461+<ul></ul>
462+<p style="padding-left: 30px;">Sometimes packages fail to build due to change on the dependencies or unmaintained packages. In this report you can see what packages are failing to build and why.</p>]]></content:encoded>
463+<excerpt:encoded><![CDATA[]]></excerpt:encoded>
464+<wp:post_id>136</wp:post_id>
465+<wp:post_date>2010-09-08 10:37:01</wp:post_date>
466+<wp:post_date_gmt>2010-09-08 10:37:01</wp:post_date_gmt>
467+<wp:comment_status>closed</wp:comment_status>
468+<wp:ping_status>open</wp:ping_status>
469+<wp:post_name>report-list</wp:post_name>
470+<wp:status>publish</wp:status>
471+<wp:post_parent>0</wp:post_parent>
472+<wp:menu_order>0</wp:menu_order>
473+<wp:post_type>page</wp:post_type>
474+<wp:post_password></wp:post_password>
475+<wp:is_sticky>0</wp:is_sticky>
476+<wp:postmeta>
477+<wp:meta_key>_edit_lock</wp:meta_key>
478+<wp:meta_value>1285139630</wp:meta_value>
479+</wp:postmeta>
480+<wp:postmeta>
481+<wp:meta_key>_edit_last</wp:meta_key>
482+<wp:meta_value>2</wp:meta_value>
483+</wp:postmeta>
484+<wp:comment>
485+<wp:comment_id>3</wp:comment_id>
486+<wp:comment_author><![CDATA[111-222-1933email@address.tst]]></wp:comment_author>
487+<wp:comment_author_email>sample@email.tst</wp:comment_author_email>
488+<wp:comment_author_url>http://'</wp:comment_author_url>
489+<wp:comment_author_IP>188.50.84.71</wp:comment_author_IP>
490+<wp:comment_date>2010-10-09 07:03:01</wp:comment_date>
491+<wp:comment_date_gmt>2010-10-09 07:03:01</wp:comment_date_gmt>
492+<wp:comment_content><![CDATA[111-222-1933email@address.tst]]></wp:comment_content>
493+<wp:comment_approved>trash</wp:comment_approved>
494+<wp:comment_type></wp:comment_type>
495+<wp:comment_parent>0</wp:comment_parent>
496+<wp:comment_user_id>0</wp:comment_user_id>
497+</wp:comment>
498+ </item>
499+<item>
500+<title>Tools</title>
501+<link>http://qa.ubuntu.com/tools/</link>
502+<pubDate>Thu, 09 Sep 2010 07:27:12 +0000</pubDate>
503+<dc:creator><![CDATA[apulido]]></dc:creator>
504+
505+ <category><![CDATA[Uncategorized]]></category>
506+
507+ <category domain="category" nicename="uncategorized"><![CDATA[Uncategorized]]></category>
508+
509+<guid isPermaLink="false">https://newqa.ubunut.com/?page_id=159</guid>
510+<description></description>
511+<content:encoded><![CDATA[<h3>Apart from having enough information, you also need some tools that help you doing your daily job in Ubuntu QA. These are some of the tools that we use and that will help you on your way:</h3>
512+<ul>
513+ <li><a href="https://launchpad.net/launchpadlib">launchpadlib</a></li>
514+</ul>
515+<p style="padding-left: 30px;">This is a python interface to the Launchpad API. You can use it to create python scripts that access and modify the data in Launchpad.</p>
516+
517+<ul>
518+ <li><a href="https://launchpad.net/ubuntu-qa-tools">Ubuntu QA Tools</a></li>
519+</ul>
520+<p style="padding-left: 30px;">These are a set of small tools developed by the Ubuntu QA team to help us in our daily activities. The most useful subset of these tools for the wider audience are packaged in Ubuntu under the name ubuntu-qa-tools.</p>
521+
522+<ul>
523+ <li><a href="https://launchpad.net/launchpad-gm-scripts">Greasemonkey Launchpad Scripts</a></li>
524+</ul>
525+<p style="padding-left: 30px;">This project is a set of Greasemonkey scripts that adds functionality to Launchpad that is helpful if you have to use Launchpad on a daily basis. For example, it adds the bug stock responses that you can add quickly to your Launchpad comment.</p>]]></content:encoded>
526+<excerpt:encoded><![CDATA[]]></excerpt:encoded>
527+<wp:post_id>159</wp:post_id>
528+<wp:post_date>2010-09-09 07:27:12</wp:post_date>
529+<wp:post_date_gmt>2010-09-09 07:27:12</wp:post_date_gmt>
530+<wp:comment_status>close</wp:comment_status>
531+<wp:ping_status>open</wp:ping_status>
532+<wp:post_name>tools</wp:post_name>
533+<wp:status>publish</wp:status>
534+<wp:post_parent>0</wp:post_parent>
535+<wp:menu_order>0</wp:menu_order>
536+<wp:post_type>page</wp:post_type>
537+<wp:post_password></wp:post_password>
538+<wp:is_sticky>0</wp:is_sticky>
539+<wp:postmeta>
540+<wp:meta_key>_edit_lock</wp:meta_key>
541+<wp:meta_value>1285076551</wp:meta_value>
542+</wp:postmeta>
543+<wp:postmeta>
544+<wp:meta_key>_edit_last</wp:meta_key>
545+<wp:meta_value>2</wp:meta_value>
546+</wp:postmeta>
547+ </item>
548+<item>
549+<title>cropped-PlatformQAPrague.resized.jpg</title>
550+<link>http://qa.ubuntu.com/?attachment_id=207</link>
551+<pubDate>Thu, 16 Sep 2010 13:54:53 +0000</pubDate>
552+<dc:creator><![CDATA[apulido]]></dc:creator>
553+
554+ <category><![CDATA[Uncategorized]]></category>
555+
556+ <category domain="category" nicename="uncategorized"><![CDATA[Uncategorized]]></category>
557+
558+<guid isPermaLink="false">https://newqa.ubunut.com/wp-content/uploads/2010/09/cropped-PlatformQAPrague.resized.jpg</guid>
559+<description></description>
560+<content:encoded><![CDATA[https://newqa.ubunut.com/wp-content/uploads/2010/09/cropped-PlatformQAPrague.resized.jpg]]></content:encoded>
561+<excerpt:encoded><![CDATA[]]></excerpt:encoded>
562+<wp:post_id>207</wp:post_id>
563+<wp:post_date>2010-09-16 13:54:53</wp:post_date>
564+<wp:post_date_gmt>2010-09-16 13:54:53</wp:post_date_gmt>
565+<wp:comment_status>closed</wp:comment_status>
566+<wp:ping_status>open</wp:ping_status>
567+<wp:post_name>cropped-platformqaprague-resized-jpg</wp:post_name>
568+<wp:status>inherit</wp:status>
569+<wp:post_parent>0</wp:post_parent>
570+<wp:menu_order>0</wp:menu_order>
571+<wp:post_type>attachment</wp:post_type>
572+<wp:post_password></wp:post_password>
573+<wp:is_sticky>0</wp:is_sticky>
574+<wp:attachment_url>http://qa.ubuntu.com/wp-content/uploads/2010/09/cropped-PlatformQAPrague.resized.jpg</wp:attachment_url>
575+<wp:postmeta>
576+<wp:meta_key>_wp_attached_file</wp:meta_key>
577+<wp:meta_value>2010/09/cropped-PlatformQAPrague.resized.jpg</wp:meta_value>
578+</wp:postmeta>
579+<wp:postmeta>
580+<wp:meta_key>_wp_attachment_metadata</wp:meta_key>
581+<wp:meta_value>a:6:{s:5:"width";s:3:"976";s:6:"height";s:3:"428";s:14:"hwstring_small";s:23:"height='56' width='128'";s:4:"file";s:44:"2010/09/cropped-PlatformQAPrague.resized.jpg";s:5:"sizes";a:2:{s:9:"thumbnail";a:3:{s:4:"file";s:44:"cropped-PlatformQAPrague.resized-150x150.jpg";s:5:"width";s:3:"150";s:6:"height";s:3:"150";}s:6:"medium";a:3:{s:4:"file";s:44:"cropped-PlatformQAPrague.resized-300x131.jpg";s:5:"width";s:3:"300";s:6:"height";s:3:"131";}}s:10:"image_meta";a:10:{s:8:"aperture";s:1:"0";s:6:"credit";s:0:"";s:6:"camera";s:0:"";s:7:"caption";s:0:"";s:17:"created_timestamp";s:1:"0";s:9:"copyright";s:0:"";s:12:"focal_length";s:1:"0";s:3:"iso";s:1:"0";s:13:"shutter_speed";s:1:"0";s:5:"title";s:0:"";}}</wp:meta_value>
582+</wp:postmeta>
583+ </item>
584+<item>
585+<title>cropped-FontanaVillage_015-BW.resized.jpg</title>
586+<link>http://qa.ubuntu.com/?attachment_id=208</link>
587+<pubDate>Thu, 16 Sep 2010 14:06:31 +0000</pubDate>
588+<dc:creator><![CDATA[apulido]]></dc:creator>
589+
590+ <category><![CDATA[Uncategorized]]></category>
591+
592+ <category domain="category" nicename="uncategorized"><![CDATA[Uncategorized]]></category>
593+
594+<guid isPermaLink="false">https://newqa.ubunut.com/wp-content/uploads/2010/09/cropped-FontanaVillage_015-BW.resized.jpg</guid>
595+<description></description>
596+<content:encoded><![CDATA[https://newqa.ubunut.com/wp-content/uploads/2010/09/cropped-FontanaVillage_015-BW.resized.jpg]]></content:encoded>
597+<excerpt:encoded><![CDATA[]]></excerpt:encoded>
598+<wp:post_id>208</wp:post_id>
599+<wp:post_date>2010-09-16 14:06:31</wp:post_date>
600+<wp:post_date_gmt>2010-09-16 14:06:31</wp:post_date_gmt>
601+<wp:comment_status>closed</wp:comment_status>
602+<wp:ping_status>open</wp:ping_status>
603+<wp:post_name>cropped-fontanavillage_015-bw-resized-jpg</wp:post_name>
604+<wp:status>inherit</wp:status>
605+<wp:post_parent>0</wp:post_parent>
606+<wp:menu_order>0</wp:menu_order>
607+<wp:post_type>attachment</wp:post_type>
608+<wp:post_password></wp:post_password>
609+<wp:is_sticky>0</wp:is_sticky>
610+<wp:attachment_url>http://qa.ubuntu.com/wp-content/uploads/2010/09/cropped-FontanaVillage_015-BW.resized.jpg</wp:attachment_url>
611+<wp:postmeta>
612+<wp:meta_key>_wp_attached_file</wp:meta_key>
613+<wp:meta_value>2010/09/cropped-FontanaVillage_015-BW.resized.jpg</wp:meta_value>
614+</wp:postmeta>
615+<wp:postmeta>
616+<wp:meta_key>_wp_attachment_metadata</wp:meta_key>
617+<wp:meta_value>a:6:{s:5:"width";s:3:"976";s:6:"height";s:3:"428";s:14:"hwstring_small";s:23:"height='56' width='128'";s:4:"file";s:49:"2010/09/cropped-FontanaVillage_015-BW.resized.jpg";s:5:"sizes";a:2:{s:9:"thumbnail";a:3:{s:4:"file";s:49:"cropped-FontanaVillage_015-BW.resized-150x150.jpg";s:5:"width";s:3:"150";s:6:"height";s:3:"150";}s:6:"medium";a:3:{s:4:"file";s:49:"cropped-FontanaVillage_015-BW.resized-300x131.jpg";s:5:"width";s:3:"300";s:6:"height";s:3:"131";}}s:10:"image_meta";a:10:{s:8:"aperture";s:1:"0";s:6:"credit";s:0:"";s:6:"camera";s:0:"";s:7:"caption";s:0:"";s:17:"created_timestamp";s:1:"0";s:9:"copyright";s:0:"";s:12:"focal_length";s:1:"0";s:3:"iso";s:1:"0";s:13:"shutter_speed";s:1:"0";s:5:"title";s:0:"";}}</wp:meta_value>
618+</wp:postmeta>
619+ </item>
620+<item>
621+<title>Bugs</title>
622+<link>http://qa.ubuntu.com/bugs/</link>
623+<pubDate>Tue, 21 Sep 2010 08:16:43 +0000</pubDate>
624+<dc:creator><![CDATA[apulido]]></dc:creator>
625+
626+ <category><![CDATA[Uncategorized]]></category>
627+
628+ <category domain="category" nicename="uncategorized"><![CDATA[Uncategorized]]></category>
629+
630+<guid isPermaLink="false">https://newqa.ubunut.com/?page_id=235</guid>
631+<description></description>
632+<content:encoded><![CDATA[<h3>Ubuntu is a huge project with millions of users. We have thousands of bugs that need processing, reproducing, sending upstream, etc. Triaging bugs is a great way to help Ubuntu.</h3>
633+Bug triage is an essential part of Ubuntu's development.
634+
635+Triaging bugs consists of several things:
636+<ul>
637+ <li>Responding to new bugs as they are filed.</li>
638+ <li>Ensuring that new bugs have all the necessary information.</li>
639+ <li>Assigning bugs to the proper package.</li>
640+ <li>Confirming bug reports by trying to reproduce them.</li>
641+ <li>Setting the priority of bugs reports.</li>
642+ <li>Searching for and marking duplicates in the bug tracking system.</li>
643+ <li>Sending bugs to their upstream authors, when applicable.</li>
644+ <li>Cross-referencing bugs from other distributions.</li>
645+ <li>Expiring old bugs.</li>
646+</ul>
647+However, you don't need to do all of those things to help! Recreating a bug and setting the status to Confirmed is enough.
648+
649+Bug triage is an excellent way to start helping out. You get to learn a lot about Ubuntu, its available packages, its infrastructure, and you get a feel for the development pulse.
650+
651+You can learn how to triage bugs and chip in, just see the <a href="https://wiki.ubuntu.com/Bugs/HowToTriage">Bugs/HowToTriage</a> page.
652+<h4>Joining the team</h4>
653+<p style="padding-left: 30px;">The people who work on triaging bugs in Ubuntu are called the Ubuntu <a href="https://wiki.ubuntu.com/BugSquad">BugSquad</a>. Check out the <a href="https://wiki.ubuntu.com/BugSquad/GettingInvolved">BugSquad/GettingInvolved</a> page to learn how to join.</p>
654+<p style="padding-left: 30px;">You can almost always find members of the Bug Squad in #ubuntu-bugs on the freenode <a href="https://wiki.ubuntu.com/IRC">IRC</a> server who will be happy to answer any questions you have.</p>
655+
656+<h4 id="Adopting a package">Adopting a package</h4>
657+<p style="padding-left: 30px;">If you've got a keen interest in a particular source package, you can help out by adopting it. This means that you want to act as a liaison between Ubuntu and the people who wrote the package that we include in the distribution.</p>
658+<p style="padding-left: 30px;">This involves developing a relationship with the people who work on this software: developers, users, and other members of the community. You can quickly become an expert by triaging bugs associated with this package and even fixing some of them.</p>
659+<p style="padding-left: 30px;">You can learn more about doing this by consulting the <a href="https://wiki.ubuntu.com/BugSquad/AdoptPackage">BugSquad/AdoptPackage</a> page.</p>]]></content:encoded>
660+<excerpt:encoded><![CDATA[]]></excerpt:encoded>
661+<wp:post_id>235</wp:post_id>
662+<wp:post_date>2010-09-21 08:16:43</wp:post_date>
663+<wp:post_date_gmt>2010-09-21 08:16:43</wp:post_date_gmt>
664+<wp:comment_status>closed</wp:comment_status>
665+<wp:ping_status>open</wp:ping_status>
666+<wp:post_name>bugs</wp:post_name>
667+<wp:status>publish</wp:status>
668+<wp:post_parent>0</wp:post_parent>
669+<wp:menu_order>0</wp:menu_order>
670+<wp:post_type>page</wp:post_type>
671+<wp:post_password></wp:post_password>
672+<wp:is_sticky>0</wp:is_sticky>
673+<wp:postmeta>
674+<wp:meta_key>_edit_lock</wp:meta_key>
675+<wp:meta_value>1285064060</wp:meta_value>
676+</wp:postmeta>
677+<wp:postmeta>
678+<wp:meta_key>_edit_last</wp:meta_key>
679+<wp:meta_value>2</wp:meta_value>
680+</wp:postmeta>
681+<wp:postmeta>
682+<wp:meta_key>_wp_page_template</wp:meta_key>
683+<wp:meta_value>default</wp:meta_value>
684+</wp:postmeta>
685+ </item>
686+<item>
687+<title>Automation</title>
688+<link>http://qa.ubuntu.com/automation/</link>
689+<pubDate>Tue, 21 Sep 2010 08:20:56 +0000</pubDate>
690+<dc:creator><![CDATA[apulido]]></dc:creator>
691+
692+ <category><![CDATA[Uncategorized]]></category>
693+
694+ <category domain="category" nicename="uncategorized"><![CDATA[Uncategorized]]></category>
695+
696+<guid isPermaLink="false">https://newqa.ubunut.com/?page_id=172</guid>
697+<description></description>
698+<content:encoded><![CDATA[<h3>We try to automate as much as we can, and we have tools that help us in our mission. All of these tools and processes are released under a Free Software license, so you can start collaborating as soon as you want!</h3>
699+<h4><strong>Checkbox</strong></h4>
700+<p style="padding-left: 30px;">Checkbox is one of the main tools we use for testing automation. Basically, it is a test runner that can run any kind of tests: automated or manual, shell scripts or complex applications. It gathers all the information in a XML file that can be used to create reports. This is the tool that you have installed in your Ubuntu system under System-&gt;Administration-&gt;System Testing.</p>
701+<p style="padding-left: 30px;">Launchpad Project: <a href="https://launchpad.net/checkbox">https://launchpad.net/checkbox</a>
702+Documentation: <a href="https://wiki.ubuntu.com/Testing/Automation/Checkbox">https://wiki.ubuntu.com/Testing/Automation/Checkbox</a></p>
703+
704+<h4><strong>Mago</strong></h4>
705+<p style="padding-left: 30px;">Mago is a desktop testing initiative, built on top of the LDTP GUI testing framework (http://ldtp.freedesktop.org/), that aims to have a set of processes and code to make writing automated desktop test scripts easier and more reusable.</p>
706+<p style="padding-left: 30px;">Launchpad Project: <a href="https://launchpad.net/mago">https://launchpad.net/mago</a>
707+Documentation: <a href="http://mago.ubuntu.com">http://mago.ubuntu.com</a></p>
708+
709+<h4><strong>Mvo’s automated upgrades</strong></h4>
710+<p style="padding-left: 30px;">Michael Vogt maintains a set of daily upgrade tests to check if all the packages are upgrading. You can check the results online:</p>
711+
712+<ul>
713+ <li>Ubuntu-&gt;Ubuntu+1 Upgrades: <a href="http://people.canonical.com/~mvo/automatic-upgrade-testing/current/">http://people.canonical.com/~mvo/automatic-upgrade-testing/current/</a></li>
714+ <li>Ubuntu-&gt;Ubuntu-updates: <a href="http://people.canonical.com/~mvo/automatic-upgrade-testing/current-stable/">http://people.canonical.com/~mvo/automatic-upgrade-testing/current-stable/</a></li>
715+</ul>
716+<strong>Ev’s automated installation tests</strong>
717+<p style="padding-left: 30px;">Evan Dandrea, the maintainer of Ubiquity, the Ubuntu installer, is creating a set of scripts to automate the installation process. This is a work in progress, we will update this entry as soon as the work is published.</p>]]></content:encoded>
718+<excerpt:encoded><![CDATA[]]></excerpt:encoded>
719+<wp:post_id>172</wp:post_id>
720+<wp:post_date>2010-09-21 08:20:56</wp:post_date>
721+<wp:post_date_gmt>2010-09-21 08:20:56</wp:post_date_gmt>
722+<wp:comment_status>closed</wp:comment_status>
723+<wp:ping_status>closed</wp:ping_status>
724+<wp:post_name>automation</wp:post_name>
725+<wp:status>publish</wp:status>
726+<wp:post_parent>0</wp:post_parent>
727+<wp:menu_order>0</wp:menu_order>
728+<wp:post_type>page</wp:post_type>
729+<wp:post_password></wp:post_password>
730+<wp:is_sticky>0</wp:is_sticky>
731+<wp:postmeta>
732+<wp:meta_key>_edit_lock</wp:meta_key>
733+<wp:meta_value>1285061138</wp:meta_value>
734+</wp:postmeta>
735+<wp:postmeta>
736+<wp:meta_key>_edit_last</wp:meta_key>
737+<wp:meta_value>2</wp:meta_value>
738+</wp:postmeta>
739+ </item>
740+<item>
741+<title>cropped-road.jpg</title>
742+<link>http://qa.ubuntu.com/?attachment_id=264</link>
743+<pubDate>Tue, 21 Sep 2010 10:23:06 +0000</pubDate>
744+<dc:creator><![CDATA[apulido]]></dc:creator>
745+
746+ <category><![CDATA[Uncategorized]]></category>
747+
748+ <category domain="category" nicename="uncategorized"><![CDATA[Uncategorized]]></category>
749+
750+<guid isPermaLink="false">http://newqa.ubunut.com/wp-content/uploads/2010/09/cropped-road.jpg</guid>
751+<description></description>
752+<content:encoded><![CDATA[http://newqa.ubunut.com/wp-content/uploads/2010/09/cropped-road.jpg]]></content:encoded>
753+<excerpt:encoded><![CDATA[]]></excerpt:encoded>
754+<wp:post_id>264</wp:post_id>
755+<wp:post_date>2010-09-21 10:23:06</wp:post_date>
756+<wp:post_date_gmt>2010-09-21 10:23:06</wp:post_date_gmt>
757+<wp:comment_status>closed</wp:comment_status>
758+<wp:ping_status>open</wp:ping_status>
759+<wp:post_name>cropped-road-jpg</wp:post_name>
760+<wp:status>inherit</wp:status>
761+<wp:post_parent>0</wp:post_parent>
762+<wp:menu_order>0</wp:menu_order>
763+<wp:post_type>attachment</wp:post_type>
764+<wp:post_password></wp:post_password>
765+<wp:is_sticky>0</wp:is_sticky>
766+<wp:attachment_url>http://qa.ubuntu.com/wp-content/uploads/2010/09/cropped-road.jpg</wp:attachment_url>
767+<wp:postmeta>
768+<wp:meta_key>_wp_attachment_metadata</wp:meta_key>
769+<wp:meta_value>a:6:{s:5:"width";s:3:"976";s:6:"height";s:3:"428";s:14:"hwstring_small";s:23:"height='56' width='128'";s:4:"file";s:24:"2010/09/cropped-road.jpg";s:5:"sizes";a:2:{s:9:"thumbnail";a:3:{s:4:"file";s:24:"cropped-road-150x150.jpg";s:5:"width";s:3:"150";s:6:"height";s:3:"150";}s:6:"medium";a:3:{s:4:"file";s:24:"cropped-road-300x131.jpg";s:5:"width";s:3:"300";s:6:"height";s:3:"131";}}s:10:"image_meta";a:10:{s:8:"aperture";s:1:"0";s:6:"credit";s:0:"";s:6:"camera";s:0:"";s:7:"caption";s:0:"";s:17:"created_timestamp";s:1:"0";s:9:"copyright";s:0:"";s:12:"focal_length";s:1:"0";s:3:"iso";s:1:"0";s:13:"shutter_speed";s:1:"0";s:5:"title";s:0:"";}}</wp:meta_value>
770+</wp:postmeta>
771+<wp:postmeta>
772+<wp:meta_key>_wp_attached_file</wp:meta_key>
773+<wp:meta_value>2010/09/cropped-road.jpg</wp:meta_value>
774+</wp:postmeta>
775+ </item>
776+<item>
777+<title>cropped-road.jpg</title>
778+<link>http://qa.ubuntu.com/?attachment_id=274</link>
779+<pubDate>Wed, 22 Sep 2010 06:53:33 +0000</pubDate>
780+<dc:creator><![CDATA[apulido]]></dc:creator>
781+
782+ <category><![CDATA[Uncategorized]]></category>
783+
784+ <category domain="category" nicename="uncategorized"><![CDATA[Uncategorized]]></category>
785+
786+<guid isPermaLink="false">http://qa.ubuntu.com/wp-content/uploads/2010/09/cropped-road.jpg</guid>
787+<description></description>
788+<content:encoded><![CDATA[http://qa.ubuntu.com/wp-content/uploads/2010/09/cropped-road.jpg]]></content:encoded>
789+<excerpt:encoded><![CDATA[]]></excerpt:encoded>
790+<wp:post_id>274</wp:post_id>
791+<wp:post_date>2010-09-22 06:53:33</wp:post_date>
792+<wp:post_date_gmt>2010-09-22 06:53:33</wp:post_date_gmt>
793+<wp:comment_status>closed</wp:comment_status>
794+<wp:ping_status>open</wp:ping_status>
795+<wp:post_name>cropped-road-jpg-2</wp:post_name>
796+<wp:status>inherit</wp:status>
797+<wp:post_parent>0</wp:post_parent>
798+<wp:menu_order>0</wp:menu_order>
799+<wp:post_type>attachment</wp:post_type>
800+<wp:post_password></wp:post_password>
801+<wp:is_sticky>0</wp:is_sticky>
802+<wp:attachment_url>http://qa.ubuntu.com/wp-content/uploads/2010/09/cropped-road.jpg</wp:attachment_url>
803+<wp:postmeta>
804+<wp:meta_key>_wp_attachment_metadata</wp:meta_key>
805+<wp:meta_value>a:6:{s:5:"width";s:3:"976";s:6:"height";s:3:"428";s:14:"hwstring_small";s:23:"height='56' width='128'";s:4:"file";s:24:"2010/09/cropped-road.jpg";s:5:"sizes";a:2:{s:9:"thumbnail";a:3:{s:4:"file";s:24:"cropped-road-150x150.jpg";s:5:"width";s:3:"150";s:6:"height";s:3:"150";}s:6:"medium";a:3:{s:4:"file";s:24:"cropped-road-300x131.jpg";s:5:"width";s:3:"300";s:6:"height";s:3:"131";}}s:10:"image_meta";a:10:{s:8:"aperture";s:1:"0";s:6:"credit";s:0:"";s:6:"camera";s:0:"";s:7:"caption";s:0:"";s:17:"created_timestamp";s:1:"0";s:9:"copyright";s:0:"";s:12:"focal_length";s:1:"0";s:3:"iso";s:1:"0";s:13:"shutter_speed";s:1:"0";s:5:"title";s:0:"";}}</wp:meta_value>
806+</wp:postmeta>
807+<wp:postmeta>
808+<wp:meta_key>_wp_attached_file</wp:meta_key>
809+<wp:meta_value>2010/09/cropped-road.jpg</wp:meta_value>
810+</wp:postmeta>
811+ </item>
812+</channel>
813+</rss>

Subscribers

People subscribed via source and target branches

to status/vote changes: