> If we make this conditional on the merge of the MC branch, then an important question is if we have an outlook as to the solution of the required data migration from non-MC to MC. As long as we don't have a good solution there, I'm thinking we shouldn't hold back changes conditionally.
>
> I'd like to put it differently: if we postpone this until after 1.5 then is there a good reason why we would *not* want to have this in 1.5 whereas that reason doesn't apply to 1.6?I am worried about tests and tooling.
> If this really is about merging pain, then I'm thinking we should create a copy-repo, create the move on master and then try to merge that to MC and see if it works or completely falls down. Does that work for you?
Yes that is fine. Might also be worth playing with in a branch for discussion and review purposes
------------------------------------------------------------------------------ Site24x7 APM Insight: Get Deep Visibility into Application Performance APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month Monitor end-to-end web transactions and take corrective actions now Troubleshoot faster and improve end-user experience. Signup Now! http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
_______________________________________________ Ledger-smb-devel mailing list ..hidden.. https://lists.sourceforge.net/lists/listinfo/ledger-smb-devel