Tracking issues that we should be testing

Robie Basak robie.basak at
Wed Jun 6 12:58:13 UTC 2012


Every so often I come across an issue which I feel that we should be
testing on a regular basis. For example: I think that this multipath bug
should be considered for automated installer testing for Ubuntu Server:

I think this kind of thing is a candidate for a consumer of UTAH, but
due to the d-i involvement required is perhaps not trivial to do right

Do we have a way of tracking these items so that we could have a backlog
of tests that we would like to have once the infrastructure is in place?
Perhaps a Launchpad project to add a bug task against?



More information about the Ubuntu-qa mailing list