[openstack-dev] [keystone][api] Backwards incompatible changes based on config

Dean Troyer dtroyer at gmail.com
Mon Aug 7 12:33:04 UTC 2017


On Mon, Aug 7, 2017 at 4:00 AM, Chris Dent <cdent+os at anticdent.org> wrote:
> Many deployments are several months behind. If _all_ (or even many)
> deployments are that far behind, maybe we could consider saving ourselves
> some pain?

I would agree with this when we get some solid feedback on the impact.
We started with CD as one of the fundamental
constraints^H^H^H^H^Hgoals and to drop it should be a deliberate
decision.

In addition to direct deployments, I found things like this [0] in a
quick search for who is publicly saying they (still) do CD, it is a
category I had not considered before and makes me think that this kind
of decision has a wider impact range than we may be aware of.

Looking in https://www.openstack.org/analytics for the 2017 User
Survey shows no production deployments on "trunk" but of course that
doesn't mean there are none.  I wonder if deployments using CD are (or
have now) fallen behind similarly to what we know to be the case with
deployments on releases, only maybe not quite as far?

dt

[0] https://devops.com/automic-empowers-cloud-continuous-delivery-openstack-integration/

-- 

Dean Troyer
dtroyer at gmail.com



More information about the OpenStack-dev mailing list