Automate testing from -proposed

[Leann Ogasawara]

Hi All,

A discussion regarding testing packages in the -proposed pocket has
recently come up.  Obviously our own personal interest lies with testing
of the kernels which land in -proposed before they are promoted to
-updates.  Below is an initial summary of requirements that need to be
resolved as well as some follow up questions which have been raised.

Initial list of requirements from QA Team (ie Mathieu Trudel-Lapierre):

 * an infrastructure to support adding these special tasks to the
installation preseed, in other words what will add the repository and
install/upgrade packages (mostly done)
 * a tracker to kick-start installations once new packages are found in
-proposed
 * a way to display the fact, on the certification website, that testing
was done on a release image (or point-release image), with additional
packages from proposed, and *which* additional packages

So far, the tracker and display changes have not been started yet. This
is all development on the hardware certification side of things.

Our comments/concerns from a kernel point of view are as follows:
 * Are the above requirements blocking current testing of packages in
-proposed?  It seems QA could/should be testing every kernel uploaded to
-proposed already, even if it needs to be done manually until the
automation is in place.
 * How long is it going to take for the infrastructure to be completed
to an extent where you/we can start using it?
 * When will QA start on the tracker / display changes and what is an
estimate for having them completed?
 * What constitutes the set of automated tests that are currently being
run?
 * Where can we expect to view test results and what permissions will we
need to access the results?

I think this summarizes the current discussion up to now.  Please feel
free to add anything I've missed or raise any additional questions.

Thanks,
Leann