[neutron] Bumping of requirements on RDO before bumping them on Neutron
Brian Haley
haleyb.dev at gmail.com
Tue Jan 31 22:17:10 UTC 2023
Hi Elvira,
Thanks for starting a discussion on this.
On 1/31/23 12:02 PM, Elvira Garcia Ruiz wrote:
> Hi Neutrinos!
>
> RDO folks proposed that, in order to be able to correctly build CI
> gates for testing, it would be nice if we tried to update the
> neutron-distgit requirement file when we want to update the minimal
> version of a dependency before merging it on our repository.
> This would allow them to realize whether they need or not to update
> any Fedora package. In order to do that, we just need to send a small
> commit to their repository [0]. You can use your GitHub account for
> the login.
I do feel it's a good idea for downstream maintainers to be informed
when we change library or binary dependencies on the master branch, we
have actually been bit by this recently as well when ovsdb-client
started being used in [0].
My only concern here is this is leaving out the other distros like
Ubuntu, Debian, etc., so I'm wondering if there is a more generic way?
We could do something like send an email to this list at cycle
milestones that a maintainer might watch for to then trigger some
downstream work, but that is after-the-fact and not before as you are
suggesting. I just don't think having developers update all the distros
is scalable when there are more than one.
Of course this would affect more than Neutron as well.
Thoughts?
-Brian
[0] https://review.opendev.org/c/openstack/neutron/+/860275
> Here you can find an example for pyroute2 in RDO [1] and the
> respective pyroute2 bump in Neutron [2].
>
> Regards!
> Elvira García (elvira)
>
> [0] https://review.rdoproject.org/r/openstack/neutron-distgit
404 :(
> [1] https://review.rdoproject.org/r/c/openstack/neutron-distgit/+/46809
> [2] https://review.opendev.org/c/openstack/neutron/+/870963
More information about the openstack-discuss
mailing list