search

eskerda / citybikes-api

10 stars 2 forks source link

Branching and tagging for versioning #5

Open eskerda opened 10 years ago

eskerda commented 10 years ago

So far we've got a different branch for v1 (as it goes back to compatibility).

For the next versions of the API v2.x, we should tag each release version, so it's easy to keep supporting them on the server side.

When there's a new version of the API, it should be moved to a branch (where it can be updated for compatibility again).

Master branch should always point to the latest version.

I guess this makes sense?

psyrax commented 10 years ago

Checkout git flow: it might work. https://github.com/nvie/gitflow