<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">But I do think running a job with lowest version may still help a developer realize that a feature in the latest library is not available in an older supported version. The person can then bump up the library's min version in the requirements. Today, it;s not possible to find this out until someone else runs into an issue with the older lib.<div><br></div><div>Ref:- I have noticed some bugs in the past and I did <a href="http://lists.openstack.org/pipermail/openstack-infra/2014-January/000703.html">post</a> about this to openstack-infra. From Jeremy Stanley's comment on that thread, I understand that it may be tough to setup it up this way due to transitive dependencies. <div><br></div><div><div>-Sabari</div><div><br><div><div>On Feb 20, 2014, at 3:06 PM, Sean Dague wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div>On 02/20/2014 05:50 PM, Christopher Yeoh wrote:<br><blockquote type="cite">On Thu, 20 Feb 2014 14:45:03 -0500<br></blockquote><blockquote type="cite">Sean Dague <<a href="mailto:sean@dague.net">sean@dague.net</a>> wrote:<br></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">So I'm one of the first people to utter "if it isn't tested, it's<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">probably broken", however I also think we need to be realistic about<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">the fact that if you did out the permutations of dependencies and<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">config options, we'd have as many test matrix scenarios as grains of<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">sand on the planet.<br></blockquote></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">I think it makes sense to at test with all the most recent versions.<br></blockquote><blockquote type="cite">Perhaps all the lowest as well, though I'm not sure how common that<br></blockquote><blockquote type="cite">configuration would really be. And we can't do all of the various<br></blockquote><blockquote type="cite">combinations. <br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">But how about testing on a periodic job the version<br></blockquote><blockquote type="cite">configurations used by some of the major distros? So we know on which<br></blockquote><blockquote type="cite">distros we're going to be broken on by default (if we don't get around<br></blockquote><blockquote type="cite">to fixing them straight away) which will really help inform those<br></blockquote><blockquote type="cite">trying out the latest from git. Or are the distros doing this anyway<br></blockquote><blockquote type="cite">(either way having the info public and feeding back to our bug tracker<br></blockquote><blockquote type="cite">would be handy).<br></blockquote><br>Honestly, I think our experience in even doing a homogenous gate means I<br>think we should let the distros come in with 3rd party testing on those<br>results. Because we don't really have the bw, in either people or<br>machines, to explode that matrix much in infra.<br><br><span class="Apple-tab-span" style="white-space:pre"> </span>-Sean<br><br>-- <br>Sean Dague<br>Samsung Research America<br><a href="mailto:sean@dague.net">sean@dague.net</a> / <a href="mailto:sean.dague@samsung.com">sean.dague@samsung.com</a><br><a href="https://urldefense.proofpoint.com/v1/url?u=http://dague.net/&k=oIvRg1%2BdGAgOoM1BIlLLqw%3D%3D%0A&r=t%2BccgWNa3RGhEJzfoLbZKcoWP6fDp0ZLoIyTd0CiIdk%3D%0A&m=kRy3u472erydn9aD1jOg%2FCQqzv1p0pQeNd%2BI8WXeZLk%3D%0A&s=493bac7a717a985bdb4d64eca320969ecb2a6df00d7ee8f5d8bcaf895dd24fe8">https://urldefense.proofpoint.com/v1/url?u=http://dague.net/&k=oIvRg1%2BdGAgOoM1BIlLLqw%3D%3D%0A&r=t%2BccgWNa3RGhEJzfoLbZKcoWP6fDp0ZLoIyTd0CiIdk%3D%0A&m=kRy3u472erydn9aD1jOg%2FCQqzv1p0pQeNd%2BI8WXeZLk%3D%0A&s=493bac7a717a985bdb4d64eca320969ecb2a6df00d7ee8f5d8bcaf895dd24fe8</a><br><br>_______________________________________________<br>OpenStack-dev mailing list<br>OpenStack-dev@lists.openstack.org<br>https://urldefense.proofpoint.com/v1/url?u=http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev&k=oIvRg1%2BdGAgOoM1BIlLLqw%3D%3D%0A&r=t%2BccgWNa3RGhEJzfoLbZKcoWP6fDp0ZLoIyTd0CiIdk%3D%0A&m=kRy3u472erydn9aD1jOg%2FCQqzv1p0pQeNd%2BI8WXeZLk%3D%0A&s=d484eedf637b01155f20eeda79378a9d506d6a39060517e70e868dcab571f3c6<br></div></blockquote></div><br></div></div></div></body></html>