This is an example of when not to set a limit. There wasn’t a previous commitmen... | Hacker News

Hacker Newsnew | past | comments | ask | show | jobs | submit

		prepend on Nov 29, 2022 \| parent \| context \| favorite \| on: Enabling the Future of GitHub's REST API with API ... This 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 on Nov 29, 2022 [–]

Author 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.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact