Florent Poinsard

On https://github.com/vitessio/vitess/pull/14935 we have seen that the coverage of `planbuilder` is not being reported. On the base branch it is reported as `0.00%` which leads to Code coverage failure as...

> @GuptaManan100 `vitess/go/history` already has `100%` coverage when I run the tests locally. Can you confirm? @EshaanAgg, @GuptaManan100 is OOO, but I can confirm that it already has `100%` of...

I think it could be relevant to combine certain workflow files into one. However, the matrix needs to be configured in a way that the whole workflow does not fail...

Hello @EshaanAgg, thank you for this issue. I think it is a good idea especially given all the work going on right now to improve code coverage throughout the codebase....

I think this makes a lot of sense, it will ease the job of both the release team and the rest of contributors doing backports. The RC release branch, can...

It would be fine to keep the branch around. We could keep it until it EOLs to avoid having dozen of branches. But as far as I know, people can...

I am removing the `Benchmark me` label to not overload arewefastyet while it catches up with the list of benchmark it needs to re-do

I think it sounds like a reasonable idea, this can help us ensure the automatic golang upgrades are well made too. To avoid having too many workflows we can add...

> This is my first PR to vitessio/vitess so not sure about other procedures such as backports, etc. I would vote for backporting this to previous release branches as people...

Hello @jeefy! I have removed the `m2.xlarge.x86` since we were no longer using it. Regarding the `c3.small.x86` server, it is still used frequently to perform all kind of manual builds...