4 ms·

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 so

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.

jjawssd 9y ago
Use namespaces to separate API versions? POST /v4/whatever POST /v3/whatever
- _asummers 9y ago
  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.
  - jjawssd 9y ago
    A better approach would be to alias /v3/user to /v1/user until there is a breaking change needed in the v3 code tier.
    - _asummers 9y ago
      On a rapidly developing API, that would be way too much churn on our front end. For an externally facing API, I completely agree.
dom0 9y ago
Yes, although this applies to all forms of porting changesets or patches between branches or releases.