Software & Systems Engineering·Designing an API·CoreWhen a new version is warrantedA team versions their API and releases v2 whenever they add a field.What is wrong with that practice?AVersion numbers should only ever increase on a fixed scheduleBTwo versions cannot be supported at the same time in most frameworks anywayCCallers would need to update their code to receive the new fieldDAdding a field is compatible, so the version costs maintenance and buys nothingCheck answer