Johan Corveleyn wrote on Wed, 22 Apr 2020 13:30 +0200:
> I don't know the exact rules, but does backporting testsuite fixes cause a
> restart of the soak? If we can backport those and include them into the
> final 1.14.0 without restarting the soak, that would be ideal. Otherwise ...
In general, I think test suite infrastructure changes would qualify as
restarting the soak, since they could conceivably break «make check»
for someone out there.
In this instance, however, the purpose of the fixes is to _unbreak_
«make check» for someone in here. It's appealing to say that fixing
a known problem should have priority over the risk of _potentially_
introducing a new problem, but on the other hand, the arguments for not
shortening the soak serve equally well as arguments for not making
exceptions to it.
How about a compromise: keep the test suite changes out of 1.14.0
(unless the soak is restarted), but schedule a 1.14.1 to, say, late
June to release them in?
Received on 2020-04-22 14:02:32 CEST