settingsLogin | Registersettings

[openstack-dev] [requirements] Projects holding back requirements updates

0 votes

This is just a friendly reminder that without a release from master, if
your project still caps a requirement then it may be either holding back
a package or not be included in upper-constraints updates.

http://logs.openstack.org/76/466476/5/check/gate-requirements-tox-py27-check-uc-ubuntu-xenial/d71b8f6/console.html#_2017-05-22_09_38_53_142301

http://logs.openstack.org/76/466476/4/check/gate-requirements-tox-py27-check-uc-ubuntu-xenial/27cb570/console.html#_2017-05-21_09_00_14_624413

The following packages are taken from those lists and holding back
requirements updates.

Holding back updates from upstream to be consumed by other openstack
projects:

mistral - holding back sqlalchemy (no release that uncaps sqlalchemy)
django-openstack-auth - holding back django

Being held back from being updated and being consumed, all these is
because they don't have a release that uncaps pbr.

mistral
os-apply-config
os-collect-config
os-refresh-config
os-vif

If these projects could make a release (something fetchable by pypi) off
of master that's all that's needed. They all have updated their
requirements in master, just no consumable release.

--
Matthew Thode (prometheanfire)


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

asked May 26, 2017 in openstack-dev by prometheanfire_at_ge (6,880 points)   1 4 5

4 Responses

0 votes

Tagging with tripleo and heat teams for the os-*-config projects. I'm
not sure which owns them now, but it sounds like we need a new release.

On 05/22/2017 10:32 AM, Matthew Thode wrote:
This is just a friendly reminder that without a release from master, if
your project still caps a requirement then it may be either holding back
a package or not be included in upper-constraints updates.

http://logs.openstack.org/76/466476/5/check/gate-requirements-tox-py27-check-uc-ubuntu-xenial/d71b8f6/console.html#_2017-05-22_09_38_53_142301

http://logs.openstack.org/76/466476/4/check/gate-requirements-tox-py27-check-uc-ubuntu-xenial/27cb570/console.html#_2017-05-21_09_00_14_624413

The following packages are taken from those lists and holding back
requirements updates.

Holding back updates from upstream to be consumed by other openstack
projects:

mistral - holding back sqlalchemy (no release that uncaps sqlalchemy)
django-openstack-auth - holding back django

Being held back from being updated and being consumed, all these is
because they don't have a release that uncaps pbr.

mistral
os-apply-config
os-collect-config
os-refresh-config
os-vif

If these projects could make a release (something fetchable by pypi) off
of master that's all that's needed. They all have updated their
requirements in master, just no consumable release.


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
responded May 25, 2017 by Ben_Nemec (19,660 points)   2 3 4
0 votes

On Thu, May 25, 2017 at 03:15:13PM -0500, Ben Nemec wrote:
Tagging with tripleo and heat teams for the os-*-config projects. I'm not
sure which owns them now, but it sounds like we need a new release.

I think they're still owned by the TripleO team, but we missed them in the
pike-1 release, I pushed this patch aiming to resolve that:

https://review.openstack.org/#/c/468292/

Steve


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
responded May 26, 2017 by Steven_Hardy (16,900 points)   2 7 12
0 votes

On 05/26/2017 04:22 AM, Steven Hardy wrote:
On Thu, May 25, 2017 at 03:15:13PM -0500, Ben Nemec wrote:

Tagging with tripleo and heat teams for the os-*-config projects. I'm not
sure which owns them now, but it sounds like we need a new release.

I think they're still owned by the TripleO team, but we missed them in the
pike-1 release, I pushed this patch aiming to resolve that:

https://review.openstack.org/#/c/468292/

Thanks, Steve. Looks like Jenkins isn't happy with it though. :-/


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
responded May 26, 2017 by Ben_Nemec (19,660 points)   2 3 4
0 votes

On Fri, May 26, 2017 at 11:22 AM, Steven Hardy shardy@redhat.com wrote:
On Thu, May 25, 2017 at 03:15:13PM -0500, Ben Nemec wrote:

Tagging with tripleo and heat teams for the os-*-config projects. I'm not
sure which owns them now, but it sounds like we need a new release.

I think they're still owned by the TripleO team, but we missed them in the
pike-1 release, I pushed this patch aiming to resolve that:

Indeed, we missed it, apologize for that.

Thanks!

Steve


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

--
Emilien Macchi


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
responded May 26, 2017 by emilien_at_redhat.co (36,940 points)   3 8 13
...