openstack team mailing list archive
-
openstack team
-
Mailing list archive
-
Message #02896
Re: Diablo unit testing
-
To:
openstack@xxxxxxxxxxxxxxxxxxx
-
From:
Thierry Carrez <thierry@xxxxxxxxxxxxx>
-
Date:
Fri, 17 Jun 2011 09:05:53 +0200
-
In-reply-to:
<108211607B558E4585B627A795F6CB1B081A7CF8@SG1RD3XVS271.red003.local>
-
Organization:
OpenStack
-
User-agent:
Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.17) Gecko/20110516 Thunderbird/3.1.10
Rohit Karajgi wrote:
> Hello Vish,
>
> We at NTT are supporting the unit-testing efforts for Diablo as part of the related blueprints. We are currently in the process of expanding the Unit Test suite for Libvirt.
> How can we contribute these efforts and source code to the community? Can we have a related branch for the existing blueprints or a separate blueprint for this activity?
>
> Please let me know your thoughts.
It's a bit difficult to track generic (but necessary) efforts like this.
We can use a generic blueprint (like [1]) but since the work is never
totally "completed" it's not really efficient.
[1] https://blueprints.launchpad.net/nova/+spec/unittest-coverage
I think we have three options: create a Diablo-specific unittest
blueprint (to which you could attach your own work), create an
NTT-specific blueprint about libvirt unittests (that we would target to
Diablo), or not track it using blueprints and just submit branches for
merging.
Vish, any preference ?
--
Thierry Carrez (ttx)
Release Manager, OpenStack
References