Xcode version support #1914
Replies: 2 comments
-
My very simple take is to make minimum supported by the current ruleset whatever the minimum supported Xcode version is. Like you mentioned folks who need older versions could always use the older rules. Might be helpful to describe what would be required maintenance wise from contributors to support older versions in the current rules. If it's much more work I think it makes sense to drop older version |
Beta Was this translation helpful? Give feedback.
-
For official support (with CI test/validations), I would say your suggestion of matching AppStore makes sense. If somebody needs an older version of Xcode, considering this would be the lesser of the cases, I would say is easier if they try to update (easier for you maintainers, and probably beneficial for users in the long term, as support/documentation for older versions will be harder due to almost nobody using such version of Xcode). Of course, if no breaking changes, unofficially rules could keep working with older versions of Xcode. But I would say the burden of officially maintaining those (with tests) is probably not worth it |
Beta Was this translation helpful? Give feedback.
-
Next month Apple won’t allow you to submit to the App Store using anything before Xcode 14.1. We (the rules_apple/rules_swift maintainers) have used this as the highest our minimum Xcode version support could be. But what about the absolute minimum we should support? There are use cases outside of App Store submission, sure, but do you also need the latest rules version in those cases as well?
I’m also personally interested from the point of view of rules_xcodeproj.
So, what is your thoughts on this? Which Xcode version should we minimally support/which methodology should we use to determine it?
Beta Was this translation helpful? Give feedback.
All reactions