The Mapbox GL ecosystem is now wide and deep; breaking changes can have rippling consequences, imposing costs on many downstream components. This is particularly true for changes to the style specification, which by their nature will typically affect gl-js, gl-native core, the native SDKs, Mapbox Studio, Mapbox web services, documentation and customer support, and innumerable utilities, plugins, and applications, both those maintained by Mapbox and those written by customers and open source users.
It therefore seems unlikely that we'll make breaking changes to the style spec in the future, unless they provide a substantial benefit to compensate for these costs. In particular, "cosmetic" breaking changes, such as renaming a style property, are unlikely to meet this bar.
It remains a possibility that at some future date we'll make a coordinated effort to produce a "v9" version of the style specification that aggregates many of these breaking changes in one major release, hoping that by making them simultaneously, we can reduce the overall cost in exchange for their combined benefits. Therefore this "meta issue" collects such issues, previously tracked individually. After being listed here, the individual issues will be closed, in order to keep our issue count more manageable. Feel free to add additional issues to the list.
The Mapbox GL ecosystem is now wide and deep; breaking changes can have rippling consequences, imposing costs on many downstream components. This is particularly true for changes to the style specification, which by their nature will typically affect gl-js, gl-native core, the native SDKs, Mapbox Studio, Mapbox web services, documentation and customer support, and innumerable utilities, plugins, and applications, both those maintained by Mapbox and those written by customers and open source users.
It therefore seems unlikely that we'll make breaking changes to the style spec in the future, unless they provide a substantial benefit to compensate for these costs. In particular, "cosmetic" breaking changes, such as renaming a style property, are unlikely to meet this bar.
It remains a possibility that at some future date we'll make a coordinated effort to produce a "v9" version of the style specification that aggregates many of these breaking changes in one major release, hoping that by making them simultaneously, we can reduce the overall cost in exchange for their combined benefits. Therefore this "meta issue" collects such issues, previously tracked individually. After being listed here, the individual issues will be closed, in order to keep our issue count more manageable. Feel free to add additional issues to the list.