Open Stack

On Wed, 6 Jan 2021 at 19:07, Ghanshyam Mann <gmann at ghanshyammann.com> wrote:
>
> Hello Everyone,
>
> You might have seen the discussion around dropping the lower constraints
> testing as it becomes more challenging than the current value of doing it.
>
> Few of the ML thread around this discussion:
>
> - http://lists.openstack.org/pipermail/openstack-discuss/2020-December/019521.html
> - http://lists.openstack.org/pipermail/openstack-discuss/2020-December/019390.html
>
> As Oslo and many other project dropping or already dropped it, we should decide it for all
> other projects also otherwise it can be more changing than it is currently.
>
> We have not defined it in PTI or testing runtime so it is always up to projects if they still
> want to keep it but we should decide a general recommendation here.

I would suggest dropping the lower-constraints job only in projects
where it becomes too difficult to maintain.

I fixed those jobs in Blazar yesterday. It was a bit painful, but in
the process I discovered several requirements were incorrectly
defined, as we were using features not available in the minimum
version required…