[all] Dropping lower constraints testing (WAS: Re: [stable][requirements][neutron] Capping pip in stable branches or not)
Goutham Pacha Ravi
gouthampravi at gmail.com
Fri Dec 11 21:06:31 UTC 2020
I hope you won't mind me shifting this discussion to [all] - many projects
have had to make changes due to the dependency resolver catching some of
our uncaught lies.
In manila, i've pushed up three changes to fix the CI on the main,
stable/victoria and stable/ussuri  branches. I used fungi's method of
installing things and playing whack-a-mole  and Brain
Rosmaita's approach  of taking the opportunity to raise the minimum
required packages for Wallaby. However, this all seems kludgy maintenance -
and possibly no-one is benefitting from the effort we're putting into this
as called out.
Can more distributors and deployment tooling folks comment?
On Fri, Dec 11, 2020 at 12:51 PM Sorin Sbarnea <ssbarnea at redhat.com> wrote:
> Jeremy nailed it very well.
> Tripleo already removed lower-constraints from most places (some changes
> may be still waiting to be gated).
> Regarding decoupling linting from test-requirements: yes! This was already
> done by some when conflicts appeared. For old branches I personally do not
> care much even if maintainers decide to disable linting, their main benefit
> is on main branches.
> On Fri, 11 Dec 2020 at 18:14, Radosław Piliszek <
> radoslaw.piliszek at gmail.com> wrote:
>> On Fri, Dec 11, 2020 at 5:16 PM Ghanshyam Mann <gmann at ghanshyammann.com>
>> > Maintaining it up to date is not so worth compare to the effort it is
>> taking. I will also suggest to
>> > remove this.
>> Kolla dropped lower-constraints from all the branches.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the openstack-discuss