On Mon, 2016-06-13 at 18:34 +0100, Daniel P. Berrange wrote: > This bumps the release number of 2.0.0, to reflect the switch to > a new time based release versioning scheme. The downloads page > is updated to describe our policies for release schedules and > release version numbering > > The stable release docs are changed to reflect the fact that > the stable version numbers are now just 3 digits long instead > of 4. > > Signed-off-by: Daniel P. Berrange <berrange@xxxxxxxxxx> > --- > configure.ac | 2 +- > docs/downloads.html.in | 59 ++++++++++++++++++++++++++++++++++++++++++++++---- > src/libvirt_lxc.syms | 2 +- > 3 files changed, 57 insertions(+), 6 deletions(-) > > diff --git a/configure.ac b/configure.ac > index 827d9db..0114149 100644 > --- a/configure.ac > +++ b/configure.ac > @@ -16,7 +16,7 @@ dnl You should have received a copy of the GNU Lesser General Public > dnl License along with this library. If not, see > dnl <http://www.gnu.org/licenses/>. > > -AC_INIT(, [1.3.6], [libvir-list@xxxxxxxxxx], [], [http://libvirt.org]) > +AC_INIT(, [2.0.0], [libvir-list@xxxxxxxxxx], [], [http://libvirt.org]) > AC_CONFIG_SRCDIR([src/libvirt.c]) > AC_CONFIG_AUX_DIR([build-aux]) > AC_CONFIG_HEADERS([config.h]) > diff --git a/docs/downloads.html.in b/docs/downloads.html.in > index 13a6db1..32cc2ec 100644 > --- a/docs/downloads.html.in > +++ b/docs/downloads.html.in > @@ -32,20 +32,71 @@ > <li><a href="http://libvirt.org/sources/libvirt-git-snapshot.tar.gz";>libvirt.org HTTP server</a></li> > </ul> > > + <h2><a name="schedule">Primary release schedule</a></h2> > + > + <p> > + Libvirt follows a time based plan, with releases made once a month > + on the 1st of each month give or take a few days. The only exception > + is at the start of the year where there are two 6 weeks gaps, giving > + a total of 11 releases a year. Expect to see releases on approx: ~~~~~~ Either use "approx." or, better yet, "approximately". > + </p> > + > + <ul> > + <li>Jan 15th</li> > + <li>Mar 1st</li> > + <li>Apr 1st</li> > + <li>May 1st</li> > + <li>Jun 1st</li> > + <li>Jul 1st</li> > + <li>Aug 1st</li> > + <li>Sep 1st</li> > + <li>Oct 1st</li> > + <li>Nov 1st</li> > + <li>Dec 1st</li> > + </ul> On the other hand, do we really need to be so specific, and even list specific dates? I'd go with something a bit more generic, along the lines of "we're going to do a release at the beginning of each month, but releases might slip a few days due to holidays and such". > + <h2><a name="numbering">Release numbering</a></h2> > + > + <p> > + Since libvirt 2.0.0, a time based version numbering rule > + is applied. As such, the changes in version number have > + do not have any implications wrt the scope of features ~~~ Please use the extended form. > + or bugfixes included, the stability of the code, or the > + API / ABI compatibility (libvirt API / ABI is guaranteed > + stable forever). The rules applied for changing the libvirt > + version number are: > + </p> > + > + <ul> > + <li><code>major</code> - incremented by 1 for the first release of the year (the Jan 15th release)</li> > + <li><code>minor</code> - incremented by 1 for each monthly release from git master</li> > + <li><code>micro</code> - always 0 for releases from git master, incremented by 1 for each stable maintenance > release</li> > + </ul> These could be wrapped at ~80 columns. -- Andrea Bolognani Software Engineer - Virtualization Team -- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list