On 13 November 2017 at 10:03, Cédric Le Goater <c...@kaod.org> wrote: > One of the sweeping change for 3.0 could be to stop to maintaining > migration compatibility with older versions (2.x). Even if the > feature is really a must have in some cluster environment, the > code (and the developer) is starting to suffer from it.
We certainly can't just drop all migration-compat. The closest we might come would be to say we dropped migration-compat from versions older than $X for some value of X. But this kind of discussion is what I mean -- various people have different ideas about what we might or might not drop, but we need to come to a consensus about what we can actually do first. thanks -- PMM
