diff --git a/docs/downloads.html.in b/docs/downloads.html.in index 1a3400af16..eb1dd27b83 100644 --- a/docs/downloads.html.in +++ b/docs/downloads.html.in @@ -6,15 +6,337 @@
- The latest versions of the libvirt C library can be downloaded from: + The libvirt project maintains a number of inter-related modules beyond + the core C library/daemon. +
+ +Module | +Releases | +GIT Repo | +GIT Mirrors | +|||
---|---|---|---|---|---|---|
libvirt | ++ ftp + http + https + | ++ libvirt + | ++ gitlab + github + | +|||
Language bindings | +||||||
C# | ++ ftp + http + https + | ++ libvirt + | ++ gitlab + github + | +|||
Java | ++ ftp + http + https + | ++ libvirt + | ++ gitlab + github + | +|||
OCaml | ++ ftp + http + https + | ++ libvirt + | ++ gitlab + github + | +|||
Perl (Sys::Virt) | ++ cpan + | ++ libvirt + | ++ gitlab + github + | +|||
PHP | ++ ftp + http + https + | ++ libvirt + | ++ gitlab + github + | +|||
Python | ++ ftp + http + https + pypi + | ++ libvirt + | ++ gitlab + github + | +|||
Ruby | ++ ftp + http + https + | ++ libvirt + | ++ gitlab + github + | +|||
Integration modules | +||||||
GLib / GConfig / GObject | ++ ftp + http + https + | ++ libvirt + | ++ gitlab + github + | +|||
CIM provider | ++ ftp + http + https + | ++ libvirt + | ++ gitlab + github + | +|||
CIM utils | ++ ftp + http + https + | ++ libvirt + | ++ gitlab + github + | +|||
SNMP | ++ ftp + http + https + | ++ libvirt + | ++ gitlab + github + | +|||
Application Sandbox | ++ ftp + http + https + | ++ libvirt + | ++ gitlab + github + | +|||
Testing | +||||||
TCK | ++ ftp + http + https + | ++ libvirt + | ++ gitlab + github + | +|||
Test API | ++ | + libvirt + | ++ gitlab + github + | +|||
Jenkins Config | ++ | + libvirt + | ++ gitlab + github + | +|||
CIM Test | ++ | + libvirt + | ++ gitlab + github + | +|||
Documentation | +||||||
Publican Brand | ++ | + libvirt + | ++ gitlab + github + | +|||
App Development Guide | ++ | + libvirt + | ++ gitlab + github + | +|||
App Development Guide Python | ++ | + libvirt + | ++ gitlab + github + | +|||
virsh Command Reference | ++ | + libvirt + | ++ gitlab + github + | +
+ 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.
- 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 (first - release in the middle of Jan, then skip the Feb release), giving - a total of 11 releases a year. + 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.
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 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: + 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:
Prior to 2.0.0, the major/minor numbers were incremented fairly arbitrarily, and maintenance releases appended a - fourth digit. + 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.
- In the git repository are several stable maintenance branches,
- matching the
+ In the git repository are several stable maintenance branches
+ for the core library, matching the
pattern vmajor.minor-maint
;
these branches are forked off the corresponding
vmajor.minor.0
formal
@@ -88,7 +417,9 @@
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
- bugfixes to downstream consumers.
+ bugfixes to downstream consumers. The language bindings
+ and other modules generally do not provide stable branch
+ releases.
@@ -100,22 +431,16 @@
- Libvirt code source is now maintained in a git - repository available on libvirt.org: + All modules maintained by the libvirt project have their primary + source available in the project GIT server. + Each module can be cloned anonymously using:
- git clone git://libvirt.org/libvirt.git+ git clone git://libvirt.org/[module name].git
- It can also be browsed at: -
- -- http://libvirt.org/git/?p=libvirt.git;a=summary- -
- In addition to this repository, there are the following read-only git + In addition to this primary repository, there are the following read-only git 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 @@ -124,58 +449,8 @@
- https://github.com/libvirt/libvirt - http://repo.or.cz/w/libvirt.git - https://gitlab.com/libvirt/libvirt+ https://github.com/libvirt/ + https://gitlab.com/libvirt/ -
- The guide is both a learning tool for developing with libvirt and an - API reference document. It is a work in progress, composed by a - professional author from contributions written by members of the - libvirt team. -
- -- Contributions to the guide are VERY welcome. If you'd like to get - your name on this and demonstrate your virtualisation prowess, a solid - contribution to the content here will do it. :) -
- -- PDF download is available here: -
- -- The source is also in a git repository: -
- -- git clone git://libvirt.org/libvirt-appdev-guide.git- -
- Browsable at: -
- -- http://libvirt.org/git/?p=libvirt-appdev-guide.git;a=summary- -
- Once you've have obtained the libvirt source code, you can compile it - using the instructions here. -