Re: [VOTE] release VCL 2.1
+1 -Andy Josh Thompson wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 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.1-RC2: http://svn.apache.org/repos/asf/incubator/vcl/tags/release-2.1-RC2/ The artifact is an export from that tag. 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.1-RC2-incubating/ The list of resolved JIRA issues associated with this release can be found on the VCL 2.1 release page (this has been regenerated for RC2): http://cwiki.apache.org/VCL/vcl-21-unreleased.html#VCL2.1%2528unreleased%2529-ChangeLog Installation instructions are on the Confluence site and in the INSTALLATION file included in the artifact. Aaron, Andy, and I have completed a test install of all parts and were able to successfully create and capture a base image (we did not repeat this for RC2 because there were only a few very minor bugfixes). The directory created by extracting the RC2 artifact is apache-VCL-2.1-RC2-incubating. Licensing information about perl and its required modules, php and its required modules, and mysql has been restated that they are system requirements according to the information under System Requirements on http://www.apache.org/legal/3party.html. It's also worth noting that the roadmap has been slightly updated. Please vote by the end of the day on Tuesday, Nov 17th 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.1 [ ] 0 dunno [ ] -1 no, don't release VCL 2.1 (provide reasons if this is your vote) Josh - -- - --- Josh Thompson Systems Programmer Advanced Computing | VCL Developer North Carolina State University josh_thomp...@ncsu.edu 919-515-5323 my GPG/PGP key can be found at pgp.mit.edu -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFK/IMBV/LQcNdtPQMRAps5AJ9EGLEgeRNcksx3Ujv5NrGGrv8eEwCfRZs8 SRm+5RkM+YFse8wY8UruVao= =Sdi4 -END PGP SIGNATURE-
RE: [VOTE] release VCL 2.1
+1 -- Tony Miller Technology Consultant Academic Technologies mill...@ecu.edu -Original Message- From: Josh Thompson [mailto:josh_thomp...@ncsu.edu] Sent: Thursday, November 12, 2009 4:50 PM To: vcl-dev@incubator.apache.org Cc: Matt Hogstrom; Kevan Miller; Alan D. Cabrera Subject: [VOTE] release VCL 2.1 -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 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.1-RC2: http://svn.apache.org/repos/asf/incubator/vcl/tags/release-2.1-RC2/ The artifact is an export from that tag. 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.1-RC2-incubating/ The list of resolved JIRA issues associated with this release can be found on the VCL 2.1 release page (this has been regenerated for RC2): http://cwiki.apache.org/VCL/vcl-21-unreleased.html#VCL2.1%2528unreleased%2529-ChangeLog Installation instructions are on the Confluence site and in the INSTALLATION file included in the artifact. Aaron, Andy, and I have completed a test install of all parts and were able to successfully create and capture a base image (we did not repeat this for RC2 because there were only a few very minor bugfixes). The directory created by extracting the RC2 artifact is apache-VCL-2.1-RC2-incubating. Licensing information about perl and its required modules, php and its required modules, and mysql has been restated that they are system requirements according to the information under System Requirements on http://www.apache.org/legal/3party.html. It's also worth noting that the roadmap has been slightly updated. Please vote by the end of the day on Tuesday, Nov 17th to publish this release (this allows for 3 business days to vote). Please note that anyone in the VCL community is allowed to vote. [X] +1 yes, release VCL 2.1 [ ] 0 dunno [ ] -1 no, don't release VCL 2.1 (provide reasons if this is your vote) Josh - -- - --- Josh Thompson Systems Programmer Advanced Computing | VCL Developer North Carolina State University josh_thomp...@ncsu.edu 919-515-5323 my GPG/PGP key can be found at pgp.mit.edu -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFK/IMBV/LQcNdtPQMRAps5AJ9EGLEgeRNcksx3Ujv5NrGGrv8eEwCfRZs8 SRm+5RkM+YFse8wY8UruVao= =Sdi4 -END PGP SIGNATURE-
Re: [VOTE] release VCL 2.1 - RC2
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 [X] +1 yes, release VCL 2.1 [ ] 0 dunno [ ] -1 no, don't release VCL 2.1 (provide reasons if this is your vote) Josh - -- - --- Josh Thompson Systems Programmer Advanced Computing | VCL Developer North Carolina State University josh_thomp...@ncsu.edu 919-515-5323 my GPG/PGP key can be found at pgp.mit.edu -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFLAWszV/LQcNdtPQMRAhKMAJ4+elWQHhP88l4tbRy3YTBx7sVY7ACeK8nL u75t3s+/CDyDmWamt7LcLQo= =mVXW -END PGP SIGNATURE-
Re: [VOTE] release VCL 2.1
+1 Josh Thompson wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 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.1-RC2: http://svn.apache.org/repos/asf/incubator/vcl/tags/release-2.1-RC2/ The artifact is an export from that tag. 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.1-RC2-incubating/ The list of resolved JIRA issues associated with this release can be found on the VCL 2.1 release page (this has been regenerated for RC2): http://cwiki.apache.org/VCL/vcl-21-unreleased.html#VCL2.1%2528unreleased%2529-ChangeLog Installation instructions are on the Confluence site and in the INSTALLATION file included in the artifact. Aaron, Andy, and I have completed a test install of all parts and were able to successfully create and capture a base image (we did not repeat this for RC2 because there were only a few very minor bugfixes). The directory created by extracting the RC2 artifact is apache-VCL-2.1-RC2-incubating. Licensing information about perl and its required modules, php and its required modules, and mysql has been restated that they are system requirements according to the information under System Requirements on http://www.apache.org/legal/3party.html. It's also worth noting that the roadmap has been slightly updated. Please vote by the end of the day on Tuesday, Nov 17th 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.1 [ ] 0 dunno [ ] -1 no, don't release VCL 2.1 (provide reasons if this is your vote) Josh - -- - --- Josh Thompson Systems Programmer Advanced Computing | VCL Developer North Carolina State University josh_thomp...@ncsu.edu 919-515-5323 my GPG/PGP key can be found at pgp.mit.edu -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFK/IMBV/LQcNdtPQMRAps5AJ9EGLEgeRNcksx3Ujv5NrGGrv8eEwCfRZs8 SRm+5RkM+YFse8wY8UruVao= =Sdi4 -END PGP SIGNATURE- -- Mike Waldron Systems Specialist ITS Research Computing University of North Carolina at Chapel Hill CB #3420, ITS Manning, Rm 2509 Office: 919-962-9778
Re: [VOTE] release VCL 2.1 - RC2
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I forgot to add RC2 to the subject in my first message. Josh On Thu November 12 2009 4:49:51 pm Josh Thompson wrote: 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.1-RC2: http://svn.apache.org/repos/asf/incubator/vcl/tags/release-2.1-RC2/ The artifact is an export from that tag. 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.1-RC2-incubating/ The list of resolved JIRA issues associated with this release can be found on the VCL 2.1 release page (this has been regenerated for RC2): http://cwiki.apache.org/VCL/vcl-21-unreleased.html#VCL2.1%2528unreleased%25 29-ChangeLog Installation instructions are on the Confluence site and in the INSTALLATION file included in the artifact. Aaron, Andy, and I have completed a test install of all parts and were able to successfully create and capture a base image (we did not repeat this for RC2 because there were only a few very minor bugfixes). The directory created by extracting the RC2 artifact is apache-VCL-2.1-RC2-incubating. Licensing information about perl and its required modules, php and its required modules, and mysql has been restated that they are system requirements according to the information under System Requirements on http://www.apache.org/legal/3party.html. It's also worth noting that the roadmap has been slightly updated. Please vote by the end of the day on Tuesday, Nov 17th 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.1 [ ] 0 dunno [ ] -1 no, don't release VCL 2.1 (provide reasons if this is your vote) Josh - -- - --- Josh Thompson Systems Programmer Virtual Computing Lab (VCL) North Carolina State University josh_thomp...@ncsu.edu 919-515-5323 my GPG/PGP key can be found at www.keyserver.net -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.11 (GNU/Linux) iD8DBQFK/KTFV/LQcNdtPQMRAkyXAJ41ayT97g8h9W8L7JnTUxovQiQQCwCggCFw VG7CQj8PRKMezDGhitCaCJE= =PjNC -END PGP SIGNATURE-
Re: [VOTE] release VCL 2.1
On Oct 23, 2009, at 10:36 PM, Josh Thompson wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Fri October 23 2009 4:45:26 pm Kevan Miller wrote: On Oct 21, 2009, at 1:27 PM, Josh Thompson wrote: (Question to mentors: Do I need to vote in a successive email in this thread, or is this post an implicit vote?) You should either include an explicit +1 in the initial vote email, or reply in another email. Either is acceptable. I kind of prefer a separate email, but that's just me... Okay - since I didn't include and explicit +1 in the initial message, I'll do it here. +1 Most votes will include a formal statement on what the vote is about. E.g.: [ ] +1 yes, release VCL 2.1 [ ] 0 dunno [ ] -1 no, don't release VCL 2.1 (provide reasons). Now that you mention it, I remember seeing that in some places. Somehow, I came up with an example email calling for a vote that I linked to off of this page: http://cwiki.apache.org/confluence/display/VCL/VCL+Release+Procedures direct link to email: http://mail-archives.apache.org/mod_mbox/stdcxx-dev/200601.mbox/%3c43c1c0a0.7040...@roguewave.com%3e That email doesn't include what you mentioned. I'll revise the release docs to explain that part should be in there and maybe find a better example email. This is the strangest Apache release that I've ever seen... Taking some getting used to... I have some questions/comments. Haven't decided on my vote, yet. Since this is the only Apache release those of us from NCSU have ever seen, can you explain further why you say it is so strange? I thought the release procedures page followed the suggested guidelines pretty well. I'm assuming the items listed below aren't explaining that but are points you think need addressing before finalizing a release. It's strange to me, because I typically assume there is a binary build, in addition to the source. Installation seems pretty involved. I'm just going to be *reading* the installation steps, not actually following them... * web/.ht-inc/conf.php contains references to Shibboleth and UNC. I assume that's holdover from VCL's origins. I left it in there as an example of how Shibboleth authentication would be added in. It is commented out, but I can completely remove it if you think it is confusing. It's fine, I think... * Instructions on installation, prereqs, etc should be clear that a user must determine the licensing of the technologies that you are requiring/referring to/downloading. It's not clear to me if that information is being conveyed. Clearly, you require GPL, LGPL, and microsoft proprietary artifacts. Wondering how much of this needs to flow through legal-discuss... Prolly Alan and Matt have thought about this already. The web frontend only requires dojo to be installed. It is Apache Licensed. The licensing for JPGraph is explained in the INSTALLATION file as well as the fact that it is not needed. There are several options on how you use VCL, and therefore what external software is needed for use by the backend. I'll defer to Aaron and Andy to answer this point further since the backend is not my area of focus. * managementnode/bin/install_perl_libs.pl will download install libraries, IIUC. What are the licenses of these artifacts? Users need to be made aware of what you are doing for them... So, my concern is that we're clear about the licensing implications of VCL. If VCL automatically downloads some set of libraries, then users need to be made aware of the licensing implications... --kevan
Re: [VOTE] release VCL 2.1
I gathered the license information for the Perl modules downloaded and installed by install_perl_libs.pl and added this information to README. Two of the modules use LGPL. The others use the Artistic License or GPL. It would be great if someone could go through them and double check. There was one module (Digest-HMAC) which I couldn't find the license for. The Digest-HMAC module was a dependency for the Authen-SASL 2.12 module. The Digest-HMAC module no longer appears to be a dependency for Authen-SASL 2.13. I updated the Authen-SASL URL to fetch version 2.13 and removed Digest-HMAC from install_perl_libs.pl and README. I added code to install_perl_libs.pl which requires the user to enter 'YES' the script will install and download the modules. The following is displayed: = *** NOTICE *** This script will download and install Perl modules distributed under the following licenses: - The Artistic License - GNU General Public License (GPL) - GNU Library or Lesser General Public License (LGPL) See the README file for more information. = Type YES to proceed, type NO to abort: Regarding the Microsoft artifacts, the instructions direct the person installing the management node to the URL of the page where the supplemental utilities can be obtained. These are not direct download links. Can the responsibility to read the license terms provided by the 3rd party be left to the person downloading the files? Thanks, Andy Andy Kurth wrote: I will look up the licenses of the modules the install_perl_libs.pl script downloads/installs and include a disclaimer when the script is executed. I will add the license information to the list of prerequisites in README. Will this be sufficient? -Andy Kevan Miller wrote: On Oct 23, 2009, at 10:36 PM, Josh Thompson wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Fri October 23 2009 4:45:26 pm Kevan Miller wrote: On Oct 21, 2009, at 1:27 PM, Josh Thompson wrote: (Question to mentors: Do I need to vote in a successive email in this thread, or is this post an implicit vote?) You should either include an explicit +1 in the initial vote email, or reply in another email. Either is acceptable. I kind of prefer a separate email, but that's just me... Okay - since I didn't include and explicit +1 in the initial message, I'll do it here. +1 Most votes will include a formal statement on what the vote is about. E.g.: [ ] +1 yes, release VCL 2.1 [ ] 0 dunno [ ] -1 no, don't release VCL 2.1 (provide reasons). Now that you mention it, I remember seeing that in some places. Somehow, I came up with an example email calling for a vote that I linked to off of this page: http://cwiki.apache.org/confluence/display/VCL/VCL+Release+Procedures direct link to email: http://mail-archives.apache.org/mod_mbox/stdcxx-dev/200601.mbox/%3c43c1c0a0.7040...@roguewave.com%3e That email doesn't include what you mentioned. I'll revise the release docs to explain that part should be in there and maybe find a better example email. This is the strangest Apache release that I've ever seen... Taking some getting used to... I have some questions/comments. Haven't decided on my vote, yet. Since this is the only Apache release those of us from NCSU have ever seen, can you explain further why you say it is so strange? I thought the release procedures page followed the suggested guidelines pretty well. I'm assuming the items listed below aren't explaining that but are points you think need addressing before finalizing a release. It's strange to me, because I typically assume there is a binary build, in addition to the source. Installation seems pretty involved. I'm just going to be *reading* the installation steps, not actually following them... * web/.ht-inc/conf.php contains references to Shibboleth and UNC. I assume that's holdover from VCL's origins. I left it in there as an example of how Shibboleth authentication would be added in. It is commented out, but I can completely remove it if you think it is confusing. It's fine, I think... * Instructions on installation, prereqs, etc should be clear that a user must determine the licensing of the technologies that you are requiring/referring to/downloading. It's not clear to me if that information is being conveyed. Clearly, you require GPL, LGPL, and microsoft proprietary artifacts. Wondering how much of this needs to flow through legal-discuss... Prolly Alan and Matt have thought about this already. The web frontend only requires dojo to be installed. It is Apache Licensed. The licensing for JPGraph is explained in the INSTALLATION file as well as the fact that it is not needed. There are several options on how you use VCL, and therefore what external software is needed for use by the backend. I'll defer to Aaron and
Re: [VOTE] release VCL 2.1
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Fri October 23 2009 4:45:26 pm Kevan Miller wrote: On Oct 21, 2009, at 1:27 PM, Josh Thompson wrote: (Question to mentors: Do I need to vote in a successive email in this thread, or is this post an implicit vote?) You should either include an explicit +1 in the initial vote email, or reply in another email. Either is acceptable. I kind of prefer a separate email, but that's just me... Okay - since I didn't include and explicit +1 in the initial message, I'll do it here. +1 Most votes will include a formal statement on what the vote is about. E.g.: [ ] +1 yes, release VCL 2.1 [ ] 0 dunno [ ] -1 no, don't release VCL 2.1 (provide reasons). Now that you mention it, I remember seeing that in some places. Somehow, I came up with an example email calling for a vote that I linked to off of this page: http://cwiki.apache.org/confluence/display/VCL/VCL+Release+Procedures direct link to email: http://mail-archives.apache.org/mod_mbox/stdcxx-dev/200601.mbox/%3c43c1c0a0.7040...@roguewave.com%3e That email doesn't include what you mentioned. I'll revise the release docs to explain that part should be in there and maybe find a better example email. This is the strangest Apache release that I've ever seen... Taking some getting used to... I have some questions/comments. Haven't decided on my vote, yet. Since this is the only Apache release those of us from NCSU have ever seen, can you explain further why you say it is so strange? I thought the release procedures page followed the suggested guidelines pretty well. I'm assuming the items listed below aren't explaining that but are points you think need addressing before finalizing a release. * web/.ht-inc/conf.php contains references to Shibboleth and UNC. I assume that's holdover from VCL's origins. I left it in there as an example of how Shibboleth authentication would be added in. It is commented out, but I can completely remove it if you think it is confusing. * Instructions on installation, prereqs, etc should be clear that a user must determine the licensing of the technologies that you are requiring/referring to/downloading. It's not clear to me if that information is being conveyed. Clearly, you require GPL, LGPL, and microsoft proprietary artifacts. Wondering how much of this needs to flow through legal-discuss... Prolly Alan and Matt have thought about this already. The web frontend only requires dojo to be installed. It is Apache Licensed. The licensing for JPGraph is explained in the INSTALLATION file as well as the fact that it is not needed. There are several options on how you use VCL, and therefore what external software is needed for use by the backend. I'll defer to Aaron and Andy to answer this point further since the backend is not my area of focus. * managementnode/bin/install_perl_libs.pl will download install libraries, IIUC. What are the licenses of these artifacts? Users need to be made aware of what you are doing for them... --kevan Thanks for your comments. We want this to be as successful and correctly released as possible. Josh - -- - --- Josh Thompson Systems Programmer Virtual Computing Lab (VCL) North Carolina State University josh_thomp...@ncsu.edu 919-515-5323 my GPG/PGP key can be found at www.keyserver.net -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.11 (GNU/Linux) iD8DBQFK4mhDV/LQcNdtPQMRAhOKAJ9YIi3FqH5djL0/xbLbqGqhax1v6ACeNcMO ff9+YnGGvn98/wITV49jS7M= =T1db -END PGP SIGNATURE-
Re: [VOTE] release VCL 2.1
I don't have time to double check this release until this weekend. Normally votes are 72 hours. I request that we don't count the votes until Monday, if that's ok. Regards, Alan On Oct 21, 2009, at 10:27 AM, Josh Thompson wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 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.1-RC1: http://svn.apache.org/repos/asf/incubator/vcl/tags/release-2.1-RC1/ The artifact is an export from that tag. 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.1-RC1-incubating/ The list of resolved JIRA issues associated with this release can be found on the VCL 2.1 release page: http://cwiki.apache.org/VCL/vcl-21-unreleased.html#VCL2.1%2528unreleased%2529-ChangeLog Installation instructions are on the Confluence site and in the INSTALLATION file included in the artifact. Aaron, Andy, and I have completed a test install of all parts and were able to successfully create and capture a base image. Please vote to publish this release. (Question to mentors: Do I need to vote in a successive email in this thread, or is this post an implicit vote?) - -- - --- Josh Thompson Systems Programmer Advanced Computing | VCL Developer North Carolina State University josh_thomp...@ncsu.edu 919-515-5323 my GPG/PGP key can be found at pgp.mit.edu -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFK30SGV/LQcNdtPQMRAhk8AJsGL4m0J1v0DC7U9Yyc31TIRjKXFACdE0bM 827++1u0XH9c2GqKP/pAE80= =QrMV -END PGP SIGNATURE-
Re: [VOTE] release VCL 2.1
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 That's fine. Several of us were at a conference all day today and will be tomorrow as well anyway. Josh On Thu October 22 2009 12:57:29 pm Alan D. Cabrera wrote: I don't have time to double check this release until this weekend. Normally votes are 72 hours. I request that we don't count the votes until Monday, if that's ok. Regards, Alan On Oct 21, 2009, at 10:27 AM, Josh Thompson wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 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.1-RC1: http://svn.apache.org/repos/asf/incubator/vcl/tags/release-2.1-RC1/ The artifact is an export from that tag. 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.1-RC1-incubating/ The list of resolved JIRA issues associated with this release can be found on the VCL 2.1 release page: http://cwiki.apache.org/VCL/vcl-21-unreleased.html#VCL2.1%2528unreleased% 2529-ChangeLog Installation instructions are on the Confluence site and in the INSTALLATION file included in the artifact. Aaron, Andy, and I have completed a test install of all parts and were able to successfully create and capture a base image. Please vote to publish this release. (Question to mentors: Do I need to vote in a successive email in this thread, or is this post an implicit vote?) - -- - --- Josh Thompson Systems Programmer Advanced Computing | VCL Developer North Carolina State University josh_thomp...@ncsu.edu 919-515-5323 my GPG/PGP key can be found at pgp.mit.edu -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFK30SGV/LQcNdtPQMRAhk8AJsGL4m0J1v0DC7U9Yyc31TIRjKXFACdE0bM 827++1u0XH9c2GqKP/pAE80= =QrMV -END PGP SIGNATURE- - -- - --- Josh Thompson Systems Programmer Virtual Computing Lab (VCL) North Carolina State University josh_thomp...@ncsu.edu 919-515-5323 my GPG/PGP key can be found at www.keyserver.net -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.11 (GNU/Linux) iD8DBQFK4QMTV/LQcNdtPQMRAuNiAJwJ0WsP7IDgB8X5YneNoGcqmIz5ygCfVUe4 y6/cQYVx4fRbCJeaC6BoYBg= =eFx1 -END PGP SIGNATURE-
Re: [VOTE] release VCL 2.1
Since I was part of packaging and went through due-diligence with a 3rd party. I feel this is ready. +1 Aaron --On October 21, 2009 1:27:34 PM -0400 Josh Thompson josh_thomp...@ncsu.edu wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 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.1-RC1: http://svn.apache.org/repos/asf/incubator/vcl/tags/release-2.1-RC1/ The artifact is an export from that tag. 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.1-RC1-incubating/ The list of resolved JIRA issues associated with this release can be found on the VCL 2.1 release page: http://cwiki.apache.org/VCL/vcl-21-unreleased.html#VCL2.1%2528unreleased% 2529-ChangeLog Installation instructions are on the Confluence site and in the INSTALLATION file included in the artifact. Aaron, Andy, and I have completed a test install of all parts and were able to successfully create and capture a base image. Please vote to publish this release. (Question to mentors: Do I need to vote in a successive email in this thread, or is this post an implicit vote?) - -- - --- Josh Thompson Systems Programmer Advanced Computing | VCL Developer North Carolina State University josh_thomp...@ncsu.edu 919-515-5323 my GPG/PGP key can be found at pgp.mit.edu -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFK30SGV/LQcNdtPQMRAhk8AJsGL4m0J1v0DC7U9Yyc31TIRjKXFACdE0bM 827++1u0XH9c2GqKP/pAE80= =QrMV -END PGP SIGNATURE- Aaron Peeler OIT Advanced Computing College of Engineering-NCSU 919.513.4571 http://vcl.ncsu.edu
