+1

Arbin Darren Sanders
 
Information Technology Manager - Academic Support Services
Information Technology Services
North Carolina Central University
712 Cecil Street
Suite 3014
Durham, NC 27707
919.530.6307
919.530.5097 (Fax)

 
CONFIDENTIALITY: This email (including any attachments) may contain 
confidential, proprietary and privileged information, and unauthorized 
disclosure or use is prohibited. If you received this email in error, please 
notify the sender and delete this e-mail from your system.


-----Original Message-----
From: Josh Thompson [mailto:[email protected]] 
Sent: Tuesday, July 17, 2012 3:44 PM
To: [email protected]
Subject: [VOTE] release VCL 2.3 (graduated, based on RC4)

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

So, we've finally graduated and mostly migrated out of the incubator.  We can 
now start the process of making our first *official* ASF release!  (The 
previous ones had a disclaimer that they were not fully endorsed by ASF since 
we were still in the incubator.)

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.3-RC4:

http://svn.apache.org/repos/asf/vcl/tags/release-2.3-RC4/

(note that 'incubator/' has been dropped from the repo path)

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-RC4/

(no more -incubating at the end!)

The list of resolved JIRA issues associated with this release can be found 
under Change Log on the VCL 2.3 release page:

https://cwiki.apache.org/VCL/vcl-23.html#VCL2.3-ChangeLog

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

I tested doing an install and several parts of the website, including doing a 
few deploys.

The directory created by extracting the RC4 artifact is "apache-VCL-2.3-RC4" 
(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.

Please vote by the 4pm EST on Friday, July 20th to publish this release (this 
allows for 3 business days to vote).  Please note that anyone in the VCL 
community is allowed to vote.  I'll close the vote Friday afternoon (assuming I 
don't have to cancel it for another bug...).  At that point, we'll be ready to 
release it!  As a TLP, we no longer need to submit our vote to another group.  
Yay for graduating!

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

Josh Thompson
Apache VCL Release Manager
- --
- -------------------------------
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.17 (GNU/Linux)

iEYEARECAAYFAlAFwIwACgkQV/LQcNdtPQOutACdFALcs/XnZuTK7P8upI4V1Pfl
jQAAnR9Ku8+fwxoUKfvrys2BTOXY5ulc
=wsRW
-----END PGP SIGNATURE-----


______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com 
______________________________________________________________________

______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
______________________________________________________________________

Reply via email to