<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0">
  <channel>
    <title>links.lmorchard.com - #versioning</title>
    <link>/tags/versioning/</link>
    <description>Recent bookmarks tagged #versioning</description>
    <lastBuildDate>Mon, 02 Nov 2026 08:24:54 +0000</lastBuildDate>
    <item>
      <title>Semantic Versioning</title>
      <link>http://semver.org</link>
      <description>&#34;I propose a simple set of rules and requirements that dictate how version numbers are assigned and incremented. For this system to work, you first need to declare a public API. This may consist of documentation or be enforced by the code itself. Regardless, it is important that this API be clear and precise. Once you identify your public API, you communicate changes to it with specific increments to your version number. Consider a version format of X.Y.Z (Major.Minor.Patch). Bug fixes not affecting the API increment the patch version, backwards compatible API additions/changes increment the minor version, and backwards incompatible API changes increment the major version.&#34;&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #development #software #versioning&lt;/p&gt;</description>
      <pubDate>Thu, 07 Jan 2010 02:57:51 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:12724</guid>
      <category>development</category>
      <category>software</category>
      <category>versioning</category>
    </item>
    <item>
      <title>Peter Williams - Versioning REST Web Services</title>
      <link>http://barelyenough.org/blog/2008/05/versioning-rest-web-services</link>
      <description>&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #http #rest #versioning #webservices&lt;/p&gt;</description>
      <pubDate>Wed, 15 Oct 2008 19:49:57 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:11542</guid>
      <category>http</category>
      <category>rest</category>
      <category>versioning</category>
      <category>webservices</category>
    </item>
  </channel>
</rss>
