[webkit-gtk] Breaking the API/ABI for 2.6

[Martin Robinson]

On Tue, Jun 3, 2014 at 6:18 AM, Carlos Garcia Campos <cgarcia at igalia.com> wrote:
>   - Limit the amount of API we expose to the GObject DOM bindings API.
> We currently expose every single idl file that is added to the
> repository, no matter of the API is just a w3c draft, or if it's
> prefixed, etc. This is giving us a lot of work everytime any idl API
> changes, and we end up with special cases to deprecate the old API and
> add new one, for things that have never been used by anybody. So, I
> propose to only expose "stable" APIs that are unlikely to change. I'm
> not sure how to define that, though, maybe when the w3c spec is final or
> whatever. I should also probably not expose anything depending on a
> feature protected by conditional compilation and not enabled by default
> in GTK+. I'm open to any proposal in this regard. Of course we would
> remove all the deprecated API in the DOM bindings for 2.6.

We should really think hard about what API to expose and ensure that
it doesn't change based on build options. I also recommend that we
take a close look at the API to fix any other long-standing issues.

Generally, this all sounds good to me, though it's a pity that we have
to do an ABI/API break.