Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

4
  • So if my website is just coded for me I don't need semantic versionning if I understand Commented May 14, 2014 at 19:58
  • That is completely possible. Commented May 14, 2014 at 19:59
  • I apologize for being stupid, but their is no I interest in using semantic versionning for me? Also, where should I put the versionning if there is a public api as described ? For the whole website or just for the part? Commented May 14, 2014 at 20:04
  • 2
    These are all "it depends" type questions. We don't know enough about your use case to say "this doesn't make sense for you". All we can say is "this may not make sense". When versioning a web-service, it is common to use path parameters as ''/api/v2/people/42''. If you're talking about language specific APIs / libraries, the versioning really depends on the framework and implementation (Java, PHP, C#). Commented May 14, 2014 at 20:07