On 18-09-05 07:04:12, Andreas Jaeger wrote:
> On 2018-09-05 05:20, Matthew Thode wrote:
> > With the move to per-project requirements (aka divergent requirements)
> > we started allowing projects to have differing exclusions and minimums.
> > As long as projects still tested against
On 2018-09-05 05:20, Matthew Thode wrote:
With the move to per-project requirements (aka divergent requirements)
we started allowing projects to have differing exclusions and minimums.
As long as projects still tested against upper-constraints we were good.
Part of the reason why we use
With the move to per-project requirements (aka divergent requirements)
we started allowing projects to have differing exclusions and minimums.
As long as projects still tested against upper-constraints we were good.
Part of the reason why we use upper-constraints is to ensure that
project A and
