--- On Thu, 11/12/09, Josh Thompson <josh_thomp...@ncsu.edu> wrote:

From: Josh Thompson <josh_thomp...@ncsu.edu>
Subject: [VOTE] release VCL 2.1
To: vcl-dev@incubator.apache.org
Cc: "Matt Hogstrom" <m...@hogstrom.org>, "Kevan Miller" 
<kevan.mil...@gmail.com>, "Alan D. Cabrera" <l...@toolazydogs.com>
Date: Thursday, November 12, 2009, 4:49 PM

Hash: SHA1

I created a release artifact based off of trunk.  I copied trunk to a tag 
under the tags area of the repo that is named release-2.1-RC2:


The artifact is an export from that tag.  The artifact, MD5 and SHA1 sums, and 
my GPG signature of it are available from my space on people.a.o:


The list of resolved JIRA issues associated with this release can be found on 
the VCL 2.1 release page (this has been regenerated for RC2):


Installation instructions are on the Confluence site and in the INSTALLATION 
file included in the artifact.

Aaron, Andy, and I have completed a test install of all parts and were able to 
successfully create and capture a base image (we did not repeat this for RC2 
because there were only a few very minor bugfixes).

The directory created by extracting the RC2 artifact 
is "apache-VCL-2.1-RC2-incubating".  Licensing information about perl and its 
required modules, php and its required modules, and mysql has been restated 
that they are "system requirements" according to the information 
under "System Requirements" on http://www.apache.org/legal/3party.html.  It's 
also worth noting that the roadmap has been slightly updated.

Please vote by the end of the day on Tuesday, Nov 17th to publish this release 
(this allows for 3 business days to vote).  Please note that anyone in the 
VCL community is allowed to vote.

[ ] +1 yes, release VCL 2.1
[ ] 0 dunno
[ ] -1 no, don't release VCL 2.1 (provide reasons if this is your vote)

- -- 
- -------------------------------
Josh Thompson
Systems Programmer
Advanced Computing | VCL Developer
North Carolina State University


my GPG/PGP key can be found at pgp.mit.edu
Version: GnuPG v1.4.6 (GNU/Linux)



Reply via email to