<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif;">
<div>Hey folks,</div>
<div><br>
</div>
<div>As we split out the repository per our unanimous vote several months ago, we have a choice to make (I think, assuming we are given latitude of the release team who is in the cc list) as to which version to call kolla-ansible.</div>
<div><br>
</div>
<div>My personal preference is to completely retag our newly split repo with all old tags from kolla git revisions up to version 3.0.z. The main rationale I can think of is kolla-ansible 1 = liberty, 2 = mitaka, 3 = newton. I think calling kolla-ansible 1.0
= newton would be somewhat confusing, but we could do that as well.</div>
<div><br>
</div>
<div>The reason the repository needs to be retagged in either case is to generate release artifacts (tarballs, pypi, etc).</div>
<div><br>
</div>
<div>Would also like feedback from the release team on what they think is a best practice here (we may be breaking new ground for the OpenStack release team, maybe not – is there prior art here?)</div>
<div><br>
</div>
<div>For a diagram (mostly for the release team) of the repository split check out:</div>
<div><a href="https://www.gliffy.com/go/share/sg9fc5eg9ktg9binvc89">https://www.gliffy.com/go/share/sg9fc5eg9ktg9binvc89</a></div>
<div><br>
</div>
<div>Thanks!</div>
<div>-steve</div>
<div><br>
</div>
<div>
<div id="MAC_OUTLOOK_SIGNATURE"></div>
</div>
</body>
</html>