Open Stack

Just confirming and closing things out. We did not receive any negative
responses to the plan below, so a little earlier today I approved the mentioned
patch and we cut releases and branches for all libs.

The next step if for these new versions to pass CI and get FFEs to raise the
upper constraints for them past our requirements freeze. That official request
will be coming shortly.

Sean

On Wed, Jan 31, 2018 at 03:03:44PM -0600, Sean McGinnis wrote:
> While reviewing Queens release deliverables and preparing missing stable/queens
> branches, we have identified several libraries that have not had any Queens
> releases.
> 
> In the past, we have stated we would force a release for any missing
> deliverables in order to have a clear branching point. We considered tagging
> the base of the stable/pike branch again and starting a new stable/queens
> branch from there, but that doesn't work for several technical reasons the most
> important of which is that the queens release would not include any changes
> that had been backported to stable/pike, and we have quite a few of those. So,
> we are left with 2 choices: do not release these libraries at all for queens,
> or release from HEAD on master. Skipping the releases entirely will make it
> difficult to provide bug fixes in these libraries over the life of the queens
> release so, although it is potentially disruptive, we plan to release from HEAD
> on master. We will rely on the constraints update mechanism to protect the gate
> if the new releases introduce bugs and teams will be able to fix those problems
> on the new stable/queens branch and then release a new version.
> 
> See https://review.openstack.org/#/c/539657/ and the notes below for details of
> what will be tagged.
> 
> ceilometermiddleware
> --------------------
> 
> Mostly doc and CI related changes, but the "Retrieve project id to ignore from
> keystone" commit (e2bf485) looks like it may be important.
> 
> Heat
> ----
> 
> heat-translator
> There are quite a few bug fixes and feature changes merged that have not been
> released. It is currently marked with a type of "library", but we will change
> this to "other" and require a release by the end of the cycle (see
> https://review.openstack.org/#/c/539655/ for that change). Based on the README
> description, this appears to be a command line and therefore should maybe have
> a type of "client-library", but "other" would work as far as release process
> goes. Since this is kind of a special command line, perhaps "other" would be
> the correct type going forward, but we will need input from the Heat team on
> that.
> 
> python-heatclient
> Only reno updates, so a new release on master should not be very disruptive.
> 
> tosca-parser
> Several unreleased bug fixes and feature changes. Consumed by heat-translator
> and tacker, so there is some risk in releasing it this late.
> 
> 
> Mistral
> -------
> 
> mistral-lib
> Mostly packaging and build changes, with a couple of fixes. It is used by
> mistral and tripleo-common.
> 
> SDK
> ---
> 
> requestsexceptions
> No changes this cycle. We will branch stable/queens from the same point as
> stable/pike.
> 
> Searchlight
> -----------
> 
> python-searchlightclient
> Only doc and g-r changes. Since the risk here is low, we are going to release
> from master and branch from there.
> 
> Senlin
> ------
> 
> python-senlinclient
> Just one bug fix. This is a dependency for heat, mistral, openstackclient,
> python-openstackclient, rally, and senlin-dashboard. The one bug fix looks
> fairly safe though, so we are going to release from master and branch from
> there.
> 
> Tacker
> ------
> 
> python-tackerclient
> Many feature changes and bug fixes. This impacts mistral and tacker.
> 
> Tricircle
> ---------
> 
> python-tricircleclient
> One feature and several g-r changes.
> 
> 
> Please respond here, comment on the patch, or hit us up in #openstack-release
> if you have any questions or concerns.
> 
> Thanks,
> Sean McGinnis (smcginnis)
> 
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev