<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">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.<label></label><br>
<br>
On 2013年10月30日 21:10, Christopher Yeoh wrote:<br>
</div>
<blockquote
cite="mid:CANCY3ecG3dFUzAOP4RMXAuCn6yqeSySuDQgPRvG=Hx76hEbezw@mail.gmail.com"
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 moz-do-not-send="true"
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 class="im">> 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 moz-do-not-send="true"
href="https://docs.google.com/spreadsheet/ccc?key=0AmYuZ6T4IJETdEVNTWlYVUVOWURmOERSZ0VGc1BBQWc#gid=0">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 moz-do-not-send="true"
href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
<a moz-do-not-send="true"
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 class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
OpenStack-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a>
<a class="moz-txt-link-freetext" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a>
</pre>
</blockquote>
<br>
</body>
</html>