| Message ID | 20181128145008.6574-1-berrange@redhat.com |
|---|---|
| State | New |
| Headers | show |
| Series | [qemu-web] download: document version numbering scheme | expand |
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
On Wed, Nov 28, 2018 at 6:50 PM Daniel P. Berrangé <berrange@redhat.com> 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> Thanks for the clarification. (It should be displayed under the os menu/carousel on https://www.qemu.org/download/) Reviewed-by: Marc-André Lureau <marcandre.lureau@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: > + </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'); > -- > 2.19.2 >
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: + </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');
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(+)