Hi Joe , +1 .Looks nice .
Also would it be a good idea to have a link or a reference to the file you mentioned here (which has a list of changes involved in the 4.0.1 release) in the release note itself ? Regards, Pranav -----Original Message----- From: Joe Brockmeier [mailto:[email protected]] Sent: Tuesday, February 05, 2013 11:36 AM To: [email protected]; CloudStack Developers Subject: [DRAFT][DISCUSS] Hi all, Draft release announcement for 4.0.1-incubating attached. Please submit any comments or corrections within 72 hours. Thanks! Apache CloudStack 4.0.1-incubating Released The Apache CloudStack project is pleased to announce the 4.0.1-incubating release of the CloudStack Infrastructure-as-a-Service (IaaS) cloud orchestration platform. This is a minor release in the 4.0.0 branch, which contains fixes for more than 30 bugs. Apache CloudStack is an integrated software platform that allows users to build a feature-rich IaaS. CloudStack includes an intuitive user interface and rich API for managing the compute, networking, accounting, and storage for private, hybrid, or public clouds. The project entered the Apache Incubator in April 2012. The 4.0.1-incubating release includes fixes for a number of issues, including a minor security vulnerability (CVE-2012-5616), problems adding KVM hosts, fixes to documentation, and more. Please see the CHANGES file in the release for a full list of issues that are fixed in this release. As a bugfix release, no new features are included in 4.0.1-incubating, and it should be a simple upgrade from 4.0.0-incubating. ##Downloads The official source code release can be downloaded from: http://incubator.apache.org/cloudstack/downloads.html In addition to the official source code release, individual contributors have also made convenience binaries available on the Apache CloudStack download page. ##Incubating Apache CloudStack is an effort undergoing incubation at The Apache Software Foundation (ASF). Incubation is required of all newly accepted projects until a further review indicates that the infrastructure, communications, and decision making process have stabilized in a manner consistent with other successful ASF projects. While incubation status is not necessarily a reflection of the completeness or stability of the code, it does indicate that the project has yet to be fully endorsed by the ASF. ###
