External/libvirt
1
0
Fork 0
mirror of https://gitlab.com/libvirt/libvirt.git synced 2024-11-09 06:50:22 +00:00
Code Issues Packages Projects Releases Wiki Activity
013df874db
libvirt/docs/downloads.html.in

458 lines
17 KiB
HTML
Raw Normal View History

Fix multiple formatting problems in HTML docs The rule generating the HTML docs passing the --html flag to xsltproc. This makes it use the legacy HTML parser, which either ignores or tries to fix all sorts of broken XML tags. There's no reason why we should be writing broken XML in the first place, so removing --html and adding the XHTML doctype to all files forces us to create good XML. This adds the XHTML doc type and fixes many, many XML tag problems it exposes. Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
2013-05-03 14:25:37 +00:00
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
Split website out into one file per page. APply new layout and styling
2008-04-23 17:08:31 +00:00
<body>
docs: add the app dev guide Added a workable initial page for the libvirt Application Development Guide, giving the online viewable options + the available download ones (pdf, epub, srpm). Added a link to the PDF to the main Downloads page, plus neatened the html tags throughout the page as they were a bit of a mess. Added --enable-compile-warnings=error to the autogen line, as suggested by Eric Blake.
2010-09-10 09:26:05 +00:00
<h1>Downloads</h1>
Split website out into one file per page. APply new layout and styling
2008-04-23 17:08:31 +00:00
docs: added a table of contents to the first 11 docs files There are a 58 docs files, so adding an autogenerated Table Of Contents to them all will take some time. This is the first piece of the work done.
2010-10-23 21:46:32 +00:00
<ul id="toc"></ul>
docs: expand downloads page to cover all modules Previously the download page only covered the main libvirt module and the app dev guide. Expand it to provide direct links to all artifacts published by the project, whether the main library, language bindings, docs, or testing. Tweak the top table styling to better fit in with new branding. Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
2016-10-31 11:27:27 +00:00
<h2><a name="releases">Project modules</a></h2>
Split website out into one file per page. APply new layout and styling
2008-04-23 17:08:31 +00:00
<p>
docs: expand downloads page to cover all modules Previously the download page only covered the main libvirt module and the app dev guide. Expand it to provide direct links to all artifacts published by the project, whether the main library, language bindings, docs, or testing. Tweak the top table styling to better fit in with new branding. Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
2016-10-31 11:27:27 +00:00
The libvirt project maintains a number of inter-related modules beyond
the core C library/daemon.
</p>
<table class="top_table downloads">
<thead>
<tr>
<th>Module</th>
<th>Releases</th>
<th>GIT Repo</th>
<th>GIT Mirrors</th>
</tr>
</thead>
<tbody>
<tr>
<td>libvirt</td>
<td>
<a href="ftp://libvirt.org/libvirt/">ftp</a>
<a href="http://libvirt.org/sources/">http</a>
<a href="https://libvirt.org/sources/">https</a>
</td>
<td>
<a href="http://libvirt.org/git/?p=libvirt.git;a=summary">libvirt</a>
</td>
<td>
<a href="https://gitlab.com/libvirt/libvirt">gitlab</a>
<a href="https://github.com/libvirt/libvirt">github</a>
</td>
</tr>
<tr>
<th colspan="7">Language bindings</th>
</tr>
<tr>
<td>C#</td>
<td>
<a href="ftp://libvirt.org/libvirt/csharp/">ftp</a>
<a href="http://libvirt.org/sources/csharp/">http</a>
<a href="https://libvirt.org/sources/csharp/">https</a>
</td>
<td>
<a href="http://libvirt.org/git/?p=libvirt-csharp.git;a=summary">libvirt</a>
</td>
<td>
<a href="https://gitlab.com/libvirt/libvirt-csharp">gitlab</a>
<a href="https://github.com/libvirt/libvirt-csharp">github</a>
</td>
</tr>
<tr>
<td>Java</td>
<td>
<a href="ftp://libvirt.org/libvirt/java/">ftp</a>
<a href="http://libvirt.org/sources/java/">http</a>
<a href="https://libvirt.org/sources/java/">https</a>
</td>
<td>
<a href="http://libvirt.org/git/?p=libvirt-java.git;a=summary">libvirt</a>
</td>
<td>
<a href="https://gitlab.com/libvirt/libvirt-java">gitlab</a>
<a href="https://github.com/libvirt/libvirt-java">github</a>
</td>
</tr>
<tr>
<td>OCaml</td>
<td>
<a href="ftp://libvirt.org/libvirt/ocaml/">ftp</a>
<a href="http://libvirt.org/sources/ocaml/">http</a>
<a href="https://libvirt.org/sources/ocaml/">https</a>
</td>
<td>
<a href="http://libvirt.org/git/?p=libvirt-ocaml.git;a=summary">libvirt</a>
</td>
<td>
<a href="https://gitlab.com/libvirt/libvirt-ocaml">gitlab</a>
<a href="https://github.com/libvirt/libvirt-ocaml">github</a>
</td>
</tr>
<tr>
<td>Perl (Sys::Virt)</td>
<td>
<a href="http://search.cpan.org/dist/Sys-Virt/">cpan</a>
</td>
<td>
<a href="http://libvirt.org/git/?p=libvirt-perl.git;a=summary">libvirt</a>
</td>
<td>
<a href="https://gitlab.com/libvirt/libvirt-perl">gitlab</a>
<a href="https://github.com/libvirt/libvirt-perl">github</a>
</td>
</tr>
<tr>
<td>PHP</td>
<td>
<a href="ftp://libvirt.org/libvirt/php/">ftp</a>
<a href="http://libvirt.org/sources/php/">http</a>
<a href="https://libvirt.org/sources/php/">https</a>
</td>
<td>
<a href="http://libvirt.org/git/?p=libvirt-php.git;a=summary">libvirt</a>
</td>
<td>
<a href="https://gitlab.com/libvirt/libvirt-php">gitlab</a>
<a href="https://github.com/libvirt/libvirt-php">github</a>
</td>
</tr>
<tr>
<td>Python</td>
<td>
<a href="ftp://libvirt.org/libvirt/python/">ftp</a>
<a href="http://libvirt.org/sources/python/">http</a>
<a href="https://libvirt.org/sources/python/">https</a>
<a href="https://pypi.python.org/pypi/libvirt-python">pypi</a>
</td>
<td>
<a href="http://libvirt.org/git/?p=libvirt-python.git;a=summary">libvirt</a>
</td>
<td>
<a href="https://gitlab.com/libvirt/libvirt-python">gitlab</a>
<a href="https://github.com/libvirt/libvirt-python">github</a>
</td>
</tr>
<tr>
<td>Ruby</td>
<td>
<a href="ftp://libvirt.org/libvirt/ruby/">ftp</a>
<a href="http://libvirt.org/sources/ruby/">http</a>
<a href="https://libvirt.org/sources/ruby/">https</a>
</td>
<td>
<a href="http://libvirt.org/git/?p=ruby-libvirt.git;a=summary">libvirt</a>
</td>
<td>
<a href="https://gitlab.com/libvirt/ruby-libvirt">gitlab</a>
<a href="https://github.com/libvirt/ruby-libvirt">github</a>
</td>
</tr>
<tr>
<th colspan="7">Integration modules</th>
</tr>
<tr>
<td>GLib / GConfig / GObject</td>
<td>
<a href="ftp://libvirt.org/libvirt/glib/">ftp</a>
<a href="http://libvirt.org/sources/glib/">http</a>
<a href="https://libvirt.org/sources/glib/">https</a>
</td>
<td>
<a href="http://libvirt.org/git/?p=libvirt-glib.git;a=summary">libvirt</a>
</td>
<td>
<a href="https://gitlab.com/libvirt/libvirt-glib">gitlab</a>
<a href="https://github.com/libvirt/libvirt-glib">github</a>
</td>
</tr>
<tr>
<td>CIM provider</td>
<td>
<a href="ftp://libvirt.org/libvirt/CIM/">ftp</a>
<a href="http://libvirt.org/sources/CIM/">http</a>
<a href="https://libvirt.org/sources/CIM/">https</a>
</td>
<td>
<a href="http://libvirt.org/git/?p=libvirt-cim.git;a=summary">libvirt</a>
</td>
<td>
<a href="https://gitlab.com/libvirt/libvirt-cim">gitlab</a>
<a href="https://github.com/libvirt/libvirt-cim">github</a>
</td>
</tr>
<tr>
<td>CIM utils</td>
<td>
<a href="ftp://libvirt.org/libvirt/CIM/">ftp</a>
<a href="http://libvirt.org/sources/CIM/">http</a>
<a href="https://libvirt.org/sources/CIM/">https</a>
</td>
<td>
<a href="http://libvirt.org/git/?p=libcmpiutil.git;a=summary">libvirt</a>
</td>
<td>
<a href="https://gitlab.com/libvirt/libcmpiutil">gitlab</a>
<a href="https://github.com/libvirt/libcmpiutil">github</a>
</td>
</tr>
<tr>
<td>SNMP</td>
<td>
<a href="ftp://libvirt.org/libvirt/snmp/">ftp</a>
<a href="http://libvirt.org/sources/snmp/">http</a>
<a href="https://libvirt.org/sources/snmp/">https</a>
</td>
<td>
<a href="http://libvirt.org/git/?p=libvirt-snmp.git;a=summary">libvirt</a>
</td>
<td>
<a href="https://gitlab.com/libvirt/libvirt-snmp">gitlab</a>
<a href="https://github.com/libvirt/libvirt-snmp">github</a>
</td>
</tr>
<tr>
<td>Application Sandbox</td>
<td>
<a href="ftp://libvirt.org/libvirt/sandbox/">ftp</a>
<a href="http://libvirt.org/sources/sandbox/">http</a>
<a href="https://libvirt.org/sources/sandbox/">https</a>
</td>
<td>
<a href="http://libvirt.org/git/?p=libvirt-sandbox.git;a=summary">libvirt</a>
</td>
<td>
<a href="https://gitlab.com/libvirt/libvirt-sandbox">gitlab</a>
<a href="https://github.com/libvirt/libvirt-sandbox">github</a>
</td>
</tr>
<tr>
<th colspan="7">Testing</th>
</tr>
<tr>
<td>TCK</td>
<td>
<a href="ftp://libvirt.org/libvirt/tck/">ftp</a>
<a href="http://libvirt.org/sources/tck/">http</a>
<a href="https://libvirt.org/sources/tck/">https</a>
</td>
<td>
<a href="http://libvirt.org/git/?p=libvirt-tck.git;a=summary">libvirt</a>
</td>
<td>
<a href="https://gitlab.com/libvirt/libvirt-tck">gitlab</a>
<a href="https://github.com/libvirt/libvirt-tck">github</a>
</td>
</tr>
<tr>
<td>Test API</td>
<td></td>
<td>
<a href="http://libvirt.org/git/?p=libvirt-test-API.git;a=summary">libvirt</a>
</td>
<td>
<a href="https://gitlab.com/libvirt/libvirt-test-API">gitlab</a>
<a href="https://github.com/libvirt/libvirt-test-API">github</a>
</td>
</tr>
<tr>
<td>Jenkins Config</td>
<td></td>
<td>
<a href="http://libvirt.org/git/?p=libvirt-jenkins-ci.git;a=summary">libvirt</a>
</td>
<td>
<a href="https://gitlab.com/libvirt/libvirt-jenkins-ci">gitlab</a>
<a href="https://github.com/libvirt/libvirt-jenkins-ci">github</a>
</td>
</tr>
<tr>
<td>CIM Test</td>
<td></td>
<td>
<a href="http://libvirt.org/git/?p=cimtest.git;a=summary">libvirt</a>
</td>
<td>
<a href="https://gitlab.com/libvirt/cimtest">gitlab</a>
<a href="https://github.com/libvirt/cimtest">github</a>
</td>
</tr>
<tr>
<th colspan="7">Documentation</th>
</tr>
<tr>
<td>Publican Brand</td>
<td></td>
<td>
<a href="http://libvirt.org/git/?p=libvirt-publican.git;a=summary">libvirt</a>
</td>
<td>
<a href="https://gitlab.com/libvirt/libvirt-publican">gitlab</a>
<a href="https://github.com/libvirt/libvirt-publican">github</a>
</td>
</tr>
<tr>
<td>App Development Guide</td>
<td></td>
<td>
<a href="http://libvirt.org/git/?p=libvirt-appdev-guide.git;a=summary">libvirt</a>
</td>
<td>
<a href="https://gitlab.com/libvirt/libvirt-appdev-guide">gitlab</a>
<a href="https://github.com/libvirt/libvirt-appdev-guide">github</a>
</td>
</tr>
<tr>
<td>App Development Guide Python</td>
<td></td>
<td>
<a href="http://libvirt.org/git/?p=libvirt-appdev-guide-python.git;a=summary">libvirt</a>
</td>
<td>
<a href="https://gitlab.com/libvirt/libvirt-appdev-guide-python">gitlab</a>
<a href="https://github.com/libvirt/libvirt-appdev-guide-python">github</a>
</td>
</tr>
<tr>
<td>virsh Command Reference</td>
<td></td>
<td>
<a href="http://libvirt.org/git/?p=libvirt-virshcmdref.git;a=summary">libvirt</a>
</td>
<td>
<a href="https://gitlab.com/libvirt/libvirt-virshcmdref">gitlab</a>
<a href="https://github.com/libvirt/libvirt-virshcmdref">github</a>
</td>
</tr>
</tbody>
</table>
<h2>Primary download site</h2>
<p>
Most modules have releases made available for download on the project
site, via FTP, HTTP or HTTPS. Some modules are instead made available
at alternative locations, for example, the Perl binding is made
available only on CPAN.
Split website out into one file per page. APply new layout and styling
2008-04-23 17:08:31 +00:00
</p>
<ul>
<li><a href="ftp://libvirt.org/libvirt/">libvirt.org FTP server</a></li>
<li><a href="http://libvirt.org/sources/">libvirt.org HTTP server</a></li>
docs: expand downloads page to cover all modules Previously the download page only covered the main libvirt module and the app dev guide. Expand it to provide direct links to all artifacts published by the project, whether the main library, language bindings, docs, or testing. Tweak the top table styling to better fit in with new branding. Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
2016-10-31 11:27:27 +00:00
<li><a href="https://libvirt.org/sources/">libvirt.org HTTPS server</a></li>
Split website out into one file per page. APply new layout and styling
2008-04-23 17:08:31 +00:00
</ul>
docs: added a table of contents to the first 11 docs files There are a 58 docs files, so adding an autogenerated Table Of Contents to them all will take some time. This is the first piece of the work done.
2010-10-23 21:46:32 +00:00
<h2><a name="hourly">Hourly development snapshots</a></h2>
Split website out into one file per page. APply new layout and styling
2008-04-23 17:08:31 +00:00
<p>
update download informations after switch to git * docs/downloads.html docs/downloads.html.in: update download informations after switch to git daniel
2009-07-06 12:27:00 +00:00
Once an hour, an automated snapshot is made from the git server
* proxy/libvirt_proxy.c and docs/* typo fixing Atsushi
2008-04-24 09:17:29 +00:00
source tree. These snapshots should be usable, but we make no guarantees
docs: mention maintenance branches Mitre tried to assign us two separate CVEs for the fix for https://bugzilla.redhat.com/show_bug.cgi?id=1047577, on the grounds that the fixes were separated by more than an hour and thus triggered different hourly snapshots. But we explicitly do NOT want to treat transient security bugs as CVEs if they can only be triggered by patches in libvirt.git but where the problem is cleaned up before a formal release. Meanwhile, I noticed that while our wiki mentioned maintenance branches and releases, our formal documentation did not. * docs/downloads.html.in: Contrast hourly snapshots with maintenance branches. Signed-off-by: Eric Blake <eblake@redhat.com>
2014-01-14 16:49:50 +00:00
about their stability; furthermore, they should NOT be
considered formal releases, and they may have transient security
problems that will not be assigned a CVE.
Split website out into one file per page. APply new layout and styling
2008-04-23 17:08:31 +00:00
</p>
<ul>
maint: Switch to xz compressed PAX release archives This allows us to produce releases that are roughly a third in size, have no limitation on path length, and are still readable by all supported platforms.
2016-06-15 11:19:32 +00:00
<li><a href="ftp://libvirt.org/libvirt/libvirt-git-snapshot.tar.xz">libvirt.org FTP server</a></li>
<li><a href="http://libvirt.org/sources/libvirt-git-snapshot.tar.xz">libvirt.org HTTP server</a></li>
Split website out into one file per page. APply new layout and styling
2008-04-23 17:08:31 +00:00
</ul>
Bump release to 2.0.0 and document release schedule & versioning 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@redhat.com>
2016-06-13 17:34:48 +00:00
<h2><a name="schedule">Primary release schedule</a></h2>
<p>
docs: expand downloads page to cover all modules Previously the download page only covered the main libvirt module and the app dev guide. Expand it to provide direct links to all artifacts published by the project, whether the main library, language bindings, docs, or testing. Tweak the top table styling to better fit in with new branding. Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
2016-10-31 11:27:27 +00:00
The core libvirt module 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
(first release in the middle of Jan, then skip the Feb release), giving
a total of 11 releases a year. The Python and Perl modules will aim to
release at the same time as the core libvirt module. Other modules have
independant ad-hoc releases with no fixed time schedle.
Bump release to 2.0.0 and document release schedule & versioning 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@redhat.com>
2016-06-13 17:34:48 +00:00
</p>
<h2><a name="numbering">Release numbering</a></h2>
<p>
Since libvirt 2.0.0, a time based version numbering rule
docs: expand downloads page to cover all modules Previously the download page only covered the main libvirt module and the app dev guide. Expand it to provide direct links to all artifacts published by the project, whether the main library, language bindings, docs, or testing. Tweak the top table styling to better fit in with new branding. Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
2016-10-31 11:27:27 +00:00
is applied to the core library releases. As such, the changes
in version number have do not have any implications with respect
to the scope of features 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:
Bump release to 2.0.0 and document release schedule & versioning 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@redhat.com>
2016-06-13 17:34:48 +00:00
</p>
Fix renumbering once again I screwed up by accidentally pushing incomplete version of the renumbering commit. This patch just fixes the rest so the tree matches changes in v2. Signed-off-by: Martin Kletzander <mkletzan@redhat.com>
2016-06-14 10:06:13 +00:00
<dl>
docs: Fix syntax-check Commit id '42ff399a' broke syntax-check by not encasing <dt> elements in <code>xxx</code>
2016-06-14 10:22:37 +00:00
<dt><code>major</code></dt>
Fix renumbering once again I screwed up by accidentally pushing incomplete version of the renumbering commit. This patch just fixes the rest so the tree matches changes in v2. Signed-off-by: Martin Kletzander <mkletzan@redhat.com>
2016-06-14 10:06:13 +00:00
<dd>incremented by 1 for the first release of the year (the
Jan 15th release)</dd>
docs: Fix syntax-check Commit id '42ff399a' broke syntax-check by not encasing <dt> elements in <code>xxx</code>
2016-06-14 10:22:37 +00:00
<dt><code>minor</code></dt>
docs: improve release numbering rule for minor numbers Adding first build of year minor number reset to 0. Signed-off-by: Boris Fiuczynski <fiuczy@linux.vnet.ibm.com> Signed-off-by: Martin Kletzander <mkletzan@redhat.com>
2016-11-30 12:04:04 +00:00
<dd>reset to 0 with every major increment, otherwise incremented by 1
for each monthly release from git master</dd>
docs: Fix syntax-check Commit id '42ff399a' broke syntax-check by not encasing <dt> elements in <code>xxx</code>
2016-06-14 10:22:37 +00:00
<dt><code>micro</code></dt>
Fix renumbering once again I screwed up by accidentally pushing incomplete version of the renumbering commit. This patch just fixes the rest so the tree matches changes in v2. Signed-off-by: Martin Kletzander <mkletzan@redhat.com>
2016-06-14 10:06:13 +00:00
<dd>always 0 for releases from git master, incremented by 1
for each stable maintenance release</dd>
</dl>
Bump release to 2.0.0 and document release schedule & versioning 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@redhat.com>
2016-06-13 17:34:48 +00:00
<p>
Fix renumbering once again I screwed up by accidentally pushing incomplete version of the renumbering commit. This patch just fixes the rest so the tree matches changes in v2. Signed-off-by: Martin Kletzander <mkletzan@redhat.com>
2016-06-14 10:06:13 +00:00
Prior to 2.0.0, the major/minor numbers were incremented
Bump release to 2.0.0 and document release schedule & versioning 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@redhat.com>
2016-06-13 17:34:48 +00:00
fairly arbitrarily, and maintenance releases appended a
docs: expand downloads page to cover all modules Previously the download page only covered the main libvirt module and the app dev guide. Expand it to provide direct links to all artifacts published by the project, whether the main library, language bindings, docs, or testing. Tweak the top table styling to better fit in with new branding. Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
2016-10-31 11:27:27 +00:00
fourth digit. The language bindings will aim to use the
same version number as the most recent core library API
they support. The other modules have their own distinct
release numbering sequence, though they generally aim
to follow the above rules for incrementing major/minor/micro
digits.
Bump release to 2.0.0 and document release schedule & versioning 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@redhat.com>
2016-06-13 17:34:48 +00:00
</p>
docs: mention maintenance branches Mitre tried to assign us two separate CVEs for the fix for https://bugzilla.redhat.com/show_bug.cgi?id=1047577, on the grounds that the fixes were separated by more than an hour and thus triggered different hourly snapshots. But we explicitly do NOT want to treat transient security bugs as CVEs if they can only be triggered by patches in libvirt.git but where the problem is cleaned up before a formal release. Meanwhile, I noticed that while our wiki mentioned maintenance branches and releases, our formal documentation did not. * docs/downloads.html.in: Contrast hourly snapshots with maintenance branches. Signed-off-by: Eric Blake <eblake@redhat.com>
2014-01-14 16:49:50 +00:00
<h2><a name="maintenance">Maintenance releases</a></h2>
<p>
docs: expand downloads page to cover all modules Previously the download page only covered the main libvirt module and the app dev guide. Expand it to provide direct links to all artifacts published by the project, whether the main library, language bindings, docs, or testing. Tweak the top table styling to better fit in with new branding. Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
2016-10-31 11:27:27 +00:00
In the git repository are several stable maintenance branches
for the core library, matching the
Bump release to 2.0.0 and document release schedule & versioning 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@redhat.com>
2016-06-13 17:34:48 +00:00
pattern <code>v<i>major</i>.<i>minor</i>-maint</code>;
docs: mention maintenance branches Mitre tried to assign us two separate CVEs for the fix for https://bugzilla.redhat.com/show_bug.cgi?id=1047577, on the grounds that the fixes were separated by more than an hour and thus triggered different hourly snapshots. But we explicitly do NOT want to treat transient security bugs as CVEs if they can only be triggered by patches in libvirt.git but where the problem is cleaned up before a formal release. Meanwhile, I noticed that while our wiki mentioned maintenance branches and releases, our formal documentation did not. * docs/downloads.html.in: Contrast hourly snapshots with maintenance branches. Signed-off-by: Eric Blake <eblake@redhat.com>
2014-01-14 16:49:50 +00:00
these branches are forked off the corresponding
Bump release to 2.0.0 and document release schedule & versioning 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@redhat.com>
2016-06-13 17:34:48 +00:00
<code>v<i>major</i>.<i>minor</i>.0</code> formal
docs: mention maintenance branches Mitre tried to assign us two separate CVEs for the fix for https://bugzilla.redhat.com/show_bug.cgi?id=1047577, on the grounds that the fixes were separated by more than an hour and thus triggered different hourly snapshots. But we explicitly do NOT want to treat transient security bugs as CVEs if they can only be triggered by patches in libvirt.git but where the problem is cleaned up before a formal release. Meanwhile, I noticed that while our wiki mentioned maintenance branches and releases, our formal documentation did not. * docs/downloads.html.in: Contrast hourly snapshots with maintenance branches. Signed-off-by: Eric Blake <eblake@redhat.com>
2014-01-14 16:49:50 +00:00
release, and may have further releases of the
Bump release to 2.0.0 and document release schedule & versioning 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@redhat.com>
2016-06-13 17:34:48 +00:00
form <code>v<i>major</i>.<i>minor</i>.<i>micro</i></code>.
docs: mention maintenance branches Mitre tried to assign us two separate CVEs for the fix for https://bugzilla.redhat.com/show_bug.cgi?id=1047577, on the grounds that the fixes were separated by more than an hour and thus triggered different hourly snapshots. But we explicitly do NOT want to treat transient security bugs as CVEs if they can only be triggered by patches in libvirt.git but where the problem is cleaned up before a formal release. Meanwhile, I noticed that while our wiki mentioned maintenance branches and releases, our formal documentation did not. * docs/downloads.html.in: Contrast hourly snapshots with maintenance branches. Signed-off-by: Eric Blake <eblake@redhat.com>
2014-01-14 16:49:50 +00:00
These maintenance branches should only contain bug fixes, and no
new features, backported from the master branch, and are
supported as long as at least one downstream distribution
expresses interest in a given branch. These maintenance
Bump release to 2.0.0 and document release schedule & versioning 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@redhat.com>
2016-06-13 17:34:48 +00:00
branches are considered during CVE analysis. In contrast
to the primary releases which are made once a month, there
is no formal schedule for the maintenance releases, which
are made whenever there is a need to make available key
docs: expand downloads page to cover all modules Previously the download page only covered the main libvirt module and the app dev guide. Expand it to provide direct links to all artifacts published by the project, whether the main library, language bindings, docs, or testing. Tweak the top table styling to better fit in with new branding. Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
2016-10-31 11:27:27 +00:00
bugfixes to downstream consumers. The language bindings
and other modules generally do not provide stable branch
releases.
docs: mention maintenance branches Mitre tried to assign us two separate CVEs for the fix for https://bugzilla.redhat.com/show_bug.cgi?id=1047577, on the grounds that the fixes were separated by more than an hour and thus triggered different hourly snapshots. But we explicitly do NOT want to treat transient security bugs as CVEs if they can only be triggered by patches in libvirt.git but where the problem is cleaned up before a formal release. Meanwhile, I noticed that while our wiki mentioned maintenance branches and releases, our formal documentation did not. * docs/downloads.html.in: Contrast hourly snapshots with maintenance branches. Signed-off-by: Eric Blake <eblake@redhat.com>
2014-01-14 16:49:50 +00:00
</p>
<p>
For more details about contents of maintenance releases, see
<a href="http://wiki.libvirt.org/page/Maintenance_Releases">the
wiki page</a>.
</p>
docs: added a table of contents to the first 11 docs files There are a 58 docs files, so adding an autogenerated Table Of Contents to them all will take some time. This is the first piece of the work done.
2010-10-23 21:46:32 +00:00
<h2><a name="git">GIT source repository</a></h2>
docs: add the app dev guide Added a workable initial page for the libvirt Application Development Guide, giving the online viewable options + the available download ones (pdf, epub, srpm). Added a link to the PDF to the main Downloads page, plus neatened the html tags throughout the page as they were a bit of a mess. Added --enable-compile-warnings=error to the autogen line, as suggested by Eric Blake.
2010-09-10 09:26:05 +00:00
<p>
docs: expand downloads page to cover all modules Previously the download page only covered the main libvirt module and the app dev guide. Expand it to provide direct links to all artifacts published by the project, whether the main library, language bindings, docs, or testing. Tweak the top table styling to better fit in with new branding. Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
2016-10-31 11:27:27 +00:00
All modules maintained by the libvirt project have their primary
source available in the <a href="http://libvirt.org/git/">project GIT server</a>.
Each module can be cloned anonymously using:
docs: add the app dev guide Added a workable initial page for the libvirt Application Development Guide, giving the online viewable options + the available download ones (pdf, epub, srpm). Added a link to the PDF to the main Downloads page, plus neatened the html tags throughout the page as they were a bit of a mess. Added --enable-compile-warnings=error to the autogen line, as suggested by Eric Blake.
2010-09-10 09:26:05 +00:00
</p>
<pre>
downloads.html.in: Kill useless spaces in <pre/> The <pre/> section is rendered as-is on the page. That is, if all the lines are prefixed with 4 spaces the rendered page will also have them. Problem is if we put a box around such <pre/> because the content might not fix into it. Signed-off-by: Michal Privoznik <mprivozn@redhat.com>
2016-11-11 22:40:27 +00:00
git clone git://libvirt.org/[module name].git</pre>
docs: add the app dev guide Added a workable initial page for the libvirt Application Development Guide, giving the online viewable options + the available download ones (pdf, epub, srpm). Added a link to the PDF to the main Downloads page, plus neatened the html tags throughout the page as they were a bit of a mess. Added --enable-compile-warnings=error to the autogen line, as suggested by Eric Blake.
2010-09-10 09:26:05 +00:00
docs: Document new RO repo mirrors In the upstream discussion on creating a github mirror [1], it turned out that there are some read-only mirrors of our repository. Lets advertise them on our downloads page. But do it wisely and discourage people in sending a pull requests on GitHub. 1: https://www.redhat.com/archives/libvir-list/2015-May/msg00775.html Signed-off-by: Michal Privoznik <mprivozn@redhat.com>
2015-05-23 05:48:37 +00:00
<p>
docs: expand downloads page to cover all modules Previously the download page only covered the main libvirt module and the app dev guide. Expand it to provide direct links to all artifacts published by the project, whether the main library, language bindings, docs, or testing. Tweak the top table styling to better fit in with new branding. Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
2016-10-31 11:27:27 +00:00
In addition to this primary repository, there are the following read-only git
docs: Document new RO repo mirrors In the upstream discussion on creating a github mirror [1], it turned out that there are some read-only mirrors of our repository. Lets advertise them on our downloads page. But do it wisely and discourage people in sending a pull requests on GitHub. 1: https://www.redhat.com/archives/libvir-list/2015-May/msg00775.html Signed-off-by: Michal Privoznik <mprivozn@redhat.com>
2015-05-23 05:48:37 +00:00
repositories which mirror the master one. Note that we currently do not
use the full set of features on these mirrors (e.g. pull requests on
GitHub, so please don't use them). All patch review and discussion only
occurs on the <a href="contact.html">libvir-list</a> mailing list. Also
note that some repositories listed below allow HTTP checkouts too.
</p>
<pre>
downloads.html.in: Kill useless spaces in <pre/> The <pre/> section is rendered as-is on the page. That is, if all the lines are prefixed with 4 spaces the rendered page will also have them. Problem is if we put a box around such <pre/> because the content might not fix into it. Signed-off-by: Michal Privoznik <mprivozn@redhat.com>
2016-11-11 22:40:27 +00:00
<a href="https://github.com/libvirt/">https://github.com/libvirt/</a>
<a href="https://gitlab.com/libvirt/libvirt">https://gitlab.com/libvirt/</a></pre>
docs: add the app dev guide Added a workable initial page for the libvirt Application Development Guide, giving the online viewable options + the available download ones (pdf, epub, srpm). Added a link to the PDF to the main Downloads page, plus neatened the html tags throughout the page as they were a bit of a mess. Added --enable-compile-warnings=error to the autogen line, as suggested by Eric Blake.
2010-09-10 09:26:05 +00:00
Split website out into one file per page. APply new layout and styling
2008-04-23 17:08:31 +00:00
</body>
</html>
Reference in New Issue Copy Permalink