-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Some of the issues fixed in 2.3.2 were worth back porting to the 2.2 series so 
that people can get the updates without having to do an upgrade to the 2.3 
series.  Along with those, I've incorporated most of the bugs that have been 
fixed in the code since the 2.2.1 release.  No features have been back ported.

I created a bugfixes branch from the 2.2 release tag and checked updates in to 
that.  I then created a release artifact based off of this updated 2.2 
bugfixes branch.  I copied that branch to a tag under the tags area of the 
repo that is named release-2.2.2-RC1:

http://svn.apache.org/repos/asf/vcl/tags/release-2.2.2-RC1/

The artifact is an export from that tag with the addition of Dojo Toolkit
version 1.5.0 bundled in the web code.  The artifact, MD5 and SHA1 sums, and 
my GPG signature of it are available from my space on people.a.o:

http://people.apache.org/~jfthomps/apache-VCL-2.2.2-RC1/

The list of resolved JIRA issues associated with this release can be found
here:

https://issues.apache.org/jira/issues/?jql=project%20%3D%20VCL%20AND%20fixVersion%20%3D%20%222.2.2%22%20AND%20status%20%3D%20Resolved%20ORDER%20BY%20priority%20DESC

Installation instructions are in the INSTALLATION file included in the 
artifact.

I was able to successfully do test installs and upgrades, including image 
deploying and capture.

The directory created by extracting the RC1 artifact is "apache-VCL-2.2.2-RC1" 
(after extracting, you may want to rename it to "apache-VCL-2.2.2" so you can 
copy and paste all of the commands in the installation guide).  Licensing 
information about perl and its required modules, php and its required modules, 
and mysql are stated as "system requirements" according to the information 
under "System Requirements" on http://www.apache.org/legal/3party.html.

All of the upgrade, release notes, changelog and download content for the web 
site has been updated in the staging area.  I did not create an online 
installation page for 2.2.2 since it should really only be used as an upgrade.  
New installations should use the latest release from the 2.3 series.

After we finalize a release vote, I'll publish the site and send an 
announcement of the release.

Please vote by the end of the day on Sunday, March 24th to publish this
release.  Everyone in the community is encouraged to vote.

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

Josh
- -- 
- -----------------------------
Josh Thompson
VCL Developer
North Carolina State University

my GPG/PGP key can be found at pgp.mit.edu

All electronic mail messages in connection with State business which
are sent to or received by this account are subject to the NC Public
Records Law and may be disclosed to third parties.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)

iEYEARECAAYFAlFJ00MACgkQV/LQcNdtPQMnNgCdEh07ErG7ij5eIRtMKBKOrbXv
JXUAn0HDrISAI1G2IuEasXW11Ob8S5hq
=Bcfq
-----END PGP SIGNATURE-----

Reply via email to