<div dir="ltr"><div class="gmail_default" style="font-family:verdana,sans-serif">a huge +1!</div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">
thanks, chris, noticed the spreadsheet before, and have add some contents I have been working on. I think more people should know that, avoid conflicting.</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">
2013/10/31 Zhu Bo <span dir="ltr"><<a href="mailto:bozhu@linux.vnet.ibm.com" target="_blank">bozhu@linux.vnet.ibm.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
<div>hi, Chris thanks for your work.<br>
<br>
It's a good way. And how about creating a blue-print and putting
these link on it? Some guys have been familiar with looking for
work items from blue-print, and writing something in hacking
guide may be better.<div><div class="h5"><label></label><br>
<br>
On 2013Äê10ÔÂ30ÈÕ 21:10, Christopher Yeoh wrote:<br>
</div></div></div><div><div class="h5">
<blockquote type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">On Wed, Oct 30, 2013 at 11:18 PM,
Steven Hardy <span dir="ltr"><<a href="mailto:shardy@redhat.com" target="_blank">shardy@redhat.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On Wed, Oct 30, 2013 at
11:00:22PM +1030, Christopher Yeoh wrote:<br>
<snip><br>
<div>> I don't think blueprints/bugs work so<br>
> well at this, and I don't think we have anything
else setup at the moment,<br>
> so as a temporary measure I've created an etherpad
here:<br>
<br>
</div>
Can I ask why? Surely blueprints for new features (in
this case the<br>
feature is test coverage for $api) are exactly what the
normal openstack<br>
process dictates, and is what most folks are familiar
with?<br>
<br>
</blockquote>
<div><br>
</div>
<div>Just to be clear - Its not that I think that we
shouldn't have blueprints which covers the work being done
(we should!), but they don't work so well at allowing
people to see a good summary of what test coverage for an
API we have (some of which may have been done a long time
ago), what needs to be done and the quite fine grained
allocation of what people are working on. <br>
</div>
<div><br>
</div>
<div>For example, see the tempest coverage for the Nova v2
API spreadsheet: <a href="https://docs.google.com/spreadsheet/ccc?key=0AmYuZ6T4IJETdEVNTWlYVUVOWURmOERSZ0VGc1BBQWc#gid=0" target="_blank">https://docs.google.com/spreadsheet/ccc?key=0AmYuZ6T4IJETdEVNTWlYVUVOWURmOERSZ0VGc1BBQWc#gid=0</a><br>
</div>
<div><br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
Anyway, I added the keystone test I'm working on (which
has a BP) to the<br>
etherpad, and definitely +1 on not duplicating effort, by
whatever means ;)<br>
<br>
Steve<br>
<br>
_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</blockquote>
</div>
<br>
</div>
</div>
<br>
<fieldset></fieldset>
<br>
<pre>_______________________________________________
OpenStack-dev mailing list
<a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">OpenStack-dev@lists.openstack.org</a>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a>
</pre>
</blockquote>
<br>
</div></div></div>
<br>_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br><div dir="ltr"><div><b><font color="#000000" style="background-color:rgb(243,243,243)" face="courier new, monospace">---------------------------------------</font></b></div>
<div><font color="#0000ff" face="comic sans ms, sans-serif"><b>Lingxian Kong</b></font></div><div><font color="#ff00ff" face="comic sans ms, sans-serif">Huawei Technologies Co.,LTD.</font></div><div><font color="#ff00ff" face="comic sans ms, sans-serif">IT Product Line CloudOS PDU</font></div>
<div><font color="#ff00ff" face="comic sans ms, sans-serif">China, Xi'an</font></div><div><font color="#ff00ff" face="comic sans ms, sans-serif">Mobile: +86-18602962792</font></div><div><font color="#ff00ff" face="comic sans ms, sans-serif">Email: <a href="mailto:konglingxian@huawei.com" target="_blank">konglingxian@huawei.com</a>; <a href="mailto:anlin.kong@gmail.com" target="_blank">anlin.kong@gmail.com</a></font></div>
</div>
</div>