Author: jfthomps
Date: Thu Sep 16 19:02:28 2010
New Revision: 997882

URL: http://svn.apache.org/viewvc?rev=997882&view=rev
Log:
changed version number

removed 2.1 from roadmap

swapped cluster reservations and vmware free server 2.x between 2.2 and 2.3

added note for people wanting to develop something for VCL explaining to 
discuss things on the vcl-dev list before starting work on it

Modified:
    incubator/vcl/trunk/RELEASE_NOTES

Modified: incubator/vcl/trunk/RELEASE_NOTES
URL: 
http://svn.apache.org/viewvc/incubator/vcl/trunk/RELEASE_NOTES?rev=997882&r1=997881&r2=997882&view=diff
==============================================================================
--- incubator/vcl/trunk/RELEASE_NOTES (original)
+++ incubator/vcl/trunk/RELEASE_NOTES Thu Sep 16 19:02:28 2010
@@ -1,4 +1,4 @@
-VCL 2.1
+VCL 2.2
 
 I. Intro and Description
 
@@ -21,22 +21,15 @@ servers in a server farm or HPC cluster.
 
 II. VCL Roadmap
 
-VCL 2.1 (this release)
-  * completed modularization of vcld
-  * xCAT 2.1 support
-  * Shibboleth authentication
-  * VMWare management via VMWare toolkit
-  * ESXi with thin provisioning on a NetApp
-
-VCL 2.2
+VCL 2.2 (this release)
   * support for xCAT 2.3
-  * improve cluster reservations
-  * improve block reservations(rename to block allocations)
+  * VMWare Free Server 2.x
+  * improve block reservations (renamed to block allocations)
 
 VCL 2.3
   * Service deployments 
   * power management
-  * VMWare Free Server 2.x
+  * improve cluster reservations
 
 VCL 2.4
   * improve hypervisor support
@@ -83,6 +76,11 @@ There are five ways to become involved i
   and having a committer account created to directly contribute code to the
   project.
 
+* If you are interested in contributing something to the project, please 
discuss
+  it on the vcl-dev list BEFORE starting work on it. This allows the community
+  to be involved in decisions and allows current developers to provide some
+  guidance.
+
 IV. How to Submit Bugs and Feature Requests
 
 If you find a bug, please submit a bug report to our JIRA bug tracking system 
at


Reply via email to