Re:The largest Git repo
by seanp2k2 on Wednesday May 24, 2017 @08:13PM
(#14414443)
Cherry picking hotfixes into maint branches is cool until you have stuff like diverging APIs or refactored modules between branches. I don't know of a better solution; it kind of requires understanding in detail what the fix does and how it does it, then knowing if that's directly applicable to every release which needs to be patched.
[ Parent
| on HN ]
Use namespaces to separate API versions?
POST /v4/whatever
POST /v3/whatever
We version each of our individual resources. so a /v1/user might have many /v3/post . Seems to work for us as a smaller engineering team.
A better approach would be to alias /v3/user to /v1/user until there is a breaking change needed in the v3 code tier.
On a rapidly developing API, that would be way too much churn on our front end. For an externally facing API, I completely agree.