Open Stack

On Mon, May 19, 2014 at 9:38 AM, Alexis Lee <alexisl at hp.com> wrote:

> We're seeing the spread of various *-specs projects now, which is great
> to see. Some of these (nova, neutron and tripleo) include a Python unit
> test (tests/test_titles.py) to check the specs follow the template. The
> test has been copy-pasted between projects and it's diverging already.
> Nova has a couple of extra tests; Neutron has some custom directives;
> TripleO disallows additional sections.
>
> It seems reasonable that while the specific allowed sections and
> subsections may vary, the general guidance should apply across all
> OpenStack projects much as code shares HACKING.
>
> I put up a review here: https://review.openstack.org/#/c/91801/
> which makes it more data-driven. Potentially the TITLES structure could
> be read from a per-project YAML file and the test itself could be drawn
> from some common area?
>

This sounds like a good idea, standardizing tooling across different
projects is one of the key items that has helped OpenStack development
scale and make it easy for developers to switch between projects.


>
>
> Alexis
> --
> Nova Engineer, HP Cloud.  AKA lealexis, lxsli.
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140519/e4261fee/attachment.html>