On Mon, Aug 15, 2016 at 10:55 PM, Andrew Purtell <andrew.purt...@gmail.com> wrote:
> > Are we extending this to all interfaces? Do we support folks > implementing their own Connection? Admin? > > This will bury us in weeds and bikeshedding. We can make a blanket rule > about source compatibility appropriately scoped to minors and/or patches > without that drama. To wit: > > > So when I read the existing guides, what I see is that we're supposed to > be _source_ compatible on minor and patch releases, but binary compatible > only on patch > > We should take the opportunity to clarify the language of the > compatibility guide. And if the above is the policy then the change to > Table is not allowed. > > so "yes". :) Works for me. Moving from interfaces to abstract classes requires a deprecation cycle, so to transition I think we'd need to introduce a new API. Anyone up for this in 2.0?
