Progress towards topic-quantal-quality-community-testing

This page shows the progress towards completing a Topic . You can see from the burndown if the Topic is likely to be completed at the current rate of work. Below that you can see the progress towards the blueprints that contribute to the Topic , and the progress of each person working on the Topic .

Launchpad page

Workitem burndown


"foreign" counts refer to workitems that are assigned to someone not in the team

Burndown chart
82% of 66

Contributing Blueprints

Blueprint Completion Priority Status/Description
70% of 10
Medium Discussing options for improving manual testing, metrics, and user feedback for those running the development version of ubuntu
92% of 13
High Review of Quantal schedule and Interlock schedule to 12.04.1 needs. Primary page is: Need to synch with: (for 12.04.1)
43% of 14
Medium Discussion of changes that would help: - release team with managing and publishing images, understanding the quality/shipability - qa teams (ubuntu and flavors) for understanding quality of images and issues for developers - testers ease of using system, logging results, automated logging, knowing bugs
100% of 5
Medium Track progress and be able to determine how long will take us to get to 100% coverage and help us prioritize the work
100% of 8
High Discussing expanding the isotracker to perform testcase management and reporting for all kinds of testing, not just iso.
100% of 16
Essential Discuss what went well and what didn't go so well in terms of QA - Release team communication during P and try to put in place the actions for smoother milestones during Q.

Status by assignee

Assignee Todo Blocked In Progress Postponed Done Completion
Ara Pulido 0 0 0 0 1 100%
cgregan 1 0 0 0 0 0%
Colin Watson 0 0 0 2 1 100%
David Planella 1 0 0 0 2 67%
Fathi Boudra 0 0 0 0 1 100%
gema 1 0 0 0 0 0%
Gema Gomez 0 0 0 2 8 100%
Jean-Baptiste Lallement 0 0 0 0 1 100%
Kate Stewart 0 0 0 1 7 100%
Nicholas Skaggs 0 0 0 0 10 100%
Martin Pitt 0 0 0 0 1 100%
popey 1 0 0 0 0 0%
Paul Larson 0 0 0 0 1 100%
registry 1 0 0 0 0 0%
Ricardo Salveti 0 0 0 0 1 100%
Stéphane Graber 0 1 0 2 12 93%
timrchavez 1 0 0 0 0 0%
ubuntu-cdimage 1 0 0 0 0 0%
ubuntu-release 2 0 0 0 1 33%
Ben Howard 1 0 0 0 0 0%
Steve Langasek 1 0 0 0 0 0%

Work item details

