> From a technical perspective, as someone who had previously been merging the MR's from that author, there are also a number of technical reasons we'd slowed down on merging them and started rejecting more of the MR's - most notably it becoming increasingly obvious that the MR's were untested and breaking things. Many of the MR's already have technical objections in them to the changes, and many have no benefit other than refactoring the code to make it easier for future changes he had planned, but now will not contribute to us, so would cause code churn and risk for no remaining reason.