Fair enough.
On 26/02/2021, 20:45, "Mick Semb Wever" wrote:
Should we wait for e.g. five clean CI runs in a row? Historically flaky
> tests have been a real issue for the project, and CI success probably
> shouldn't be taken instantaneously for releases.
There are tickets fo
Should we wait for e.g. five clean CI runs in a row? Historically flaky
> tests have been a real issue for the project, and CI success probably
> shouldn't be taken instantaneously for releases.
There are tickets for flakey tests that have been pushed to fixVersion
4.0-rc intentionally, making
Should we wait for e.g. five clean CI runs in a row? Historically flaky tests
have been a real issue for the project, and CI success probably shouldn't be
taken instantaneously for releases.
On 26/02/2021, 19:38, "Michael Semb Wever" wrote:
> * We’re within line-of-sight to closing out
> * We’re within line-of-sight to closing out beta scope. Any work people can
> do on remaining blockers will accelerate the project toward RC.
So, last call for last minute concerns, the plan is to cut 4.0-rc1 once
- those beta tickets are resolved,
- the gremlins around v5 native protocol
