Open Stack

> >
> > What's the best way to make this list better?
>
> I would suggest to give us your take on the right way to consider
> Swift capabilities give some of the background I've supplied. The only
> additional caveat is that we need to be able to connect existing
> Tempest tests to capabilities. We can then work on redoing that section of the scoresheet.
>


We have not formalized this in DefCore or with the TC yet.  My thought was that the PTLs for the projects would define/recommend the capability groups and map them to the tests.  We need to move the capabilities mapping out of a spreadsheet and into a controlled json file.

We've started that https://review.openstack.org/#/c/91640/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/defcore-committee/attachments/20140508/6a2269d1/attachment.html>