Hi, Sphinx version 1.2 was just released and is not compatible with distutils in python 2.7. This causes all our doc builds to fail. Here is a change to stable/havana requirements to pin the version: https://review.openstack.org/#/c/61236/ If it lands, there will be automatic proposals to update requirements for all projects. Those will also need to land before any changes will be able to land on stable/havana branches. -Jim
2013/12/10 James E. Blair <jeblair@openstack.org>:
https://review.openstack.org/#/c/61236/
If it lands, there will be automatic proposals to update requirements for all projects. Those will also need to land before any changes will be able to land on stable/havana branches.
Would be nice if those automatic proposals used the same change-id https://review.openstack.org/#/q/I0487b4eca8f2755b882689289e3cdf429729b1fb,n... so we could track progress easily. I don't see them under https://review.openstack.org/#/q/status:open+branch:stable/havana,n,z and all docs stable bitrot jobs failed this morning! Cheers, Alan
FYIm, I got answers from SergeyLukjanov on #openstack-infra, thanks!
Would be nice if those automatic proposals used the same change-id https://review.openstack.org/#/q/I0487b4eca8f2755b882689289e3cdf429729b1fb,n... so we could track progress easily.
"Updated from global requirements" are batched and each gets separate changeid e.g. https://review.openstack.org/61277 so easy tracking single requirements update across projects and branches is currently not possible. While batch dependency updates are fine during development on master, we should consider pushing them as single changes to stable/*
I don't see them under https://review.openstack.org/#/q/status:open+branch:stable/havana,n,z and all docs stable bitrot jobs failed this morning!
They would showup under https://review.openstack.org/#/q/owner:jenkins+branch:stable/havana,n,z but automatic requirements updates for stable/havana are blocked on https://review.openstack.org/61304 Cheers, Alan
Alan Pevec <apevec@gmail.com> writes:
FYIm, I got answers from SergeyLukjanov on #openstack-infra, thanks!
Would be nice if those automatic proposals used the same change-id https://review.openstack.org/#/q/I0487b4eca8f2755b882689289e3cdf429729b1fb,n... so we could track progress easily.
"Updated from global requirements" are batched and each gets separate changeid e.g. https://review.openstack.org/61277 so easy tracking single requirements update across projects and branches is currently not possible. While batch dependency updates are fine during development on master, we should consider pushing them as single changes to stable/*
I don't see them under https://review.openstack.org/#/q/status:open+branch:stable/havana,n,z and all docs stable bitrot jobs failed this morning!
They would showup under https://review.openstack.org/#/q/owner:jenkins+branch:stable/havana,n,z but automatic requirements updates for stable/havana are blocked on https://review.openstack.org/61304
Also, they do all have the topic set to 'openstack/requirements' so you can search for: https://review.openstack.org/#/q/status:open+topic:openstack/requirements,n,... or https://review.openstack.org/#/q/status:open+branch:stable/havana+topic:open... -Jim
2013/12/11 James E. Blair <jeblair@openstack.org>:
https://review.openstack.org/#/q/status:open+branch:stable/havana+topic:open...
Stable-main team, please review above patches, they're blocking merges of recent CVE fixes which is blocking 2013.2.1 release. We need this merged to all projects participating in stable releases: nova, keystone, glance, neutron, cinder, horizon, heat and ceilometer. Cheers, Alan
The change for oslo.config says <1.2 but I thought we had to account for an alpha or beta release in that series that was published by saying something like <1.1.99. Am I misunderstanding the situation? On Thu, Dec 12, 2013 at 10:03 AM, Alan Pevec <apevec@gmail.com> wrote:
2013/12/11 James E. Blair <jeblair@openstack.org>:
https://review.openstack.org/#/q/status:open+branch:stable/havana+topic:open...
Stable-main team, please review above patches, they're blocking merges of recent CVE fixes which is blocking 2013.2.1 release. We need this merged to all projects participating in stable releases: nova, keystone, glance, neutron, cinder, horizon, heat and ceilometer.
Cheers, Alan
_______________________________________________ Openstack-stable-maint mailing list Openstack-stable-maint@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-stable-maint
2013/12/12 Doug Hellmann <doug.hellmann@dreamhost.com>:
The change for oslo.config says <1.2 but I thought we had to account for an alpha or beta release in that series that was published by saying something like <1.1.99. Am I misunderstanding the situation?
You're right, but in gate it should be ok since it's using pypi mirror without prereleases, side-effect of using pip 1.4 which ignores them without --pre option. Issue would be for local builds where tox.ini changes like[1] are required, this is being pushed separately, but not critical for 2013.2.1 release. Cheers, Alan [1] https://review.openstack.org/61507
On Thu, Dec 12, 2013 at 10:53 AM, Alan Pevec <apevec@gmail.com> wrote:
2013/12/12 Doug Hellmann <doug.hellmann@dreamhost.com>:
The change for oslo.config says <1.2 but I thought we had to account for an alpha or beta release in that series that was published by saying something like <1.1.99. Am I misunderstanding the situation?
You're right, but in gate it should be ok since it's using pypi mirror without prereleases, side-effect of using pip 1.4 which ignores them without --pre option. Issue would be for local builds where tox.ini changes like[1] are required, this is being pushed separately, but not critical for 2013.2.1 release.
OK, thanks for clearing that up. Doug
Cheers, Alan
participants (4)
-
Alan Pevec
-
Doug Hellmann
-
James E. Blair
-
jeblair＠openstack.org