Hi folks, There's a feature or two that are pending to be delivered in Mitaka [1,2], and those involve changes to both the server and client sides. Ideally we'd merge both sides in time for Mitaka RC and that implies that we would be able to release a new version of the client including changes [3,4]. This is especially important since a new client release would be beneficial to improving test coverage as needed by [5].
Considering what we released already, and what the tip of master is for the client [6], I can't see any side effect that a new neutronclient release may introduce. Having said that, I am leaning towards the all-or-none approach, but the 'all' approach is predicated on the fact that we are indeed allowed to release a new client and touch the global requirements. What's the release team's recommendation? Based on it, we may want to decide to defer these to as soon as N master opens up. Many thanks, Armando [1] https://review.openstack.org/#/q/topic:bug/1468353 [2] https://review.openstack.org/#/q/topic:bug/1521783 [3] https://review.openstack.org/#/c/254280/ [4] https://review.openstack.org/#/c/288187/ [5] https://review.openstack.org/#/c/288392/ [6] https://github.com/openstack/python-neutronclient/commit/8460b0dbb354a304a112be13c63cb933ebe1927a
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
