Work Items Tracker

Status for
canonical-platform-qa

This page shows the progress for a team or person towards a particular target. The burndown gives you a sense
of whether they are on track to complete all of their tasks at the current rate, and the information below shows
their progress against individual
Topics
, blueprints and workitems.

Compile a list of applications that are installed by default by the ISO installers for Desktop and propose two or three basic test cases for each that could be run post install giving us basic confidence that the ISO is good for further testing

Start counting how many regressions happen for SRUs in the current cycle so that we have metrics for next UDS, which packages do regress (possibly add to people.canonical.com/~ubuntu-archive/pending-sru.html), new defect tagging being discuss to be able to achieve this

Document all available jobs and reasons for them, determine a policy regarding creating new jobs so that we only create new jobs when it makes sense. If there is a job without a reason to be, it should be removed

Establish the workflow for creating jobs, removing jobs, modifying jobs. Make sure nobody adds new jobs to the production Jenkins without having tried it first and demonstrated it works in the pre-production environment. Use bazaar to store the jobs and jenkins configuration, people should submit to the branch and then you can catch up on the production servers for updating with the latest changes