[privong]

Often that is acceptable advice, but in this case, their issue that:

> - Doesn't break in the next release.

is something that can't be worked around simply by creating your own theme. That seems to be caused by poor compatibility checking (or reckless disregard, as others are claiming), which could bite you even if you create your own theme.

Obviously, you could extend your suggestion to "fork gtk3", but that's likely a significant undertaking and not reasonable for everyone. I think it is reasonable to expect developers to maintain compatibility between minor version releases, assuming they're using semantic versioning, otherwise it's poor communication on the part of the developers.

[adrianlmm]

That's an old myth, the theme engine is now stable and even if it breaks it is only a matter of minutes to fix it.

[weland]

Do a google search for GTK 3.16 theme bug. You'll find a bunch of people for whom it didn't take minutes.

[adrianlmm]

Then submits bugs and contribute to fix those bugs, it is the way open source works, if you don't like it, go use something else, nobody is forcing you to use it.

[weland]

What does being open source have to do with having crap policies?

There are plenty of open source projects that don't have those problems, and it's not like the core team is interested in making theming anything else but a clunky hack so that everyone uses Adwaita...