From patchwork Mon Feb 11 16:20:52 2019 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Kashyap Chamarthy X-Patchwork-Id: 1039948 Return-Path: X-Original-To: incoming@patchwork.ozlabs.org Delivered-To: patchwork-incoming@bilbo.ozlabs.org Authentication-Results: ozlabs.org; spf=pass (mailfrom) smtp.mailfrom=nongnu.org (client-ip=209.51.188.17; helo=lists.gnu.org; envelope-from=qemu-devel-bounces+incoming=patchwork.ozlabs.org@nongnu.org; receiver=) Authentication-Results: ozlabs.org; dmarc=fail (p=none dis=none) header.from=redhat.com Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ozlabs.org (Postfix) with ESMTPS id 43ys4875JSz9sMp for ; Tue, 12 Feb 2019 03:41:12 +1100 (AEDT) Received: from localhost ([127.0.0.1]:52569 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gtEdq-0008TQ-Ud for incoming@patchwork.ozlabs.org; Mon, 11 Feb 2019 11:41:10 -0500 Received: from eggs.gnu.org ([209.51.188.92]:47494) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gtEaq-0006Yc-Sz for qemu-devel@nongnu.org; Mon, 11 Feb 2019 11:38:06 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gtEao-0006FY-UF for qemu-devel@nongnu.org; Mon, 11 Feb 2019 11:38:04 -0500 Received: from mx1.redhat.com ([209.132.183.28]:49296) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1gtEam-0006Cz-SX for qemu-devel@nongnu.org; Mon, 11 Feb 2019 11:38:02 -0500 Received: from smtp.corp.redhat.com (int-mx07.intmail.prod.int.phx2.redhat.com [10.5.11.22]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 2CCEDAB997 for ; Mon, 11 Feb 2019 16:21:00 +0000 (UTC) Received: from paraplu.localdomain (ovpn-117-164.ams2.redhat.com [10.36.117.164]) by smtp.corp.redhat.com (Postfix) with ESMTP id 41EAC10E81C0; Mon, 11 Feb 2019 16:20:59 +0000 (UTC) From: Kashyap Chamarthy To: qemu-devel@nongnu.org Date: Mon, 11 Feb 2019 17:20:52 +0100 Message-Id: <20190211162052.13584-1-kchamart@redhat.com> X-Scanned-By: MIMEDefang 2.84 on 10.5.11.22 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.26]); Mon, 11 Feb 2019 16:21:00 +0000 (UTC) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 209.132.183.28 Subject: [Qemu-devel] [PATCH] [qemu-web] Put version numbering details in its own doc X-BeenThere: qemu-devel@nongnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Kashyap Chamarthy Errors-To: qemu-devel-bounces+incoming=patchwork.ozlabs.org@nongnu.org Sender: "Qemu-devel" 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 --- _includes/footer.html | 1 + download.html | 23 ----------------------- version-numbering.md | 26 ++++++++++++++++++++++++++ 3 files changed, 27 insertions(+), 23 deletions(-) create mode 100644 version-numbering.md diff --git a/_includes/footer.html b/_includes/footer.html index 1669ef766cc18b0df3e27418038f9bf851b74c8a..0fb85feb564e3b23bc4ab78eb05359264d13bfa5 100644 --- a/_includes/footer.html +++ b/_includes/footer.html @@ -17,6 +17,7 @@
  • Manual
  • Developer docs
  • Wiki
    • +
  • Version numbering
    • virt tools planet
      • diff --git a/download.html b/download.html index 3c2df66ff6757bba1246b5f0873b287fca600f11..e4c8bb5792aa6e6f7038a9fd2bdab3c432daa6ab 100644 --- a/download.html +++ b/download.html @@ -40,29 +40,6 @@ permalink: /download/ -

      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 - which calls for warnings to be emitted for a minimum of two releases - prior to the change. -

      -