Open Stack

On 04/24/13 22:33, Sean Dague wrote:
> This week I'd like to get a feeling on every blueprint that currently
> exists in the tempest tracker - https://launchpad.net/tempest. For
> anything that someone is committing too, we need a milestone of -1 or -2
> (-3s are discouraged at this point, unless it's part of a series of
> blueprints with -1 or -2 pieces being delivered).

[...]

> Comments and flames are welcomed. :) Hopefully this isn't terribly
> controversial though after our conversations last week.

I've very recently started hacking some tests in tempest [1] and this 
approach looks to me very good.

I've a number of other questions too:

- currently I just add a blueprint for every test I work on and post a 
review on gerrit even if the blueprint itself hasn't been 'approved' yet 
by someone else; is this okay?
- if (1) is not the correct approach, how/when should I ask for a review 
of the blueprint?
- is there anything describing how/when a test is backported into the 
tempest' stable branches?

Thanks!

1. https://review.openstack.org/#/dashboard/6796
-- 
Giulio Fidente
GPG KEY: 08D733BA | IRC: giulivo