@@ -17,6 +17,7 @@
<li><a href="https://qemu.weilnetz.de/qemu-doc.html">Manual</a></li>
<li><a href="https://wiki.qemu.org/Category:Developer_documentation">Developer docs</a></li>
<li><a href="https://wiki.qemu.org/">Wiki</a></li>
+ <li><a href="/version-numbering">Version numbering</a></li>
</ul>
<ul class="style">
<li><a href="https://planet.virt-tools.org/">virt tools planet</a></li>
@@ -40,29 +40,6 @@ permalink: /download/
</article>
</div>
-<h2>Version numbering</h2>
-<div>
- <p>
- Since version 3.0.0, QEMU uses a time based version numbering scheme:
- </p>
-<dl>
-<dt>major</dt>
-<dd>incremented by 1 for the first release of the year</dd>
-<dt>minor</dt>
-<dd>reset to 0 with every major increment, otherwise incremented by 1 for each release from git master</dd>
-<dt>micro</dt>
-<dd>always 0 for releases from git master, incremented by 1 for each stable branch release</dd>
-</dl>
- <p>
- The implication of this is that changes in major version number
- <strong>do not</strong> have any bearing on the scope of changes
- included in the release. Non-backward compatible changes may be made
- in any master branch release, provided they have followed the
- <a href="https://qemu.weilnetz.de/doc/qemu-doc.html#Deprecated-features">deprecation policy</a>
- which calls for warnings to be emitted for a minimum of two releases
- prior to the change.
- </p>
-</div>
<script>
function animateOnClick(jqThis, slide) {
$('.horiz-menu li').removeClass('active');
new file mode 100644
@@ -0,0 +1,26 @@
+---
+title: QEMU version numbering
+permalink: /version-numbering/
+---
+
+Since version 3.0.0, QEMU uses a time based version numbering scheme:
+
+ - major: incremented by 1 for the first release of the year
+
+ - minor: reset to 0 with every major increment, otherwise
+ incremented by 1 for each release from git master
+
+ - micro: always 0 for releases from git master, incremented by 1 for
+ each stable branch release
+
+The implication of this is that changes in major version number *do not*
+have any bearing on the scope of changes included in the release.
+Non-backward compatible changes may be made in any master branch
+release, provided they have followed the [deprecation
+policy](https://qemu.weilnetz.de/doc/qemu-doc.html#Deprecated-features)
+which calls for warnings to be emitted for a minimum of two releases
+prior to the change.
+
+Example number scheme: in the year 2019, there will be 4.0.0, 4.1.0 and
+4.2.0 releases; following that, 5.0.0, 5.1.0, 5.2.0 releases in 2020,
+and so on.
Instead of burying the version numbering details under "Download QEMU" page, place it in its own document. And highlight its presence in the website footer. While at it, add a concrete example of the version numbering scheme. Signed-off-by: Kashyap Chamarthy <kchamart@redhat.com> --- _includes/footer.html | 1 + download.html | 23 ----------------------- version-numbering.md | 26 ++++++++++++++++++++++++++ 3 files changed, 27 insertions(+), 23 deletions(-) create mode 100644 version-numbering.md