If projects that use neutron-lib want this specific version of neutron-lib then I guess that yes they need to update their requirements and then re-release... We already freezed releases bor lib and client-lib few days ago if the update is outside this scope (services or UI) then I think we could accept it, else it will require lot of re-release and I don't think we want to do that, especially now that branching of those is on the rails.

Le lun. 15 mars 2021 à 15:22, Matthew Thode <mthode@mthode.org> a écrit :

On 21-03-15 12:37:16, Slawek Kaplonski wrote:
> Hi,
>
> I'm raising this RFE to ask if we can release, and include new version of the
> neutron-lib in the Wallaby release.
> Neutron already migrated all our policy rules to use new personas like
> system-reader or system-admin. Recently Lance found bug [1] with those new
> personas.
> Fix for that is now merged in neutron-lib [2].
> This fix required bump the oslo_context dependency in lower-constraints and
> that lead us to bump many other dependencies versions. But in fact all those
> new versions are now aligned with what we already have in the Neutron's
> requirements so in fact neutron-lib was tested with those new versions of the
> packages every time it was run with Neutron master branch.
>
> I already proposed release patch for neutron-lib [3].
> Please let me know if I You need anything else regrarding this RFE.
>
> [1] https://launchpad.net/bugs/1918506
> [2] https://review.opendev.org/c/openstack/neutron-lib/+/780204
> [3] https://review.opendev.org/c/openstack/releases/+/780550
>
> --
> Slawek Kaplonski
> Principal Software Engineer
> Red Hat

It looks like there are a lot of places neutron-lib is still used. My
question here is if those projects need to update their requirements and
re-release?

--
Matthew Thode

Hervé Beraud

Senior Software Engineer at Red Hat

irc: hberaud

https://github.com/4383/

https://twitter.com/4383hberaud