[all][tc] Dropping lower-constraints testing from all projects

Ghanshyam Mann gmann at ghanshyammann.com
Tue Jan 19 18:16:14 UTC 2021

 ---- On Tue, 19 Jan 2021 09:32:02 -0600 Jeremy Stanley <fungi at yuggoth.org> wrote ----
 > On 2021-01-19 08:03:25 +0100 (+0100), Thomas Goirand wrote:
 > [...]
 > > Of course, I'm using upper-constraints too, to try to package them
 > > as much as possible, however, the dependencies are expressed
 > > according to lower-constraints.
 > [...]
 > The same lower bounds would also typically be expressed in the
 > requirements.txt file. Presumably you looked there before projects
 > added lower-constraints.txt files? Noting that lower bounds testing
 > isn't feasible and the jobs we were running weren't actually
 > correctly testing minimum versions of everything, these have always
 > been a "best effort" assertion anyway.
 > I gather you run Tempest tests against your OpenStack packages on
 > Debian already, so if a dependency there is too low you'll find out
 > and can let the project maintainers know that their minimum version
 > for that in requirements.txt isn't correct. Hopefully that doesn't
 > come up very often, but for things we can't realistically test,
 > getting notified by downstream distributors and users is the best
 > feedback mechanism we can hope for.

Yeah, in requirments.txt we always have a lower bound of deps and we do not update it or
sync it with u-c. Yes, we will not be testing those as such but as Jeremy mentioned if there
is some wrong lower bound then we can fix it quickly. 

Usually, on every new feature or interface deps, we do bump that lower bound in
requirements.txt. We usually check if anything new we are using that is being
updated in this file or not


 > -- 
 > Jeremy Stanley

More information about the openstack-discuss mailing list