<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
We're on a 3 week countdown before the freeze on client libraries[1]
and I'd like to aim for a python-heatclient-1.0.0 to be released
with the new openstackclient commands.<br>
<br>
However there are currently ~25 of these changes needing reviews,
and they all cause merge conflicts with each other when they append
to the entry point list in setup.cfg.<br>
<br>
I'd like to suggest some coordination to minimize the chances of
these merge conflicts:<br>
- we should use strict sorting of the openstack.orchestration.v1
list as per this change [2]<br>
- existing changes should be rebased so that they add their entries
in sort order<br>
- ideally, related commands from the same author can be combined
into a single series of changes (2 - 5 changes long)<br>
<br>
With this there should be less churn on getting these changes to
land, which will hopefully encourage some more reviews too.<br>
<br>
[1]
<a class="moz-txt-link-freetext" href="http://lists.openstack.org/pipermail/openstack-dev/2016-February/085705.html">http://lists.openstack.org/pipermail/openstack-dev/2016-February/085705.html</a><br>
<font face="Hack">[2] <a class="moz-txt-link-freetext" href="https://review.openstack.org/#/c/277595/">https://review.openstack.org/#/c/277595/</a></font><br>
</body>
</html>