Assignee Status Blueprint Priority Work item
Ara Pulido done other-q-release-schedule-review High add in official cert, and smoke test in column (and basically any cert information that is missing)
cgregan todo qa-q-manual-app-testing Medium provide information about apport-bug to nskaggs
Colin Watson done other-q-release-schedule-review High cron job updates for 12.04.1 dailies and testing.
postponed qa-q-release-communication-improvements Essential Explain what the weather report is currently used for by the release team to help QA understand how to convey/integrate that info with the new reporting
qa-q-release-communication-improvements Essential Worst case install path definition set up
David Planella todo other-q-release-schedule-review High update automatic exports to synch up with 12.04.1
done other-q-release-schedule-review High work with skaet to get clean up translation deadline.
other-q-release-schedule-review High update the TranslationsDeadline page in line with the newly merged deadline (
Fathi Boudra done other-q-release-schedule-review High add linaro events to interlock
gema todo foundations-q-iso-tracker Medium provide input examples for LAVA format, for stgraber to know what the tracker should be reading
Gema Gomez done qa-q-release-communication-improvements Essential Find out who decides which test cases are mandatory
qa-q-release-communication-improvements Essential Figure out what information is in the weather report and if it needs to be integrated with the new reporting
qa-q-release-communication-improvements Essential Think about value added of having QA Team keep an eye on what is going on on the different dev teams (there would be value, we have no bandwidth)
qa-q-release-communication-improvements Essential Find out who in the desktop team needs to notify us from app migrations and make them aware. seb128 to send updates to the qa-team
qa-q-metrics Medium Create a wiki to keep track of all the different groups tagging
qa-q-metrics Medium Figure out which tag to use for Platform QA, generic bugs (
qa-q-metrics Medium Add a report to the QA reporting to track all these bugs, already in place for existing bugs, since nobody else is adding theirs there is no need to change the report)
qa-q-metrics Medium Agree on a place to share the scripts to gather the metrics (I have my script in lp, whenever we have more scripts we can consider a launchpad project)
postponed qa-q-release-communication-improvements Essential Make sure only mandatory test cases are marked mandatory on the tracker
qa-q-release-communication-improvements Essential Make sure that app migrations grant a test case addition. Desktop team needs to be involved (we don't have the bandwidth this cycle, hopefully next)
Jean-Baptiste Lallement done other-q-release-schedule-review High update automated testing jobs to continuously test 12.04.x images in parallel of 12.10
Kate Stewart done qa-q-release-communication-improvements Essential update team reporting template to make it explicit what has changed for testing purposes
qa-q-release-communication-improvements Essential Update process pages, with places that need to be updated with minimum and recommended configuration information - (see websites on the whiteboard) release notes, any information included on, and the CD sleeves (get info from blythe where this is pulled from)
qa-q-release-communication-improvements Essential Talk about prioritization of isos with stgraber
other-q-release-schedule-review High update interlock with results from today's discussion, and master schedules.
other-q-release-schedule-review High add column for community calls for tests
other-q-release-schedule-review High rename of the merged translation deadline in the schedule be set to 'TranslationsDeadline'
qa-q-manual-app-testing Medium add Testing Days to Release Interlock page and coordinate with nskaggs
postponed qa-q-manual-app-testing Medium investigate options into making education available to folks who install CD or when apport comes up?
Nicholas Skaggs done qa-q-release-communication-improvements Essential Have all test cases for the release, ready and reviewed by feature freeze
qa-q-release-communication-improvements Essential Make sure community testing happens more evenly during the cycle
qa-q-release-communication-improvements Essential More proactive communication
other-q-release-schedule-review High review/edit planned community testing calls
qa-q-metrics Medium To find out or agree with the community what tagging they are going to use
qa-q-manual-app-testing Medium Meet with SRU verification team to discuss resource contention
qa-q-manual-app-testing Medium Meet with stgraber to discuss option for translation of testcases (to other languages) to enable wider pool of testers.
qa-q-manual-app-testing Medium Talk to apport team to understand plans for apport (how it prompts, when it appears, etc) during the development release
qa-q-manual-app-testing Medium Contact AlanBell to ensure accessibility testcases exist and are well-represented for accessibility
qa-q-manual-app-testing Medium Meet with stgraber to discuss using isotracker for manual testing events
Martin Pitt done other-q-release-schedule-review High add in community key events schedule. GNOME, KDE, LibreOffice.
popey todo qa-q-manual-app-testing Medium follow up on apport refusing to file bugs for packages taken from the official unity ppa
Paul Larson done qa-q-release-communication-improvements Essential Minimum configuration to be included on ISO testing
registry todo foundations-q-iso-tracker Medium testcases need to be denoted as manual or automated, and naming needs to be cleaned up
Ricardo Salveti done other-q-release-schedule-review High synch with kate.stewart after connect.
Stéphane Graber blocked foundations-q-iso-tracker Medium figure out how to add hardware profile to Ubuntu Friendly, and finishing hardware integation (waiting to know what tool will be used)
done qa-q-isotracker-testcases High Update DB schema to have testcase entries be one-to-many to testsuite and have testsuite be many-to-many to milestone_series
qa-q-isotracker-testcases High Never allow modifications to qatracker_testcase
qa-q-isotracker-testcases High 2: Figure out how to manage users roles (per product roles) (use lp teams, grant isotracker roles based on team)
qa-q-isotracker-testcases High add link to report "bug" against problems found on a testcase (bug #684404)
qa-q-isotracker-testcases High 2: come up with development plan for cycle
qa-q-isotracker-testcases High add testcase id that stays unique and persists across revisions
qa-q-isotracker-testcases High Let the team know when ( is ready for testing
foundations-q-iso-tracker Medium add release ready status to build record
foundations-q-iso-tracker Medium netboot changelogs put out to notice boards as example
foundations-q-iso-tracker Medium Allow for filtering by time range for /history and the top testers report (possibly others report too)
foundations-q-iso-tracker Medium Implement subscriptions page
foundations-q-iso-tracker Medium Improve subscription report to better deal with long lists of subscribers
postponed qa-q-isotracker-testcases High implement reading LAVA format on the tracker (
foundations-q-iso-tracker Medium bug columns - extract info from launchpad, show untriaged in one columns, and release critical/not in another
timrchavez todo foundations-q-iso-tracker Medium separate instance for tracking Professional service. Look into build infrastructure automatically feeding in
ubuntu-cdimage todo foundations-q-iso-tracker Medium automatically post a diff between builds to notice boards on the tracker, linking to log of what changed for history. Superseded images have differences
ubuntu-release todo foundations-q-iso-tracker Medium what are criteria for image being added to localized tester
foundations-q-iso-tracker Medium decide on what we put out, between builds, day, since milestone, between milestone
done qa-q-release-communication-improvements Essential Based on Nick's test cases, decide which ones have to be mandatory and which ones are not
Ben Howard todo foundations-q-iso-tracker Medium incorporate script so that cloud images automatically publish
Steve Langasek todo qa-q-manual-app-testing Medium discuss with mpt about adding a button to update-manager to let users see the list of all changes in one go instead of having to drill down into the list; useful to have available in the development release in particular

Last updated: Fri 26 October 2012, 08:49 UTC