From: Thomas Huth <thuth@redhat.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>, qemu-devel@nongnu.org
Cc: "Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [qemu-web PATCH] download: document version numbering scheme
Date: Wed, 28 Nov 2018 16:10:00 +0100 [thread overview]
Message-ID: <75c4897e-f24a-e1ef-bece-a6d54541b157@redhat.com> (raw)
In-Reply-To: <20181128145008.6574-1-berrange@redhat.com>
On 2018-11-28 15:50, Daniel P. Berrangé wrote:
> The new version numbering scheme was mentioned in the blog post
> announcing 3.0 previously, but this will fall out of view over
> time. It is thus preferrable to mention this on the download page
> too.
>
> Reported-by: Marc-André Lureau <marcandre.lureau@redhat.com>
> Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
> ---
> download.html | 25 +++++++++++++++++++++++++
> 1 file changed, 25 insertions(+)
>
> diff --git a/download.html b/download.html
> index 5a1e4ea..59db880 100644
> --- a/download.html
> +++ b/download.html
> @@ -39,6 +39,31 @@ permalink: /download/
> {% include_relative _download/source.html %}
> </article>
> </div>
> +
> +<h2>Version numbering</h2>
> +<div>
> + <p>
> + In 2018, for the QEMU 3.0 release, a time based version numbering scheme was
> + adopted:
I'd maybe drop the "2018" here, and use a three digit version number
(since you describe the three digits below) ... maybe rather write it
like this:
Since version 3.0.0, QEMU uses a time based version numbering scheme:
?
> + </p>
> +<ul>
> +<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>
> +</ul>
> + <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');
>
Thomas
next prev parent reply other threads:[~2018-11-28 15:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-28 14:50 [Qemu-devel] [qemu-web PATCH] download: document version numbering scheme Daniel P. Berrangé
2018-11-28 15:10 ` Thomas Huth [this message]
2018-11-28 15:14 ` Marc-André Lureau
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=75c4897e-f24a-e1ef-bece-a6d54541b157@redhat.com \
--to=thuth@redhat.com \
--cc=berrange@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).