<br><br><div class="gmail_quote">On Mon, Nov 19, 2012 at 7:21 AM, Sean Dague <span dir="ltr"><<a href="mailto:sdague@linux.vnet.ibm.com" target="_blank">sdague@linux.vnet.ibm.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">On 11/19/2012 09:35 AM, Thierry Carrez wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Gary Kotton wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
In the past we have had specific days set aside for bug triage. How<br>
about we make a concerted effort to have a test day for the following:<br>
- stable releases (if I understand correctly the up and coming one<br>
is on the 22nd too)<br>
- release cycles (up and coming is the 22nd)<br>
This will hopefully help up provide a more stable, robust and reliable<br>
solution. In addition to this it will also enable us to identify and<br>
isolate problems prior to them being found in the "real world".<br>
Any ideas or comments?<br>
</blockquote>
<br>
I think we are in two different scenarios with stable releases and<br>
milestone deliveries.<br>
<br>
Stable releases are directly used by our users once they are out, so if<br>
we want to specifically test them, it makes sense to do that before they<br>
are released. There usually is a call for testing in the days before the<br>
stable release update is issued, we could reuse that.<br>
<br>
Milestones from the current development cycle, on the other hand, are<br>
specifically there to tag a specific point in development to help<br>
testing and comparing results ("bug not present in folsom-2", "feature<br>
added in folsom-3"...). So we could imagine that a testing day is done<br>
right *after* the milestone is cut to give a common (and static) testing<br>
base for everyone participating.<br>
<br>
Thoughts?<br>
</blockquote>
<br></div>
Testing days are cool, and I think if someone wants to organize it, more power to them.<br>
<br>
What I'd really like to see though, is a Test Writing day. Tempest's test set has been pretty static recently, and it would be nice to get more folks used to writing a test or two, especially as we're looking to increase the value of the test gate.<br>
</blockquote><div><br></div><div>+1 </div><div><br></div><div>~Joe Gordon</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Run a test and your ensure things are stable today, write a test and you ensure they're stable tomorrow.<span class="HOEnZb"><font color="#888888"><br>
<br>
-Sean<br>
<br>
-- <br>
Sean Dague<br>
IBM Linux Technology Center<br>
email: <a href="mailto:sdague@linux.vnet.ibm.com" target="_blank">sdague@linux.vnet.ibm.com</a><br>
alt-email: <a href="mailto:sldague@us.ibm.com" target="_blank">sldague@us.ibm.com</a></font></span><div class="HOEnZb"><div class="h5"><br>
<br>
<br>
______________________________<u></u>_________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">OpenStack-dev@lists.openstack.<u></u>org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/<u></u>cgi-bin/mailman/listinfo/<u></u>openstack-dev</a><br>
</div></div></blockquote></div><br>