<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;" class="">Doug,<div class=""><br class=""></div><div class="">python-mistralclient-1.1.0 (also on pypi) is the final release for Liberty. Here’s the patch updating global-requirements.txt: <a href="https://review.openstack.org/#/c/225330/" class="">https://review.openstack.org/#/c/225330/</a> (upper-constraints.txt should be soon updated automatically, in my understanding)</div><div class=""><br class=""></div><div class="">I really apologize because I should have probably followed ML better and attended corresponding meetings in order to know all of this release management stuff. But I still have a number questions on release management like:</div><div class=""><ul class="MailOutline"><li class="">So far I have been doing release management for Mistral myself (~2 years), and the last year I’ve been trying to be aligned with OpenStack schedule. In may 2015 Mistral was accepted into Big Tent so does that mean I’m not longer responsible for doing that? Or I can still do it on my own? Even with final Mistral client for Liberty I’ve done it just myself (didn’t create a stable branch though yet), maybe I shouldn’t have. Clarifications would be helpful.</li><li class="">Same question about stable branches.</li><li class="">Does this all apply to all Big Tent projects?</li><li class="">What exactly is upper-constraints.txt for? I’m still not sure why global-requirements.txt is not enough.</li><li class="">What’s the best source of info about release management? Is it complete?</li></ul></div><div class=""><br class=""></div><div class="">Sorry for asking this probably basic stuff.</div><div class=""><br class=""></div><div class="">Let me know if some of what I’ve done is wrong. It’s a late night here but I’ll check ML the first thing in the morning just in case.</div><div class=""><br class=""></div><div class="">Thanks</div><div class=""><br class=""><div class="">
<div class="">Renat Akhmerov</div><div class="">@ Mirantis Inc.</div><div class=""><br class=""></div><br class="Apple-interchange-newline">
</div>
<br class=""><div><blockquote type="cite" class=""><div class="">On 15 Sep 2015, at 22:24, Nikhil Komawar <<a href="mailto:nik.komawar@gmail.com" class="">nik.komawar@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">Hi Doug,<br class=""><br class="">And it would be good to lock in on glance_store (if it applies to this<br class="">email) 0.9.1 too. (that's on pypi)<br class=""><br class="">On 9/14/15 9:26 AM, Kuvaja, Erno wrote:<br class=""><blockquote type="cite" class="">Hi Doug,<br class=""><br class="">Please find python-glanceclient 1.0.1 release request <a href="https://review.openstack.org/#/c/222716/" class="">https://review.openstack.org/#/c/222716/</a><br class=""><br class="">- Erno<br class=""><br class=""><blockquote type="cite" class="">-----Original Message-----<br class="">From: Doug Hellmann [<a href="mailto:doug@doughellmann.com" class="">mailto:doug@doughellmann.com</a>]<br class="">Sent: Monday, September 14, 2015 1:46 PM<br class="">To: openstack-dev<br class="">Subject: [openstack-dev] [all][ptl][release] final liberty cycle client library<br class="">releases needed<br class=""><br class="">PTLs and release liaisons,<br class=""><br class="">In order to keep the rest of our schedule for the end-of-cycle release tasks,<br class="">we need to have final releases for all client libraries in the next day or two.<br class=""><br class="">If you have not already submitted your final release request for this cycle,<br class="">please do that as soon as possible.<br class=""><br class="">If you *have* already submitted your final release request for this cycle,<br class="">please reply to this email and let me know that you have so I can create your<br class="">stable/liberty branch.<br class=""><br class="">Thanks!<br class="">Doug<br class=""><br class="">__________________________________________________________<br class="">________________<br class="">OpenStack Development Mailing List (not for usage questions)<br class="">Unsubscribe: OpenStack-dev-<br class=""><a href="mailto:request@lists.openstack.org" class="">request@lists.openstack.org</a>?subject:unsubscribe<br class=""><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" class="">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br class=""></blockquote>__________________________________________________________________________<br class="">OpenStack Development Mailing List (not for usage questions)<br class="">Unsubscribe: <a href="mailto:OpenStack-dev-request@lists.openstack.org" class="">OpenStack-dev-request@lists.openstack.org</a>?subject:unsubscribe<br class=""><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" class="">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br class=""></blockquote><br class="">-- <br class=""><br class="">Thanks,<br class="">Nikhil<br class=""><br class=""><br class="">__________________________________________________________________________<br class="">OpenStack Development Mailing List (not for usage questions)<br class="">Unsubscribe: <a href="mailto:OpenStack-dev-request@lists.openstack.org" class="">OpenStack-dev-request@lists.openstack.org</a>?subject:unsubscribe<br class=""><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" class="">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br class=""></div></blockquote></div><br class=""></div></body></html>