3 ms·
> After two years, we reserve the right to retire a version, but in practice, we expect to support historic versions for significantly longer than this. Consid
by abraham 4y ago
> After two years, we reserve the right to retire a version, but in practice, we expect to support historic versions for significantly longer than this.
Consider v3 has been around for a decade, they seems likely to last longer than 2 years.
- prepend 4y agoThis is an example of when not to set a limit. There wasn’t a previous commitment to maintain v3, so why add one now? And why only 2? If they intend to maintain them for 10 years then don’t set a specific timeframe and just stick to whatever their current nebulous language is.
- timrogers 4y agoAuthor here. We just wanted to provide a guarantee to reassure users that the introduction of API versioning wasn't going to mean rapid deprecations of versions. We thought that giving a guaranteed minimum lifetime was a reasonable way to do that.