+1

On Dec 13, 2012, at 15:02 , Josh Thompson <[email protected]> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> All of the JIRA issues associated with 2.3.1 are now resolved.  Here is our 
> first try at voting to release 2.3.1.
> 
> I created a release artifact based off of the 2.3 bugfixes branch.  I copied 
> that branch to a tag under the tags area of the repo that is named 
> release-2.3.1-RC1:
> 
> http://svn.apache.org/repos/asf/vcl/tags/release-2.3.1-RC1/
> 
> The artifact is an export from that tag with the addition of Dojo Toolkit
> version 1.6.1 with a custom VCL profile 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.3.1-RC1/
> 
> The list of resolved JIRA issues associated with this release can be found
> under 2.3.1 on the Change Log page in the staging area of the CMS:
> 
> http://vcl.staging.apache.org/docs/changelog.html
> 
> Installation instructions are in the INSTALLATION file included in the 
> artifact and in the staging area of the CMS:
> 
> http://vcl.staging.apache.org/docs/VCL231InstallGuide.html
> 
> 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.3.1-RC1" 
> (after extracting, you may want to rename it to "apache-VCL-2.3" 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.
> 
> After we finalize a release vote, the staging part of the CMS will be 
> published to update the production site.
> 
> Please vote by the end of the day on Tuesday, December 18th 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.3.1
> [ ] 0 dunno
> [ ] -1 no, don't release VCL 2.3.1 (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)
> 
> iEYEARECAAYFAlDKNEUACgkQV/LQcNdtPQMUvwCffbtpAkdndWQk3MMPmEJTQ2C3
> amMAn1HOeZpi3lfmRLhW6MP7VFQ8g96u
> =OiBv
> -----END PGP SIGNATURE-----
> 



--
Thank you,

Dmitri Chebotarov
VCL Sys Eng, Engineering & Architectural Support, TSD - Ent Servers & Messaging
223 Aquia Building, Ffx, MSN: 1B5
Phone: (703) 993-6175 | Fax: (703) 993-3404



Reply via email to