We're working on a small support release for https://github.com/mapbox/mapbox-gl-native-ios for iOS 15 and Xcode 13. As part of this release, we want to adopt to the 1.x series of Mobile Events. However, we do not plan to update mapbox-gl-native-ios to support development on Apple Silicon, and its current Carthage-based development environment fails with Mobile Events 1.0.2 due to the changes in 4ff47377561eeb7a3502f1ca1a02dcafc442c980. While these changes were and continue to be essential for Maps SDK v10, we need a variant of this SDK that brings back the EXCLUDED_ARCHS changes so that we can maintain our current level of support for Carthage in our upcoming release.
The challenge will be how to release this. Since Carthage works off of semver-style git tags and we do want the ability to automatically adopt subsequent minor and patch releases of MME, we can't simply make up an alternative tagging scheme within the 1.x release line.
I propose that we initiate a new line of releases that mirror the 1.x line but with the change I prototyped above. We can name this release line the 1001.x line, and as long as folks aren't using the > operator in their dependency manager, v10 consumers will continue to get 1.x and v6 consumers will get 1001.x.
This gives us more than enough room to introduce additional breaking changes to the API if needed and the pattern will continue to work (e.g. if there's a MME 2.x, we'd also release a MME 1002.x).
We're working on a small support release for https://github.com/mapbox/mapbox-gl-native-ios for iOS 15 and Xcode 13. As part of this release, we want to adopt to the 1.x series of Mobile Events. However, we do not plan to update mapbox-gl-native-ios to support development on Apple Silicon, and its current Carthage-based development environment fails with Mobile Events 1.0.2 due to the changes in 4ff47377561eeb7a3502f1ca1a02dcafc442c980. While these changes were and continue to be essential for Maps SDK v10, we need a variant of this SDK that brings back the EXCLUDED_ARCHS changes so that we can maintain our current level of support for Carthage in our upcoming release.
I've prototyped a minimal change that should address this issue: https://github.com/mapbox/mapbox-events-ios/commit/6df49a3a2619af713ba64686cf96c8c23850a336
The challenge will be how to release this. Since Carthage works off of semver-style git tags and we do want the ability to automatically adopt subsequent minor and patch releases of MME, we can't simply make up an alternative tagging scheme within the 1.x release line.
I propose that we initiate a new line of releases that mirror the 1.x line but with the change I prototyped above. We can name this release line the 1001.x line, and as long as folks aren't using the
>operator in their dependency manager, v10 consumers will continue to get 1.x and v6 consumers will get 1001.x.This gives us more than enough room to introduce additional breaking changes to the API if needed and the pattern will continue to work (e.g. if there's a MME 2.x, we'd also release a MME 1002.x).