March 25th, 2006
This week was a huge move forward for the OpenVZ project. We have released an updated vzctl, an updated stable kernel, a new development kernel based on 2.6.16, a SUSE kernel, a template for Fedora Core 5 (FC5 was itself released 20 Mar), and finally a GIT repository with our development kernel.
The GIT repository serves two purposes. First one is to make our development process more open and transparent — indeed, now everybody can track our progress, see all those patches while they are being added, in a real time, not just after a release. And if you want to stay on the cutting edge of OpenVZ, do a git clone and then a regular git pull. GIT docs are here.
Second purpose of GIT is to help us with the mainstream integration. For that, there is a linux-2.6-openvz-ms project added, which contains just stuff needed to be added into mainstream. Kirill Korotaev has already submitted a couple of patches for IPC and utsname virtualization (which is quite straightforward and can be agreed upon more easily). Like in the previous round, it received a lot of attention and comments since different people/groups have different approaches and usage cases in mind. We believe it will work out fine, since we are reacting to the comments trying to make the code as excellent as possible and satisfy everybody.
The GIT repository serves two purposes. First one is to make our development process more open and transparent — indeed, now everybody can track our progress, see all those patches while they are being added, in a real time, not just after a release. And if you want to stay on the cutting edge of OpenVZ, do a git clone and then a regular git pull. GIT docs are here.
Second purpose of GIT is to help us with the mainstream integration. For that, there is a linux-2.6-openvz-ms project added, which contains just stuff needed to be added into mainstream. Kirill Korotaev has already submitted a couple of patches for IPC and utsname virtualization (which is quite straightforward and can be agreed upon more easily). Like in the previous round, it received a lot of attention and comments since different people/groups have different approaches and usage cases in mind. We believe it will work out fine, since we are reacting to the comments trying to make the code as excellent as possible and satisfy everybody.

Comments
Do you still stand by your opinions above now in 2016?…