> -Original Message-
> From: Matthew Treinish [mailto:mtrein...@kortar.org]
> Sent: Wednesday, June 18, 2014 10:33 PM
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] [qa] Clarification of policy for qa-specs around
>
> Subject: Re: [openstack-dev] [qa] Clarification of policy for qa-specs
> > around adding new tests
> >
> > On Mon, Jun 16, 2014 at 10:46:51AM -0400, David Kranz wrote:
> > > I have been reviewing some of these specs and sense a lack of clarity
> > > aro
> -Original Message-
> From: Matthew Treinish [mailto:mtrein...@kortar.org]
> Sent: Monday, June 16, 2014 11:58 PM
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] [qa] Clarification of policy for qa-specs around
> adding
On Mon, Jun 16, 2014 at 10:46:51AM -0400, David Kranz wrote:
> I have been reviewing some of these specs and sense a lack of clarity around
> what is expected. In the pre-qa-specs world we did not want tempest
> blueprints to be used by projects to track their tempest test submissions
> because the
I have been reviewing some of these specs and sense a lack of clarity
around what is expected. In the pre-qa-specs world we did not want
tempest blueprints to be used by projects to track their tempest test
submissions because the core review team did not want to have to spend a
lot of time dea
