Hi there, Based on my understanding, 4.2.1 is scheduled to come before 4.3.0 release. If this is true, should we add an upgrade path from 4.2.1 to 4.3.0 in Master? This will help us to cherry-pick some commits done in 4.2.1 branch that involves schema changes to master. Any objections on this? If not, what will be the recommended way to cherry-pick those commits to Master? Merging schema change into schema-420to430.sql?
Thanks -min
