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 2013/03/20 16:18:19 UTC
[VOTE] release 2.2.2 (RC1) - note the *2* in the middle
-----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-----
Re: [VOTE] release 2.2.2 (RC1) - note the *2* in the middle
Posted by Henry Schaffer <he...@ncsu.edu>.
+1
--henry
On Wed, Mar 20, 2013 at 11:18 AM, Josh Thompson <jo...@ncsu.edu> wrote:
> -----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-----
>
Re: [VOTE][RESULT] release 2.2.2 (RC1) - note the *2* in the middle
Posted by Josh Thompson <jo...@ncsu.edu>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Based on the following votes, the Apache VCL community has voted to release
Apache VCL 2.2.2:
Henry Schaffer
Andy Kurth (PMC chair)
Josh Thompson (PMC member)
Larry Burton
Aaron Peeler (PMC member)
Aaron Coburn (PMC member)
Young Oh
Ivan Rako
That's +4 from PMC members and another +4 from the community. There were no 0
or -1 votes. That gives a total of 8 to pass the vote.
I'll go ahead and create the release artifact and publish it to our
distribution location. I'll give it around 24 hours for all of the mirrors to
pick it up and then send out an [ANNOUNCE] message.
Thanks,
Josh
On Wednesday, March 20, 2013 11:18:19 AM Josh Thompson wrote:
> 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%20fixVe
> rsion%20%3D%20%222.2.2%22%20AND%20status%20%3D%20Resolved%20ORDER%20BY%20pri
> ority%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.
- --
- -------------------------------
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)
iEYEARECAAYFAlFQm7AACgkQV/LQcNdtPQNK4gCfakI/dwwm803wqCmruQ+/lBVz
Kn4An1d26kvWsWjpmnFCmCLKy0y1upgH
=2zLG
-----END PGP SIGNATURE-----
Re: [VOTE] release 2.2.2 (RC1) - note the *2* in the middle
Posted by Young h Oh <oh...@us.ibm.com>.
+1
Young Hyun Oh
From: Josh Thompson <jo...@ncsu.edu>
To: dev@vcl.apache.org, user@vcl.apache.org,
Date: 03/20/2013 11:20 AM
Subject: [VOTE] release 2.2.2 (RC1) - note the *2* in the middle
-----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-----
Re: [VOTE] release 2.2.2 (RC1) - note the *2* in the middle
Posted by Andy Kurth <ar...@ncsu.edu>.
+1
-Andy
On 3/20/2013 11:18 AM, Josh Thompson wrote:
> -----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-----
>
Re: [VOTE] release 2.2.2 (RC1) - note the *2* in the middle
Posted by Ivan Rako <ir...@srce.hr>.
On Wed, Mar 20, 2013 at 11:18:19AM -0400, Josh Thompson wrote:
> [ ] +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)
+1
Best regards,
i.
--
Computer Systems Department
University of Zagreb, University Computing Centre, www.srce.unizg.hr
ivan.rako@srce.hr, tel: +385 1 616 5545, fax: +385 1 616 5559
Re: [VOTE] release 2.2.2 (RC1) - note the *2* in the middle
Posted by Aaron Peeler <fa...@ncsu.edu>.
+1
On Wed, Mar 20, 2013 at 11:18 AM, Josh Thompson <jo...@ncsu.edu> wrote:
> -----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-----
>
--
Aaron Peeler
Program Manager
Virtual Computing Lab
NC State University
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.
Re: [VOTE] release 2.2.2 (RC1) - note the *2* in the middle
Posted by Young h Oh <oh...@us.ibm.com>.
+1
Young Hyun Oh
From: Josh Thompson <jo...@ncsu.edu>
To: dev@vcl.apache.org, user@vcl.apache.org,
Date: 03/20/2013 11:20 AM
Subject: [VOTE] release 2.2.2 (RC1) - note the *2* in the middle
-----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-----
Re: [VOTE] release 2.2.2 (RC1) - note the *2* in the middle
Posted by Aaron Coburn <ac...@amherst.edu>.
+1
Aaron Coburn
On Mar 20, 2013, at 11:18 AM, Josh Thompson <jo...@ncsu.edu> wrote:
> -----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-----
>
Re: [VOTE] release 2.2.2 (RC1) - note the *2* in the middle
Posted by Aaron Coburn <ac...@amherst.edu>.
+1
Aaron Coburn
On Mar 20, 2013, at 11:18 AM, Josh Thompson <jo...@ncsu.edu> wrote:
> -----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-----
>
Re: [VOTE][RESULT] release 2.2.2 (RC1) - note the *2* in the middle
Posted by Josh Thompson <jo...@ncsu.edu>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Based on the following votes, the Apache VCL community has voted to release
Apache VCL 2.2.2:
Henry Schaffer
Andy Kurth (PMC chair)
Josh Thompson (PMC member)
Larry Burton
Aaron Peeler (PMC member)
Aaron Coburn (PMC member)
Young Oh
Ivan Rako
That's +4 from PMC members and another +4 from the community. There were no 0
or -1 votes. That gives a total of 8 to pass the vote.
I'll go ahead and create the release artifact and publish it to our
distribution location. I'll give it around 24 hours for all of the mirrors to
pick it up and then send out an [ANNOUNCE] message.
Thanks,
Josh
On Wednesday, March 20, 2013 11:18:19 AM Josh Thompson wrote:
> 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%20fixVe
> rsion%20%3D%20%222.2.2%22%20AND%20status%20%3D%20Resolved%20ORDER%20BY%20pri
> ority%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.
- --
- -------------------------------
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)
iEYEARECAAYFAlFQm7AACgkQV/LQcNdtPQNK4gCfakI/dwwm803wqCmruQ+/lBVz
Kn4An1d26kvWsWjpmnFCmCLKy0y1upgH
=2zLG
-----END PGP SIGNATURE-----
Re: [VOTE] release 2.2.2 (RC1) - note the *2* in the middle
Posted by Josh Thompson <jo...@ncsu.edu>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
+1
On Wednesday, March 20, 2013 11:18:19 AM I wrote:
> 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%20fixVe
> rsion%20%3D%20%222.2.2%22%20AND%20status%20%3D%20Resolved%20ORDER%20BY%20pri
> ority%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.
- --
- -------------------------------
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)
iEYEARECAAYFAlFKHsgACgkQV/LQcNdtPQOfVQCcCOvMJw86jA5KTSSsViSsWgQN
E8gAn1znecJPgaDOwazU8wIhUV5oRvgu
=Vvpp
-----END PGP SIGNATURE-----
Re: [VOTE] release 2.2.2 (RC1) - note the *2* in the middle
Posted by Josh Thompson <jo...@ncsu.edu>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
+1
On Wednesday, March 20, 2013 11:18:19 AM I wrote:
> 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%20fixVe
> rsion%20%3D%20%222.2.2%22%20AND%20status%20%3D%20Resolved%20ORDER%20BY%20pri
> ority%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.
- --
- -------------------------------
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)
iEYEARECAAYFAlFKHsgACgkQV/LQcNdtPQOfVQCcCOvMJw86jA5KTSSsViSsWgQN
E8gAn1znecJPgaDOwazU8wIhUV5oRvgu
=Vvpp
-----END PGP SIGNATURE-----
Re: [VOTE] release 2.2.2 (RC1) - note the *2* in the middle
Posted by Andy Kurth <ar...@ncsu.edu>.
+1
-Andy
On 3/20/2013 11:18 AM, Josh Thompson wrote:
> -----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-----
>
Re: [VOTE] release 2.2.2 (RC1) - note the *2* in the middle
Posted by Larry Burton <la...@runningcedar.com>.
+1
Josh Thompson wrote:
> -----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-----
>
Re: [VOTE] release 2.2.2 (RC1) - note the *2* in the middle
Posted by Henry Schaffer <he...@ncsu.edu>.
+1
--henry
On Wed, Mar 20, 2013 at 11:18 AM, Josh Thompson <jo...@ncsu.edu> wrote:
> -----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-----
>
Re: [VOTE] release 2.2.2 (RC1) - note the *2* in the middle
Posted by Young h Oh <oh...@us.ibm.com>.
+1
Young Hyun Oh
From: Josh Thompson <jo...@ncsu.edu>
To: dev@vcl.apache.org, user@vcl.apache.org,
Date: 03/20/2013 11:20 AM
Subject: [VOTE] release 2.2.2 (RC1) - note the *2* in the middle
-----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-----
Re: [VOTE] release 2.2.2 (RC1) - note the *2* in the middle
Posted by Aaron Peeler <fa...@ncsu.edu>.
+1
On Wed, Mar 20, 2013 at 11:18 AM, Josh Thompson <jo...@ncsu.edu> wrote:
> -----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-----
>
--
Aaron Peeler
Program Manager
Virtual Computing Lab
NC State University
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.
Re: [VOTE] release 2.2.2 (RC1) - note the *2* in the middle
Posted by Young h Oh <oh...@us.ibm.com>.
+1
Young Hyun Oh
From: Josh Thompson <jo...@ncsu.edu>
To: dev@vcl.apache.org, user@vcl.apache.org,
Date: 03/20/2013 11:20 AM
Subject: [VOTE] release 2.2.2 (RC1) - note the *2* in the middle
-----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-----
Re: [VOTE] release 2.2.2 (RC1) - note the *2* in the middle
Posted by Larry Burton <la...@runningcedar.com>.
+1
Josh Thompson wrote:
> -----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-----
>