It's my understanding the Perl Artistic license is compatible with AL
2.0 in that we are allowed to build and distribute software on the
required artifacts delivered via CPAN.
On Nov 12, 2009, at 1:49 PM, Josh Thompson wrote:
-----BEGIN PGP SIGNED MESSAGE-----
I created a release artifact based off of trunk. I copied trunk to
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
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
the VCL 2.1 release page (this has been regenerated for RC2):
Installation instructions are on the Confluence site and in the
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
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
that they are "system requirements" according to the information
under "System Requirements" on http://www.apache.org/legal/
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 allows for 3 business days to vote). Please note that anyone
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
Advanced Computing | VCL Developer
North Carolina State University
my GPG/PGP key can be found at pgp.mit.edu
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
-----END PGP SIGNATURE-----