Maintenance release

<h2 id="example-of-minor-version-numbering">Example of minor version numbering</h2>
<p>The somewhat unusual version number "3.0.5a" was used for a minor release of <a href="/facts/KDE/PCh32IWA">KDE</a> because of a lack of version numbers. Work on KDE 3.1 had already started and, up to that day, the release coordinator used version numbers such as 3.0.5, 3.0.6 internally in the main <a href="/facts/Concurrent_Versions_System/PKnqSra2">CVS</a> repository to mark snapshots of the upcoming 3.1. Then after 3.0.3, a number of important and unexpected bug fixes (starting from 3.0.4) suddenly became necessary, leading to a conflict, because 3.0.5 was at this time already in use. More recent KDE release cycles have tagged pre-release snapshots with large revision numbers, such as 3.1.95, to avoid such conflicts.
</p>
<h2 id="see-also">See also</h2>
<ul><li><a href="/facts/Patch_(computing)/sIHVBPls">Patch (computing)</a></li>
<li><a href="/facts/Software_versioning/EP8VXAUU">Software versioning</a></li>
<li><a href="/facts/Software_release_life_cycle/z4Q4RElA">Software release life cycle</a></li>
<li><a href="/facts/Point_release/xU4YUVUb">Point release</a></li></ul>

<h2 id="references">References</h2>

<ol>
<li id="fn:1"><p>Classen, H. Ward (2005). A practical guide to software licensing for licensees and licensors: analyses and model forms. Chicago, IL: American Bar Association, Section of Business Law. p. 327. ISBN 978-1590315743. <a href="978-1590315743" target="_blank">978-1590315743</a> <a href="#fnref:1" class="footnote-back-ref">↩</a></p></li>
</ol>

Maintenance release open-in-new

Maintenance release