Hi, On Fri, 22 Jun 2012 17:15:15 +0200 Martin Pitt <[email protected]> wrote:
> Chuck Short [2012-06-22 10:48 -0400]: > > We also run a couple of exercises agaisnt the deployment when it > > happens in the lab. > > Where "deployment" is "packages from -proposed", or images that were > built using the actual packages from -proposed? We need to ensure that > there have not been any misbuilds or regressions in the packaging > part; i. e. they did not accidentally drop files or put them into a > wrong place, or the postinst fails on upgrade, and similar problems > which upstream tests do not cover. We intend to address this in the openstack-ci process this cyle by including piuparts in our testing. However if a merge proposal comes upstream that ask for files to be moved around it wouldn't be a good candidate in the stable/essex tree. > A deployment test which covers these, together with the continuous > upstream integration testing certainly seems adequate for an MRE to > me. The feedback about that deployment (or other system integration) > test needs to go to the SRU tracking bug (like "update nova to 1.2.3 > in precise") to let the SRU team know when an update has been > rubber-stamped as good to go. This did not happen to any of the bugs > in the previous nova SRU and was the main case of why it got stalled. > > Thanks, > > Martin > Right that was done this time around: https://bugs.launchpad.net/ubuntu/+source/nova/+bug/1010473 We had a session about the Openstack SRU process and we are more or less following the Kernel Team's SRU process when it comes to Openstack updates. Regards chuck -- technical-board mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/technical-board
