Brian Waldon and I discussed this today. We came up with an idea which is to 
have the tempest run on stable/<last-release> during the dev cycle, and after 
the last milestone turn it on during the bugfixing phase. The potential 
disadvantage of this approach is that it could potentially make bugfixes a 
little harder to get in, but it might help make things more stable.

Definitely worth a discussion at the summit.

Vish

On Sep 6, 2012, at 8:00 AM, Dan Smith <da...@us.ibm.com> wrote:

> DK> This situation is pretty bad.
> 
> Agreed. I wonder if it makes sense to enable full-run tempest gating
> temporarily as we close in on the final days of Folsom? It might not
> make sense during open development, but at this point, it would surely
> make sense to me to require people's (say, nova) patches to not break
> tempest. Fewer patches should be going in these days, so I'd expect it
> to not require an obscene amount of resources.
> 
> -- 
> Dan Smith
> IBM Linux Technology Center


-- 
Mailing list: https://launchpad.net/~openstack-qa-team
Post to     : openstack-qa-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-qa-team
More help   : https://help.launchpad.net/ListHelp

Reply via email to