<div dir="ltr">Cool! Thanks for the work!<br><div class="gmail_extra"><br><div class="gmail_quote">2015-07-21 22:51 GMT+08:00 Ed Leafe <span dir="ltr"><<a href="mailto:ed@leafe.com" target="_blank">ed@leafe.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">-----BEGIN PGP SIGNED MESSAGE-----<br>
Hash: SHA512<br>
<br>
One of the tasks we have now that the 2.1 microversion API has become<br>
the default is cleaning up the old references to 'v3', and moving all<br>
the v2 code to a separate directory. This is needed because the<br>
current arrangement is confusing, especially to developers new to the<br>
code.<br>
<br>
There is a patch that starts the process [1], but since it touches a<br>
whole lot of test code, when it merges it will throw most patches into<br>
a merge conflict. The same thing will happen with each subsequent<br>
patch. Rather that inflict multiple painful merge conflicts, it would<br>
be better to merge all the changes at once, and only require one rebase.<br>
<br>
Since we have a bunch of the development team together for the<br>
mid-cycle, we're planning on working on this tomorrow, and merging the<br>
patches together. So consider this a courtesy notice that we're gonna<br>
break your stuff. :)<br>
<br>
[1] <a href="https://review.openstack.org/193725" rel="noreferrer" target="_blank">https://review.openstack.org/193725</a><br>
<br>
- --<br>
<br>
- -- Ed Leafe<br>
-----BEGIN PGP SIGNATURE-----<br>
Version: GnuPG v2<br>
Comment: GPGTools - <a href="https://gpgtools.org" rel="noreferrer" target="_blank">https://gpgtools.org</a><br>
Comment: Using GnuPG with Thunderbird - <a href="http://www.enigmail.net/" rel="noreferrer" target="_blank">http://www.enigmail.net/</a><br>
<br>
iQIcBAEBCgAGBQJVrlx9AAoJEKMgtcocwZqL9SQP/3JMFtpOPNRlndap3pZqfpqB<br>
hdvYr36Qq9Yy3CNSGPQQ3a3Pj06/AVWsugtfnL5lMh7fkRmaTbCSMs76fKPyVlj1<br>
MJTBPM29scKBiX81H1hl8IBHCzPz1BCgyFIqZn9hUfThbI9IcEZED/lchDF4iG1o<br>
IMMre0Tda0QYtqAJCkLdRoeK0z1EKl2+BJMCet0OdwbfoHemGdGWLXa9IKmZSdkv<br>
I3nznygIeWFrQ3NzDyh6TCV2rTLbyQL3hB+LU5nMglK1wEjG+DqE52lKAAeWBoIU<br>
5o+9lQMV7AFbIK/Zq56iGdhe+Oj7vZLlC/rbmcftiVswg6+iCazSHlk9KKFqu0Sy<br>
Lx4AIaSXeetZjt/LKSHfMyjopXoA3RhrGbEc0FTNzJLYF7IB2N/Ji5tvGTwrGZIh<br>
uACJHkOZRJfrJDsgnx1xKnzTwreXp90Z6l0wnEBjDZLPpPggo+sYoHn34IOVZ2eO<br>
SYqI4GEYe1mKu3ZzHq2w9geH2EK1xKm3zEasuh9cYeuZcA7VsaGwrKbmx4vuPuSy<br>
a5v3ZYZeE6n083F9KcxkJDTuUqvgGe6887i6y+HA5WItbgSp1vq45OxSe4yp16F7<br>
kGfk7HfLZHE5U6u8qx1fZdM7qY6+pJ1wFFnM7TRlQ4ld1QTFIaBd3gRQkBQO9RnL<br>
Y977GST224iGvKYtTQGu<br>
=N/Y2<br>
-----END PGP SIGNATURE-----<br>
<br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</blockquote></div><br></div></div>