News for hackers. Stuff that matters.
Re:How to Version an API by edoceo on Thursday June 08, 2017 @03:12PM (#14516386)
I'm similar but just prefix like

    /v2014
I assume I won't make multiple versions in a year. I have a current system with /v2014, /v2016 and /v2017

I like to smash dates into all my version strings

Re:How to Version an API by cyann on Thursday June 08, 2017 @03:31PM (#14516531)
Yes, human readable dates are very good at conveying a sense of obsolescence.

Mine are a bit more granular: /vyymm, e.g. /v1503, /v1610, /v1706. This should work well for this century ;-)