Hi Everyone, As part of the 2.5 design, I'm nuking everything non-backwards-compatible from the replication code in the master and fastmail branches. It's all bad and wrong. The replication system WILL be totally backwards compatible with 2.4.
My goal is to use named vendor annotations for any feature not supported by either end, and have the upgrade code read the annotations and apply them, meaning that you can replicate from 2.5 to 2.4, and when you upgrade the replica, it should fix itself. I haven't tested this yet, but I'm pretty sure it will be possible. This breaks FastMail production of course, but I can babysit that one into working state again. This is just fair warning for anyone ELSE who is running unreleased code ;) Bron. -- Bron Gondwana br...@fastmail.fm
