Blueprint changed by Ben Howard: Whiteboard changed: + [TEST PLAN] + The core of this blue print is adding tests. Therefore the implementation of this blue print is a test itself. + + [ASSUMPTIONS] + It is assumed that this will be a multi-cycle blue print that will undergo refinement. Implementation of some pieces may happen in later cycles. + + [RISKS] + The biggest risk for implementation is cost. For some cloud vendors, the ability to implement all tests would represent a significant financal burden. This risk will be mitigated by stepping tests such that only relavent tests will be done as approprate. + + [RELEASE NOTE] + Starting with "r", the Ubuntu Cloud Images are now on a release cadance that follows the kernel SRU process. In general, new Cloud Images for all supported stable releases and long-term releases will follow a few days after availability of kernel, gcc and other boot-critical packages. Further, all released daily builds undergo exhaustive testing to ensure quality and to check regressions, performance and integration into Cloud environments. Users who are interested in tracking the testing can find the test results on http://jenkins.qa.ubuntu.com and http://iso.qa.ubuntu.com. + + + [FEEDBACK from RFC]: + Suggested for Release Notes and Notification: 1/ release notes for each releases are published and kept on cloud-images.ubuntu.com. Maybe in /<suite>/release-notes/ with a link from the individual /<suite>/<version>/ directory? As you remove versions you still keep the release notes. 2/ Set up a notification method via twitter, or RSS Feed. 3/ Keep sending emails for the time being
-- Cloud Image Testing and Automation https://blueprints.launchpad.net/ubuntu/+spec/servercloud-r-cloudtesting -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
