+1 Sounds good, I agree. We should be making the minimal amount of changes
to 1.7. Code changes, even ones that improve performance, introduce more
risk than just simple bug fixes.
I think code changes that improve performance can be made in 1.8,
especially if the plans are to go straight to 1.9
+1 - looking forward to trying these out
On Fri, Feb 2, 2018 at 12:56 PM Keith Turner wrote:
> Recently Mike and I have made some performance improvements. We made
> these to 1.7 and 1.8 branches. I am thinking of reverting these
> changes in the 1.7 branch and keeping them in the 1.8 branch.