Re: [openstack-dev] [bashate] towards "inbox zero" on bashate changes, release?

2014-10-29 Thread Sean Dague
On 10/28/2014 10:03 PM, Ian Wienand wrote: > On 10/14/2014 04:03 PM, Ian Wienand wrote: >> Maybe it is time for a release? One thing; does the pre-release check >> run over TOT devstack and ensure there are no errors? We don't want >> to release and then 10 minutes later gate jobs start failing.

Re: [openstack-dev] [bashate] towards "inbox zero" on bashate changes, release?

2014-10-28 Thread Ian Wienand
On 10/14/2014 04:03 PM, Ian Wienand wrote: > Maybe it is time for a release? One thing; does the pre-release check > run over TOT devstack and ensure there are no errors? We don't want > to release and then 10 minutes later gate jobs start failing. Just to loop back on this ... Our main goal he

Re: [openstack-dev] [bashate] towards "inbox zero" on bashate changes, release?

2014-10-14 Thread Christian Berendt
On 10/14/2014 07:03 AM, Ian Wienand wrote: > 1) changes for auto-detection. IMO, we should drop all these and just >leave bashate as taking a list of files to check, and let >test-harnesses fix it. Everyone using it at the moment seems fine >without them I am fine with this and aband

[openstack-dev] [bashate] towards "inbox zero" on bashate changes, release?

2014-10-13 Thread Ian Wienand
Hi, I took the liberty of rebasing and approving the fairly obvious and already +1'd bashate changes today that had been sitting for quite a while. What's left is minimal and fall into three categories 1) changes for auto-detection. IMO, we should drop all these and just leave bashate as tak