From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Thomas Huth <thuth@redhat.com>
Cc: qemu-devel@nongnu.org, "Paolo Bonzini" <pbonzini@redhat.com>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>
Subject: Re: [Qemu-devel] [qemu-web PATCH v2] download: document version numbering scheme
Date: Thu, 29 Nov 2018 11:04:07 +0000 [thread overview]
Message-ID: <20181129110407.GC25007@redhat.com> (raw)
In-Reply-To: <f73a6661-83a1-73fa-d087-a8d9c9aaaff5@redhat.com>
On Thu, Nov 29, 2018 at 11:58:22AM +0100, Thomas Huth wrote:
> On 2018-11-28 16:38, 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 | 24 ++++++++++++++++++++++++
> > 1 file changed, 24 insertions(+)
> >
> > diff --git a/download.html b/download.html
> > index 5a1e4ea..bbdc00c 100644
> > --- a/download.html
> > +++ b/download.html
> > @@ -39,6 +39,30 @@ permalink: /download/
> > {% include_relative _download/source.html %}
> > </article>
> > </div>
> > +
> > +<h2>Version numbering</h2>
> > +<div>
> > + <p>
> > + 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>
>
> HTML validator (https://validator.w3.org) complains here:
>
> * Element dt not allowed as child of element ul in this context.
>
> * Element dt not allowed as child of element ul in this context.
Oh fun, browsers still rendered it correctly despite being wrong :-)
>
> Since I don't want to mess up your intended formatting, could you please
> fix it on your own and send a v3?
I've sent a v3 with s/ul/dl/
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
prev parent reply other threads:[~2018-11-29 11:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-28 15:38 [Qemu-devel] [qemu-web PATCH v2] download: document version numbering scheme Daniel P. Berrangé
2018-11-29 10:58 ` Thomas Huth
2018-11-29 11:04 ` Daniel P. Berrangé [this message]
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=20181129110407.GC25007@redhat.com \
--to=berrange@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
/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).