Thanks Marc! I owe you guys a beer next week :).
Doug.
Ok, we'll keep the compatibility changes out of master since that is the preference.
Marc
+1.
"until we use something meaningful from 4.5” is in the eye of the beholder. Who’s going to make that decision? How much time are we going to waste trying to decide?
"in case it helps others”. Would you think differently if it actually doesn’t help others? It’s a great thought, but I’m not sure there are others. Happy to be proven otherwise.
My recommendation is that you create a branch and keep your compatibility code isolated there. You can then do regular merges from master to your branch. That'll let us who don’t need to be burdened with that carry on and use all the great things the platform
is giving us in Mars and beyond, including goodies like this:
https://dev.eclipse.org/mhonarc/lists/eclipse-dev/msg09944.html, and keep the code clean.
Doug.
https://git.eclipse.org/r/#/c/43178/ shows how easy it is to make mistakes when judging issues of backward compatibility. I personally don't want to be bothered by those issues.
-sergey