You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@vcl.apache.org by Josh Thompson <jo...@ncsu.edu> on 2012/12/17 18:57:30 UTC

Re: [VOTE][ENDED] release 2.3.1 (RC2)

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

Aaron noticed that the link to the online install guide in the README file was 
not updated for 2.3.1.  I'm ending this vote and creating RC3...

Josh

On Monday, December 17, 2012 9:40:01 AM you wrote:
> My apologies.  When I updated my script that generates RC's, I missed that
> it  was pulling from trunk instead of the bugfix branch.  My testing had
> actually been done directly from subversion instead of from the RC.
> 
> I created a new release artifact that really is 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-RC2:
> 
> http://svn.apache.org/repos/asf/vcl/tags/release-2.3.1-RC2/
> 
> 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-RC2/
> 
> 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 RC2 artifact is
> "apache-VCL-2.3.1-RC2" (after extracting, you may want to rename it to
> "apache-VCL-2.3.1" 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 Wednesday, December 19th to publish
> this release (this allows for about 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.
- -- 
- -------------------------------
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)

iEYEARECAAYFAlDPXQ4ACgkQV/LQcNdtPQNJ9wCfZ3n9E3ebxwxB7eVLhUERntqO
5fIAnjsfoz6BPXP0idfwW02hzDa717VY
=iouR
-----END PGP SIGNATURE-----