Document process for updating Xcode versions
From a discussion with @tmaczukin and @DarrenEastman, we should document how we intend to keep up to date with Xcode versions as they are released. This process should probably include at least the following:
- are Xcode version updates breaking changes? how do we deprecate old OS images if yes?
- do we actually need that many Xcode versions? (context: !47 (comment 468397342))
- when do we upgrade a minor version
- when do we drop support for an old major version
- how do we communicate both of those changes
- do we need to give an advanced warning for minor version upgrades?
Feel free to add more to the list @tmaczukin @DarrenEastman
I think we need better information from potential customers, what do they actually need in terms of Xcode support, and how they expect it to evolve as new Xcode releases appear. I don’t think we have the internal knowledge about macOS development to provide useful info on this.
We currently have one customer giving feedback (#1, #2) about MacOS, and it would be interesting to get feedback from folks working on iOS as well.
Edited by Adrien Kohlbecker