Difference between revisions of "OpenVZ infrastructure"
(Add more details about infrastructure) |
(git.openvz.org -> src.openvz.org) |
||
| Line 6: | Line 6: | ||
== Code == | == Code == | ||
| − | We have a single place for all OpenVZ source code. It is a [https:// | + | We have a single place for all OpenVZ source code. It is a [https://src.openvz.org/ src.openvz.org]. |
| − | We use [https://git-scm.herokuapp.com/ GIT SCM] to track changes in source code. Each OpenVZ component is a separate GIT repository. All patches should be reviewed before committing to repository. Please read article [[How to submit patches]] before sending patch. Each repository on | + | We use [https://git-scm.herokuapp.com/ GIT SCM] to track changes in source code. Each OpenVZ component is a separate GIT repository. All patches should be reviewed before committing to repository. Please read article [[How to submit patches]] before sending patch. Each repository on src.openvz.org has a mirror on [https://github.com/OpenVZ Github account OpenVZ] for your convenience. |
== Bugs == | == Bugs == | ||
Revision as of 06:30, 29 April 2015
This article is a stub. You can help OpenVZ Wiki by expanding it.
This article describes OpenVZ standalone services.
Code
We have a single place for all OpenVZ source code. It is a src.openvz.org. We use GIT SCM to track changes in source code. Each OpenVZ component is a separate GIT repository. All patches should be reviewed before committing to repository. Please read article How to submit patches before sending patch. Each repository on src.openvz.org has a mirror on Github account OpenVZ for your convenience.
Bugs
OpenVZ project is not bug free project. We use Bugzilla for tracking all OpenVZ bugs. Please read about bug lifecycle before starting to work with bugs.
Download
All OpenVZ download files are placed on download.openvz.org and available for download via http and ftp protocols. Download server also has a list of mirrors in different countries. You can help to OpenVZ by setup a mirror.
