<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
</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>Technical Committee,</div>
<div><br>
</div>
<div>Please accept my change prior to our April 8th deadline for tagging Mitaka 2.0.0 of Kolla. To be clear, this is a clunky workaround but I feel as though we are not permitted to participate in the marketing that takes place on the releases website, and
this is the lesser of that evil.</div>
<div><br>
</div>
<div>The review is here:</div>
<div>
<p style="margin: 0px; font-size: 11px; line-height: normal; font-family: Menlo;">
<span style="font-variant-ligatures: no-common-ligatures"><a href="https://review.openstack.org/300752">https://review.openstack.org/300752</a></span></p>
<p style="margin: 0px; font-size: 11px; line-height: normal; font-family: Menlo;">
<br>
</p>
<p style="margin: 0px; font-size: 11px; line-height: normal; font-family: Menlo;">
I'd like to do it right, and remove the red tape surrounding deployment projects first, but from what I've gathered on the mailing list (sorry no references) and in various reviews I've been involved with, solving the red tape related to deployment projects
won't happen in time to apply this tag to our repository as this tag operates on a 7 day lazy consensus model, which means Kolla can still possibly gain access to the marketing resources of the releases project team's website.</p>
<p style="margin: 0px; font-size: 11px; line-height: normal; font-family: Menlo;">
<br>
</p>
<p style="margin: 0px; font-size: 11px; line-height: normal; font-family: Menlo;">
Regards</p>
<p style="margin: 0px; font-size: 11px; line-height: normal; font-family: Menlo;">
-steve</p>
</div>
</body>
</html>