[openstack-dev] What's happening with stable release management?
Morgan Fainberg
morgan.fainberg at gmail.com
Fri Aug 8 18:50:15 UTC 2014
Hi Thomas,
I think this looks like the issue outlined here http://lists.openstack.org/pipermail/openstack/2014-August/008788.html .
Keystonemiddleware should not be part of stable/icehouse requirements for Keystone as that was added in Juno (and the other
changes look similar to the Juno requirements for keystone as well).
Cheers,
Morgan
—
Morgan Fainberg
-----Original Message-----
From: Thomas Goirand <zigo at debian.org>
Reply: OpenStack Development Mailing List (not for usage questions) <openstack-dev at lists.openstack.org>>
Date: August 8, 2014 at 10:32:15
To: OpenStack Development Mailing List <openstack-dev at lists.openstack.org>>
Subject: [openstack-dev] What's happening with stable release management?
> Hi,
>
> For updating keystone from 2014.1.1 to 2014.1.2, I had to:
>
> - Upgrade oslo-config from 1.2.1 to 1.4.0.0~a3
> - Upgrade oslo.messaging from 1.3.0~a9 to 1.4.0.0~a3
> - Upgrade python-six from 1.6 to 1.7
> - Upgrade python-pycadf from 0.4 to 0.5.1
> - Add python-ldappool
> - Add python-oslo.db
> - Add python-oslo.i18n
> - Add python-keystonemiddleware, which needs python-crypto >= 2.6
> (previously, 2.5 was enough)
>
> So, we have 5 major Python module upgrades, and 4 completely new
> libraries which were not there in 2014.1.1. Some of the changes aren't
> small at all.
>
> I'm sure that there's very valid reasons for each of the upgrades or
> library addition, but I don't think that it is overall reasonable. If
> this was to happen during the freeze of Debian, or worse, after a
> release, upgrading all of this would be a nightmare, and I'm sure that
> the Debian release team would simply refuse.
>
> Should I assign myself to program a robot which will vote -1 on all
> change on the stable/Icehouse global-requirements.txt file? Or is sanity
> still possible in OpenStack? :)
>
> It is my opinion that we need to review our release process for the
> stable releases, policy for requirement changes, and need to adopt a way
> more conservative attitude.
>
> Cheers,
>
> Thomas Goirand (zigo)
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
More information about the OpenStack-dev
mailing list