I envisage following a robust testing process outside of the main repo being a bit more difficult with the Leaf because of the quite substantial changes in the can bus framework/messages over the years. A change that works for more recent years but not for prior years is not always easy to spot, also improvements/additions of metrics may only work on a particular year unless another dev with a prior year implements and tests them. Without a group of Leaf devs or testers across the various years that can be called upon to test prior to putting through a PR to main I expect future changes will stay in Leaf devs repos untested for other MYs, as there is no particular reason for others to jump in and test the code to confirm compatibility. PR487 will be a good test case to see if the approach proposed can work in practice.