Re: [VOTE] release VCL 2.3 (based on RC3)
+1 -- Mark Gardner --
Re: [VOTE] release VCL 2.3 (based on RC3)
+1 --henry schaffer
Re: [VOTE] release VCL 2.3 (based on RC3)
Here's my +1 source, license/notice, signature/checksum, all look good to me. --kevan On Jun 7, 2012, at 2:29 PM, Josh Thompson wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > And now with the correct subject... (RC2 -> RC3) > > I was finally able to (successfully) test the fixes for the xCAT2 module with > the latest version of xCAT as well as the issue of emailing > nob...@example.com. > > So, here we go again with RC3. (I'm starting to feel like the boy who cried > 'wolf'...) > > I created a release artifact based off of trunk. I copied trunk to a tag > under the tags area of the repo that is named release-2.3-RC3: > > http://svn.apache.org/repos/asf/incubator/vcl/tags/release-2.3-RC3/ > > The artifact is an export from that tag with the addition of Dojo Toolkit > version 1.6.1 with a custom VCL profile bundled in the web code. The > artifact, MD5 and SHA1 sums, and my GPG signature of it are available from my > space on people.a.o: > > http://people.apache.org/~jfthomps/apache-VCL-2.3-RC3-incubating/ > > The list of resolved JIRA issues associated with this release can be found > under Change Log on the VCL 2.3 release page: > > https://cwiki.apache.org/VCL/vcl-23.html#VCL2.3-ChangeLog > > Installation instructions are on the Confluence site and in the INSTALLATION > file included in the artifact. > > The only testing I did with RC3 was related to xCAT and watching what emails > went out. Nothing else changed from RC2. > > The directory created by extracting the RC3 artifact is > "apache-VCL-2.3-RC3-incubating" (after extracting, you may want to rename it > to "apache-VCL-2.3-incubating" so you can copy and paste all of the commands > in the installation guide). Licensing information about perl and its required > modules, php and its required modules, and mysql are stated as "system > requirements" according to the information under "System Requirements" on > http://www.apache.org/legal/3party.html. > > Please vote by the end of the day on Tuesday, June 12th to publish this > release (this allows for 3 business days to vote). Please note that anyone in > the VCL community is allowed to vote. > > +1 yes, release VCL 2.3 > 0 dunno > - -1 no, don't release VCL 2.3 (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.17 (GNU/Linux) > > iEYEARECAAYFAk/Q8yUACgkQV/LQcNdtPQMpBgCePWKUiTadPAmiuPJnejDXeFiE > 1s0Amwe8Nx3UUaosnrVzYy7LuIgYVOpz > =Yg1q > -END PGP SIGNATURE- >
Re: [VOTE] release VCL 2.3 (based on RC3)
+1 On Thu, Jun 7, 2012 at 2:29 PM, Josh Thompson wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > And now with the correct subject... (RC2 -> RC3) > > I was finally able to (successfully) test the fixes for the xCAT2 module with > the latest version of xCAT as well as the issue of emailing > nob...@example.com. > > So, here we go again with RC3. (I'm starting to feel like the boy who cried > 'wolf'...) > > I created a release artifact based off of trunk. I copied trunk to a tag > under the tags area of the repo that is named release-2.3-RC3: > > http://svn.apache.org/repos/asf/incubator/vcl/tags/release-2.3-RC3/ > > The artifact is an export from that tag with the addition of Dojo Toolkit > version 1.6.1 with a custom VCL profile bundled in the web code. The > artifact, MD5 and SHA1 sums, and my GPG signature of it are available from my > space on people.a.o: > > http://people.apache.org/~jfthomps/apache-VCL-2.3-RC3-incubating/ > > The list of resolved JIRA issues associated with this release can be found > under Change Log on the VCL 2.3 release page: > > https://cwiki.apache.org/VCL/vcl-23.html#VCL2.3-ChangeLog > > Installation instructions are on the Confluence site and in the INSTALLATION > file included in the artifact. > > The only testing I did with RC3 was related to xCAT and watching what emails > went out. Nothing else changed from RC2. > > The directory created by extracting the RC3 artifact is > "apache-VCL-2.3-RC3-incubating" (after extracting, you may want to rename it > to "apache-VCL-2.3-incubating" so you can copy and paste all of the commands > in the installation guide). Licensing information about perl and its required > modules, php and its required modules, and mysql are stated as "system > requirements" according to the information under "System Requirements" on > http://www.apache.org/legal/3party.html. > > Please vote by the end of the day on Tuesday, June 12th to publish this > release (this allows for 3 business days to vote). Please note that anyone in > the VCL community is allowed to vote. > > +1 yes, release VCL 2.3 > 0 dunno > - -1 no, don't release VCL 2.3 (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.17 (GNU/Linux) > > iEYEARECAAYFAk/Q8yUACgkQV/LQcNdtPQMpBgCePWKUiTadPAmiuPJnejDXeFiE > 1s0Amwe8Nx3UUaosnrVzYy7LuIgYVOpz > =Yg1q > -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 VCL 2.3 (based on RC3)
+1 On Thursday, June 07, 2012 2:29:57 PM Josh Thompson wrote: > > And now with the correct subject... (RC2 -> RC3) > > I was finally able to (successfully) test the fixes for the xCAT2 module > with the latest version of xCAT as well as the issue of emailing > nob...@example.com. > > So, here we go again with RC3. (I'm starting to feel like the boy who cried > 'wolf'...) > > I created a release artifact based off of trunk. I copied trunk to a tag > under the tags area of the repo that is named release-2.3-RC3: > > http://svn.apache.org/repos/asf/incubator/vcl/tags/release-2.3-RC3/ > > The artifact is an export from that tag with the addition of Dojo Toolkit > version 1.6.1 with a custom VCL profile bundled in the web code. The > artifact, MD5 and SHA1 sums, and my GPG signature of it are available from > my space on people.a.o: > > http://people.apache.org/~jfthomps/apache-VCL-2.3-RC3-incubating/ > > The list of resolved JIRA issues associated with this release can be found > under Change Log on the VCL 2.3 release page: > > https://cwiki.apache.org/VCL/vcl-23.html#VCL2.3-ChangeLog > > Installation instructions are on the Confluence site and in the > INSTALLATION file included in the artifact. > > The only testing I did with RC3 was related to xCAT and watching what emails > went out. Nothing else changed from RC2. > > The directory created by extracting the RC3 artifact is > "apache-VCL-2.3-RC3-incubating" (after extracting, you may want to rename > it to "apache-VCL-2.3-incubating" so you can copy and paste all of the > commands in the installation guide). Licensing information about perl and > its required modules, php and its required modules, and mysql are stated as > "system requirements" according to the information under "System > Requirements" on http://www.apache.org/legal/3party.html. > > Please vote by the end of the day on Tuesday, June 12th to publish this > release (this allows for 3 business days to vote). Please note that anyone > in the VCL community is allowed to vote. > > +1 yes, release VCL 2.3 > 0 dunno > -1 no, don't release VCL 2.3 (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 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 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. signature.asc Description: This is a digitally signed message part.
RE: [VOTE] release VCL 2.3 (based on RC2)
+1 Young Hyun Oh IBM Tivoli CTO Technology and Architecture From: "Waldron, Michael H" To: "vcl-dev@incubator.apache.org" , Date: 06/04/2012 02:17 PM Subject: RE: [VOTE] release VCL 2.3 (based on RC2) +1 Mike Waldron Systems Specialist ITS Research Computing University of North Carolina at Chapel Hill CB #3420, ITS Manning, Rm 2509 919-962-9778 From: Josh Thompson [josh_thomp...@ncsu.edu] Sent: Monday, June 04, 2012 2:20 PM To: vcl-dev@incubator.apache.org Subject: [VOTE] release VCL 2.3 (based on RC2) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I found a few more minor issues with the web code that I committed and a bug with image capture using VMware Free Server that Aaron fixed. I created a release artifact based off of trunk. I copied trunk to a tag under the tags area of the repo that is named release-2.3-RC2: http://svn.apache.org/repos/asf/incubator/vcl/tags/release-2.3-RC2/ The artifact is an export from that tag with the addition of Dojo Toolkit version 1.6.1 with a custom VCL profile bundled in the web code. The artifact, MD5 and SHA1 sums, and my GPG signature of it are available from my space on people.a.o: http://people.apache.org/~jfthomps/apache-VCL-2.3-RC2-incubating/ The list of resolved JIRA issues associated with this release can be found under Change Log on the VCL 2.3 release page: https://cwiki.apache.org/VCL/vcl-23.html#VCL2.3-ChangeLog Installation instructions are on the Confluence site and in the INSTALLATION file included in the artifact. I was able to successfully do a test install, including image deploying and capture. The directory created by extracting the RC2 artifact is "apache-VCL-2.3-RC2-incubating" (after extracting, you may want to rename it to "apache-VCL-2.3-incubating" so you can copy and paste all of the commands in the installation guide). Licensing information about perl and its required modules, php and its required modules, and mysql are stated as "system requirements" according to the information under "System Requirements" on http://www.apache.org/legal/3party.html. Please vote by the end of the day on Thursday, June 7th to publish this release (this allows for 3 business days to vote). Please note that anyone in the VCL community is allowed to vote. +1 yes, release VCL 2.3 0 dunno - -1 no, don't release VCL 2.3 (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.17 (GNU/Linux) iEYEARECAAYFAk/M/GUACgkQV/LQcNdtPQMliACaA5vcEuVwmUcfs1X0KmiliRRq lpwAniLra7T3K7Vahg2L0HmrXApjdaJY =SrdM -END PGP SIGNATURE-
RE: [VOTE] release VCL 2.3 (based on RC2)
+1 Mike Waldron Systems Specialist ITS Research Computing University of North Carolina at Chapel Hill CB #3420, ITS Manning, Rm 2509 919-962-9778 From: Josh Thompson [josh_thomp...@ncsu.edu] Sent: Monday, June 04, 2012 2:20 PM To: vcl-dev@incubator.apache.org Subject: [VOTE] release VCL 2.3 (based on RC2) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I found a few more minor issues with the web code that I committed and a bug with image capture using VMware Free Server that Aaron fixed. I created a release artifact based off of trunk. I copied trunk to a tag under the tags area of the repo that is named release-2.3-RC2: http://svn.apache.org/repos/asf/incubator/vcl/tags/release-2.3-RC2/ The artifact is an export from that tag with the addition of Dojo Toolkit version 1.6.1 with a custom VCL profile bundled in the web code. The artifact, MD5 and SHA1 sums, and my GPG signature of it are available from my space on people.a.o: http://people.apache.org/~jfthomps/apache-VCL-2.3-RC2-incubating/ The list of resolved JIRA issues associated with this release can be found under Change Log on the VCL 2.3 release page: https://cwiki.apache.org/VCL/vcl-23.html#VCL2.3-ChangeLog Installation instructions are on the Confluence site and in the INSTALLATION file included in the artifact. I was able to successfully do a test install, including image deploying and capture. The directory created by extracting the RC2 artifact is "apache-VCL-2.3-RC2-incubating" (after extracting, you may want to rename it to "apache-VCL-2.3-incubating" so you can copy and paste all of the commands in the installation guide). Licensing information about perl and its required modules, php and its required modules, and mysql are stated as "system requirements" according to the information under "System Requirements" on http://www.apache.org/legal/3party.html. Please vote by the end of the day on Thursday, June 7th to publish this release (this allows for 3 business days to vote). Please note that anyone in the VCL community is allowed to vote. +1 yes, release VCL 2.3 0 dunno - -1 no, don't release VCL 2.3 (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.17 (GNU/Linux) iEYEARECAAYFAk/M/GUACgkQV/LQcNdtPQMliACaA5vcEuVwmUcfs1X0KmiliRRq lpwAniLra7T3K7Vahg2L0HmrXApjdaJY =SrdM -END PGP SIGNATURE-
Re: [VOTE] release VCL 2.3
On May 30, 2012, at 5:41 PM, Aaron Coburn wrote: > -1 > > Sorry to a stick in the mud, guys, since I'd certainly like to see 2.3 > released soon, but I encountered a few issues that I think should be fixed > before cutting the release. Suggest that there should be a discussion of Aaron's issues in a separate thread. Just want to note ASF protocols for release votes. Release votes are majority approval with 3 PMC +1's (http://www.apache.org/foundation/voting.html#ReleaseVotes). Technically, there aren't veto's. However, most release votes are unanimous decisions. And most communities would carefully consider any -1 from a committer/pmc member. --kevan
Re: [VOTE] release VCL 2.3
-1
Sorry to a stick in the mud, guys, since I'd certainly like to see 2.3 released
soon, but I encountered a few issues that I think should be fixed before
cutting the release.
I installed the release candidate using a fresh database, testing against a
vCenter provisioning engine and Shibboleth authentication. I was using a 64-bit
Windows 7 image.
The first issue I encountered was that each time the management node calls
'get_file_contents', the contents of the target file are printed to the log.
This is generally not an issue, but when a slice of the registry is retrieved,
that amounted to ~30,000 lines in my logfile. And that happens each time an
image is reloaded. (Somehow I hadn't noticed this with the code from about two
weeks ago). I can certainly see the usefulness of this during development, but
I don't like the fact that this is the default behavior for a release. For now,
I would suggest modifying line 1789 of OS.pm:
-my ($exit_status, $output) = $self->execute($command);
+my ($exit_status, $output) = $self->execute($command, 0); # do not print
the cmd output to the log
Later, it could be nice to make this somewhat more configurable.
Second, if the system is using Shibboleth it is not possible to handle users
who have not previously logged in (i.e. adding someone to a group). There are
two bugs preventing this from working properly. First, if someone enables
ALLOWADDSHIBUSERS in conf.php but doesn't define a value in $addUserFuncArgs (I
would anticipate this to be what most people using Shib would do, since there
is no documentation about what that array is for), the initGlobals() function
does not properly populate the addUserFuncArgs array. This can be fixed by
adding $addUserFuncArgs to the list of 'global' values on line 68 in utils.php
-- the current code is just modifying a local value, not the global one:
-global $affilValFunc, $addUserFunc, $updateUserFunc;
+global $affilValFunc, $addUserFunc, $updateUserFunc, $addUserFuncArgs;
Once that change is made, though, there is also a SQL query expecting a
'validated' field in the users table. This field, however, does not exist. It
is in neither update-vcl.sql nor in vcl.sql:
vcl.sql, line 1079:
+ `validated` tinyint(1) unsigned NOT NULL default '1',
and update-vcl.sql, lines 827-
+ --
+
+ --
+ -- Table structure for table `user`
+ --
+
+ CALL AddColumnIfNotExists('user', 'validated', "tinyint(1) unsigned NOT NULL
default '1'");
+
Once these two changes are made, however, I am able to add shib users exactly
as the documentation suggests.
Otherwise, everything else looks good.
Aaron
--
Aaron Coburn
Systems Administrator and Programmer
Academic Technology Services, Amherst College
acob...@amherst.edu
On May 30, 2012, at 2:58 PM, Josh Thompson wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Kevan,
Correct - VCL is all in scripted languages; so, there are no binary releases.
I've avoided maintaining dojo in subversion both to keep the repo a little
cleaner and to avoid the problem of ending up with an old copy in there that
never gets updated.
I'll start a separate thread to discuss if others would like dojo in the repo.
Josh
On Wednesday, May 30, 2012 10:57:41 AM Kevan Miller wrote:
Here's my +1
Source, LICENSE/NOTICE, RAT, signature/checksum -- all look good to me.
Seem to recall a discussion on this before, but just to be sure. Apache
releases source code. PMC's vote on source releases. Many ASF projects also
have binary distributions (which a PMC also evaluates and uses in
evaluating the correctness of the release). The binaries are also
convenient for many users. So, you end up with source and binary
distributions of a project.
There is no VCL binary/compilation (that I know of). So, the VCL release is
a *source* release. One thing to note is that we don't maintain dojo in svn
(we could do so).
--kevan
On May 29, 2012, at 4:36 PM, Josh Thompson wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
We've finally reached a point where we do not seem to be finding any more
bugs.
I created a release artifact based off of trunk. I copied trunk to a tag
under the tags area of the repo that is named release-2.3-RC1:
http://svn.apache.org/repos/asf/incubator/vcl/tags/release-2.3-RC1/
The artifact is an export from that tag with the addition of Dojo Toolkit
version 1.6.1 with a custom VCL profile bundled in the web code. The
artifact, MD5 and SHA1 sums, and my GPG signature of it are available from
my space on people.a.o:
http://people.apache.org/~jfthomps/apache-VCL-2.3-RC1-incubating/
The list of resolved JIRA issues associated with this release can be found
under Change Log on the VCL 2.3 release page:
https://cwiki.apache.org/VCL/vcl-23.html#VCL2.3-ChangeLog
Installation instructions are on the Confluence site and in the
INSTALLATION file included in the artifact.
I was ab
Re: [VOTE] release VCL 2.3
+1 -Andy On Tue, May 29, 2012 at 4:36 PM, Josh Thompson wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > We've finally reached a point where we do not seem to be finding any more > bugs. > > I created a release artifact based off of trunk. I copied trunk to a tag > under the tags area of the repo that is named release-2.3-RC1: > > http://svn.apache.org/repos/asf/incubator/vcl/tags/release-2.3-RC1/ > > The artifact is an export from that tag with the addition of Dojo Toolkit > version 1.6.1 with a custom VCL profile bundled in the web code. The > artifact, MD5 and SHA1 sums, and my GPG signature of it are available from my > space on people.a.o: > > http://people.apache.org/~jfthomps/apache-VCL-2.3-RC1-incubating/ > > The list of resolved JIRA issues associated with this release can be found > under Change Log on the VCL 2.3 release page: > > https://cwiki.apache.org/VCL/vcl-23.html#VCL2.3-ChangeLog > > Installation instructions are on the Confluence site and in the INSTALLATION > file included in the artifact. > > I was able to successfully do a test install, including image deploying and > capture. > > The directory created by extracting the RC1 artifact is > "apache-VCL-2.3-RC1-incubating" (after extracting, you may want to rename it > to "apache-VCL-2.3-incubating" so you can copy and paste all of the commands > in the installation guide). Licensing information about perl and its required > modules, php and its required modules, and mysql are stated as "system > requirements" according to the information under "System Requirements" on > http://www.apache.org/legal/3party.html. > > Please vote by the end of the day on Friday, June 1st to publish this > release (this allows for 3 business days to vote). Please note that anyone in > the VCL community is allowed to vote. > > [ ] +1 yes, release VCL 2.3 > [ ] 0 dunno > [ ] -1 no, don't release VCL 2.3 (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.17 (GNU/Linux) > > iEYEARECAAYFAk/FMzYACgkQV/LQcNdtPQNOIwCfVwta+LYh0W+7tj9B39j5Owb0 > LPsAn29HkFQmU3lV2U54VrGsx2C4hZrg > =8DZ2 > -END PGP SIGNATURE- >
Re: [VOTE] release VCL 2.3
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 +1 On Tue, May 29, 2012 at 4:36 PM, Josh Thompson wrote: > We've finally reached a point where we do not seem to be finding any more > bugs. > > I created a release artifact based off of trunk. I copied trunk to a tag > under the tags area of the repo that is named release-2.3-RC1: > > http://svn.apache.org/repos/asf/incubator/vcl/tags/release-2.3-RC1/ > > The artifact is an export from that tag with the addition of Dojo Toolkit > version 1.6.1 with a custom VCL profile bundled in the web code. The > artifact, MD5 and SHA1 sums, and my GPG signature of it are available from > my space on people.a.o: > > http://people.apache.org/~jfthomps/apache-VCL-2.3-RC1-incubating/ > > The list of resolved JIRA issues associated with this release can be found > under Change Log on the VCL 2.3 release page: > > https://cwiki.apache.org/VCL/vcl-23.html#VCL2.3-ChangeLog > > Installation instructions are on the Confluence site and in the INSTALLATION > file included in the artifact. > > I was able to successfully do a test install, including image deploying and > capture. > > The directory created by extracting the RC1 artifact is > "apache-VCL-2.3-RC1-incubating" (after extracting, you may want to rename it > to "apache-VCL-2.3-incubating" so you can copy and paste all of the commands > in the installation guide). Licensing information about perl and its > required modules, php and its required modules, and mysql are stated as > "system requirements" according to the information under "System > Requirements" on > > http://www.apache.org/legal/3party.html. > > Please vote by the end of the day on Friday, June 1st to publish this > release (this allows for 3 business days to vote). Please note that anyone > in the VCL community is allowed to vote. > > [ ] +1 yes, release VCL 2.3 > [ ] 0 dunno > [ ] -1 no, don't release VCL 2.3 (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.17 (GNU/Linux) iEYEARECAAYFAk/GfPQACgkQV/LQcNdtPQOuqwCcCKOJA3pLwvMOF0XkKkX3qnAT 4I4Ani4Snjs4YeRayePcDxi9r3mndtqL =i5KP -END PGP SIGNATURE-
Re: [VOTE] release VCL 2.3
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Kevan, Correct - VCL is all in scripted languages; so, there are no binary releases. I've avoided maintaining dojo in subversion both to keep the repo a little cleaner and to avoid the problem of ending up with an old copy in there that never gets updated. I'll start a separate thread to discuss if others would like dojo in the repo. Josh On Wednesday, May 30, 2012 10:57:41 AM Kevan Miller wrote: > Here's my +1 > > Source, LICENSE/NOTICE, RAT, signature/checksum -- all look good to me. > > Seem to recall a discussion on this before, but just to be sure. Apache > releases source code. PMC's vote on source releases. Many ASF projects also > have binary distributions (which a PMC also evaluates and uses in > evaluating the correctness of the release). The binaries are also > convenient for many users. So, you end up with source and binary > distributions of a project. > > There is no VCL binary/compilation (that I know of). So, the VCL release is > a *source* release. One thing to note is that we don't maintain dojo in svn > (we could do so). > > --kevan > > On May 29, 2012, at 4:36 PM, Josh Thompson wrote: > > -BEGIN PGP SIGNED MESSAGE- > > Hash: SHA1 > > > > We've finally reached a point where we do not seem to be finding any more > > bugs. > > > > I created a release artifact based off of trunk. I copied trunk to a tag > > under the tags area of the repo that is named release-2.3-RC1: > > > > http://svn.apache.org/repos/asf/incubator/vcl/tags/release-2.3-RC1/ > > > > The artifact is an export from that tag with the addition of Dojo Toolkit > > version 1.6.1 with a custom VCL profile bundled in the web code. The > > artifact, MD5 and SHA1 sums, and my GPG signature of it are available from > > my space on people.a.o: > > > > http://people.apache.org/~jfthomps/apache-VCL-2.3-RC1-incubating/ > > > > The list of resolved JIRA issues associated with this release can be found > > under Change Log on the VCL 2.3 release page: > > > > https://cwiki.apache.org/VCL/vcl-23.html#VCL2.3-ChangeLog > > > > Installation instructions are on the Confluence site and in the > > INSTALLATION file included in the artifact. > > > > I was able to successfully do a test install, including image deploying > > and > > capture. > > > > The directory created by extracting the RC1 artifact is > > "apache-VCL-2.3-RC1-incubating" (after extracting, you may want to rename > > it to "apache-VCL-2.3-incubating" so you can copy and paste all of the > > commands in the installation guide). Licensing information about perl > > and its required modules, php and its required modules, and mysql are > > stated as "system requirements" according to the information under > > "System Requirements" on http://www.apache.org/legal/3party.html. > > > > Please vote by the end of the day on Friday, June 1st to publish this > > release (this allows for 3 business days to vote). Please note that > > anyone in the VCL community is allowed to vote. > > > > [ ] +1 yes, release VCL 2.3 > > [ ] 0 dunno > > [ ] -1 no, don't release VCL 2.3 (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.17 (GNU/Linux) > > > > iEYEARECAAYFAk/FMzYACgkQV/LQcNdtPQNOIwCfVwta+LYh0W+7tj9B39j5Owb0 > > LPsAn29HkFQmU3lV2U54VrGsx2C4hZrg > > =8DZ2 > > -END PGP SIGNATURE- - -- - --- Josh Thompson VCL Developer North Carolina State University my GPG/PGP key can be found at pgp.mit.edu All electronic mail messages in connection with State business which are sent to or received by this account are subject to the NC Public Records Law and may be disclosed to third parties. -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.17 (GNU/Linux) iEYEARECAAYFAk/GbdoACgkQV/LQcNdtPQNtiQCfUi3/ZctI9H2i5Q+8jAgJtHAI scQAn3NPQN9tdAzB1T4gXTaxzx3FJTKo =lEHU -END PGP SIGNATURE-
Re: [VOTE] release VCL 2.3
vote +1 Larry Josh Thompson wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 We've finally reached a point where we do not seem to be finding any more bugs. I created a release artifact based off of trunk. I copied trunk to a tag under the tags area of the repo that is named release-2.3-RC1: http://svn.apache.org/repos/asf/incubator/vcl/tags/release-2.3-RC1/ The artifact is an export from that tag with the addition of Dojo Toolkit version 1.6.1 with a custom VCL profile bundled in the web code. The artifact, MD5 and SHA1 sums, and my GPG signature of it are available from my space on people.a.o: http://people.apache.org/~jfthomps/apache-VCL-2.3-RC1-incubating/ The list of resolved JIRA issues associated with this release can be found under Change Log on the VCL 2.3 release page: https://cwiki.apache.org/VCL/vcl-23.html#VCL2.3-ChangeLog Installation instructions are on the Confluence site and in the INSTALLATION file included in the artifact. I was able to successfully do a test install, including image deploying and capture. The directory created by extracting the RC1 artifact is "apache-VCL-2.3-RC1-incubating" (after extracting, you may want to rename it to "apache-VCL-2.3-incubating" so you can copy and paste all of the commands in the installation guide). Licensing information about perl and its required modules, php and its required modules, and mysql are stated as "system requirements" according to the information under "System Requirements" on http://www.apache.org/legal/3party.html. Please vote by the end of the day on Friday, June 1st to publish this release (this allows for 3 business days to vote). Please note that anyone in the VCL community is allowed to vote. [ ] +1 yes, release VCL 2.3 [ ] 0 dunno [ ] -1 no, don't release VCL 2.3 (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.17 (GNU/Linux) iEYEARECAAYFAk/FMzYACgkQV/LQcNdtPQNOIwCfVwta+LYh0W+7tj9B39j5Owb0 LPsAn29HkFQmU3lV2U54VrGsx2C4hZrg =8DZ2 -END PGP SIGNATURE-
Re: [VOTE] release VCL 2.3
+1 Alex CSUEB On Wed, May 30, 2012 at 9:58 AM, Waldron, Michael H wrote: > +1 > > > Mike Waldron > Systems Specialist > ITS Research Computing > University of North Carolina at Chapel Hill > CB #3420, ITS Manning, Rm 2509 > 919-962-9778 > > From: Josh Thompson [josh_thomp...@ncsu.edu] > Sent: Tuesday, May 29, 2012 4:36 PM > To: vcl-dev@incubator.apache.org > Subject: [VOTE] release VCL 2.3 > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > We've finally reached a point where we do not seem to be finding any more > bugs. > > I created a release artifact based off of trunk. I copied trunk to a tag > under the tags area of the repo that is named release-2.3-RC1: > > http://svn.apache.org/repos/asf/incubator/vcl/tags/release-2.3-RC1/ > > The artifact is an export from that tag with the addition of Dojo Toolkit > version 1.6.1 with a custom VCL profile bundled in the web code. The > artifact, MD5 and SHA1 sums, and my GPG signature of it are available from my > space on people.a.o: > > http://people.apache.org/~jfthomps/apache-VCL-2.3-RC1-incubating/ > > The list of resolved JIRA issues associated with this release can be found > under Change Log on the VCL 2.3 release page: > > https://cwiki.apache.org/VCL/vcl-23.html#VCL2.3-ChangeLog > > Installation instructions are on the Confluence site and in the INSTALLATION > file included in the artifact. > > I was able to successfully do a test install, including image deploying and > capture. > > The directory created by extracting the RC1 artifact is > "apache-VCL-2.3-RC1-incubating" (after extracting, you may want to rename it > to "apache-VCL-2.3-incubating" so you can copy and paste all of the commands > in the installation guide). Licensing information about perl and its required > modules, php and its required modules, and mysql are stated as "system > requirements" according to the information under "System Requirements" on > http://www.apache.org/legal/3party.html. > > Please vote by the end of the day on Friday, June 1st to publish this > release (this allows for 3 business days to vote). Please note that anyone in > the VCL community is allowed to vote. > > [ ] +1 yes, release VCL 2.3 > [ ] 0 dunno > [ ] -1 no, don't release VCL 2.3 (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.17 (GNU/Linux) > > iEYEARECAAYFAk/FMzYACgkQV/LQcNdtPQNOIwCfVwta+LYh0W+7tj9B39j5Owb0 > LPsAn29HkFQmU3lV2U54VrGsx2C4hZrg > =8DZ2 > -END PGP SIGNATURE- > -- Thanks, Alex Patterson User Support Services Operating System Analyst California State University, East Bay
RE: [VOTE] release VCL 2.3
+1 Mike Waldron Systems Specialist ITS Research Computing University of North Carolina at Chapel Hill CB #3420, ITS Manning, Rm 2509 919-962-9778 From: Josh Thompson [josh_thomp...@ncsu.edu] Sent: Tuesday, May 29, 2012 4:36 PM To: vcl-dev@incubator.apache.org Subject: [VOTE] release VCL 2.3 -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 We've finally reached a point where we do not seem to be finding any more bugs. I created a release artifact based off of trunk. I copied trunk to a tag under the tags area of the repo that is named release-2.3-RC1: http://svn.apache.org/repos/asf/incubator/vcl/tags/release-2.3-RC1/ The artifact is an export from that tag with the addition of Dojo Toolkit version 1.6.1 with a custom VCL profile bundled in the web code. The artifact, MD5 and SHA1 sums, and my GPG signature of it are available from my space on people.a.o: http://people.apache.org/~jfthomps/apache-VCL-2.3-RC1-incubating/ The list of resolved JIRA issues associated with this release can be found under Change Log on the VCL 2.3 release page: https://cwiki.apache.org/VCL/vcl-23.html#VCL2.3-ChangeLog Installation instructions are on the Confluence site and in the INSTALLATION file included in the artifact. I was able to successfully do a test install, including image deploying and capture. The directory created by extracting the RC1 artifact is "apache-VCL-2.3-RC1-incubating" (after extracting, you may want to rename it to "apache-VCL-2.3-incubating" so you can copy and paste all of the commands in the installation guide). Licensing information about perl and its required modules, php and its required modules, and mysql are stated as "system requirements" according to the information under "System Requirements" on http://www.apache.org/legal/3party.html. Please vote by the end of the day on Friday, June 1st to publish this release (this allows for 3 business days to vote). Please note that anyone in the VCL community is allowed to vote. [ ] +1 yes, release VCL 2.3 [ ] 0 dunno [ ] -1 no, don't release VCL 2.3 (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.17 (GNU/Linux) iEYEARECAAYFAk/FMzYACgkQV/LQcNdtPQNOIwCfVwta+LYh0W+7tj9B39j5Owb0 LPsAn29HkFQmU3lV2U54VrGsx2C4hZrg =8DZ2 -END PGP SIGNATURE-
Re: [VOTE] release VCL 2.3
+1 On Tue, May 29, 2012 at 4:36 PM, Josh Thompson wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > We've finally reached a point where we do not seem to be finding any more > bugs. > > I created a release artifact based off of trunk. I copied trunk to a tag > under the tags area of the repo that is named release-2.3-RC1: > > http://svn.apache.org/repos/asf/incubator/vcl/tags/release-2.3-RC1/ > > The artifact is an export from that tag with the addition of Dojo Toolkit > version 1.6.1 with a custom VCL profile bundled in the web code. The > artifact, MD5 and SHA1 sums, and my GPG signature of it are available from my > space on people.a.o: > > http://people.apache.org/~jfthomps/apache-VCL-2.3-RC1-incubating/ > > The list of resolved JIRA issues associated with this release can be found > under Change Log on the VCL 2.3 release page: > > https://cwiki.apache.org/VCL/vcl-23.html#VCL2.3-ChangeLog > > Installation instructions are on the Confluence site and in the INSTALLATION > file included in the artifact. > > I was able to successfully do a test install, including image deploying and > capture. > > The directory created by extracting the RC1 artifact is > "apache-VCL-2.3-RC1-incubating" (after extracting, you may want to rename it > to "apache-VCL-2.3-incubating" so you can copy and paste all of the commands > in the installation guide). Licensing information about perl and its required > modules, php and its required modules, and mysql are stated as "system > requirements" according to the information under "System Requirements" on > http://www.apache.org/legal/3party.html. > > Please vote by the end of the day on Friday, June 1st to publish this > release (this allows for 3 business days to vote). Please note that anyone in > the VCL community is allowed to vote. > > [ ] +1 yes, release VCL 2.3 > [ ] 0 dunno > [ ] -1 no, don't release VCL 2.3 (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.17 (GNU/Linux) > > iEYEARECAAYFAk/FMzYACgkQV/LQcNdtPQNOIwCfVwta+LYh0W+7tj9B39j5Owb0 > LPsAn29HkFQmU3lV2U54VrGsx2C4hZrg > =8DZ2 > -END PGP SIGNATURE- >
Re: [VOTE] release VCL 2.3
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 +1 __Jim On 5/29/2012 1:36 PM, Josh Thompson wrote: > We've finally reached a point where we do not seem to be finding > any more bugs. > > I created a release artifact based off of trunk. I copied trunk to > a tag under the tags area of the repo that is named > release-2.3-RC1: > > http://svn.apache.org/repos/asf/incubator/vcl/tags/release-2.3-RC1/ > > The artifact is an export from that tag with the addition of Dojo > Toolkit version 1.6.1 with a custom VCL profile bundled in the web > code. The artifact, MD5 and SHA1 sums, and my GPG signature of it > are available from my space on people.a.o: > > http://people.apache.org/~jfthomps/apache-VCL-2.3-RC1-incubating/ > > The list of resolved JIRA issues associated with this release can > be found under Change Log on the VCL 2.3 release page: > > https://cwiki.apache.org/VCL/vcl-23.html#VCL2.3-ChangeLog > > Installation instructions are on the Confluence site and in the > INSTALLATION file included in the artifact. > > I was able to successfully do a test install, including image > deploying and capture. > > The directory created by extracting the RC1 artifact is > "apache-VCL-2.3-RC1-incubating" (after extracting, you may want to > rename it to "apache-VCL-2.3-incubating" so you can copy and paste > all of the commands in the installation guide). Licensing > information about perl and its required modules, php and its > required modules, and mysql are stated as "system requirements" > according to the information under "System Requirements" on > http://www.apache.org/legal/3party.html. > > Please vote by the end of the day on Friday, June 1st to publish > this release (this allows for 3 business days to vote). Please > note that anyone in the VCL community is allowed to vote. > > [ ] +1 yes, release VCL 2.3 [ ] 0 dunno [ ] -1 no, don't release > VCL 2.3 (provide reasons if this is your vote) > > Josh > - -- Jim O'Dell Network Analyst California State University Fullerton Email: jod...@fullerton.edu Phone: (657) 278-2256 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk/GTGsACgkQREVHAOnXPYT/rQCfbSW+Llo4Ed44ogGdgLAlGJ0G 8tUAnAjH5fCK26Jtp7F/yHoXdHs16D+m =KXnh -END PGP SIGNATURE-
Re: [VOTE] release VCL 2.3
+1 On Tue, May 29, 2012 at 2:36 PM, Josh Thompson wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > We've finally reached a point where we do not seem to be finding any more > bugs. > > I created a release artifact based off of trunk. I copied trunk to a tag > under the tags area of the repo that is named release-2.3-RC1: > > http://svn.apache.org/repos/asf/incubator/vcl/tags/release-2.3-RC1/ > > The artifact is an export from that tag with the addition of Dojo Toolkit > version 1.6.1 with a custom VCL profile bundled in the web code. The > artifact, MD5 and SHA1 sums, and my GPG signature of it are available from > my > space on people.a.o: > > http://people.apache.org/~jfthomps/apache-VCL-2.3-RC1-incubating/ > > The list of resolved JIRA issues associated with this release can be found > under Change Log on the VCL 2.3 release page: > > https://cwiki.apache.org/VCL/vcl-23.html#VCL2.3-ChangeLog > > Installation instructions are on the Confluence site and in the > INSTALLATION > file included in the artifact. > > I was able to successfully do a test install, including image deploying and > capture. > > The directory created by extracting the RC1 artifact is > "apache-VCL-2.3-RC1-incubating" (after extracting, you may want to rename > it > to "apache-VCL-2.3-incubating" so you can copy and paste all of the > commands > in the installation guide). Licensing information about perl and its > required > modules, php and its required modules, and mysql are stated as "system > requirements" according to the information under "System Requirements" on > http://www.apache.org/legal/3party.html. > > Please vote by the end of the day on Friday, June 1st to publish this > release (this allows for 3 business days to vote). Please note that > anyone in > the VCL community is allowed to vote. > > [ ] +1 yes, release VCL 2.3 > [ ] 0 dunno > [ ] -1 no, don't release VCL 2.3 (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.17 (GNU/Linux) > > iEYEARECAAYFAk/FMzYACgkQV/LQcNdtPQNOIwCfVwta+LYh0W+7tj9B39j5Owb0 > LPsAn29HkFQmU3lV2U54VrGsx2C4hZrg > =8DZ2 > -END PGP SIGNATURE- > >
Re: [VOTE] release VCL 2.3
Here's my +1 Source, LICENSE/NOTICE, RAT, signature/checksum -- all look good to me. Seem to recall a discussion on this before, but just to be sure. Apache releases source code. PMC's vote on source releases. Many ASF projects also have binary distributions (which a PMC also evaluates and uses in evaluating the correctness of the release). The binaries are also convenient for many users. So, you end up with source and binary distributions of a project. There is no VCL binary/compilation (that I know of). So, the VCL release is a *source* release. One thing to note is that we don't maintain dojo in svn (we could do so). --kevan On May 29, 2012, at 4:36 PM, Josh Thompson wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > We've finally reached a point where we do not seem to be finding any more > bugs. > > I created a release artifact based off of trunk. I copied trunk to a tag > under the tags area of the repo that is named release-2.3-RC1: > > http://svn.apache.org/repos/asf/incubator/vcl/tags/release-2.3-RC1/ > > The artifact is an export from that tag with the addition of Dojo Toolkit > version 1.6.1 with a custom VCL profile bundled in the web code. The > artifact, MD5 and SHA1 sums, and my GPG signature of it are available from my > space on people.a.o: > > http://people.apache.org/~jfthomps/apache-VCL-2.3-RC1-incubating/ > > The list of resolved JIRA issues associated with this release can be found > under Change Log on the VCL 2.3 release page: > > https://cwiki.apache.org/VCL/vcl-23.html#VCL2.3-ChangeLog > > Installation instructions are on the Confluence site and in the INSTALLATION > file included in the artifact. > > I was able to successfully do a test install, including image deploying and > capture. > > The directory created by extracting the RC1 artifact is > "apache-VCL-2.3-RC1-incubating" (after extracting, you may want to rename it > to "apache-VCL-2.3-incubating" so you can copy and paste all of the commands > in the installation guide). Licensing information about perl and its > required > modules, php and its required modules, and mysql are stated as "system > requirements" according to the information under "System Requirements" on > http://www.apache.org/legal/3party.html. > > Please vote by the end of the day on Friday, June 1st to publish this > release (this allows for 3 business days to vote). Please note that anyone in > the VCL community is allowed to vote. > > [ ] +1 yes, release VCL 2.3 > [ ] 0 dunno > [ ] -1 no, don't release VCL 2.3 (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.17 (GNU/Linux) > > iEYEARECAAYFAk/FMzYACgkQV/LQcNdtPQNOIwCfVwta+LYh0W+7tj9B39j5Owb0 > LPsAn29HkFQmU3lV2U54VrGsx2C4hZrg > =8DZ2 > -END PGP SIGNATURE- >
Re: [VOTE] release VCL 2.3
+1 Thanks, Xianqing Yu IBM WSTI Intern -Original Message- From: Josh Thompson Sent: Tuesday, May 29, 2012 4:36 PM To: vcl-dev@incubator.apache.org Subject: [VOTE] release VCL 2.3 -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 We've finally reached a point where we do not seem to be finding any more bugs. I created a release artifact based off of trunk. I copied trunk to a tag under the tags area of the repo that is named release-2.3-RC1: http://svn.apache.org/repos/asf/incubator/vcl/tags/release-2.3-RC1/ The artifact is an export from that tag with the addition of Dojo Toolkit version 1.6.1 with a custom VCL profile bundled in the web code. The artifact, MD5 and SHA1 sums, and my GPG signature of it are available from my space on people.a.o: http://people.apache.org/~jfthomps/apache-VCL-2.3-RC1-incubating/ The list of resolved JIRA issues associated with this release can be found under Change Log on the VCL 2.3 release page: https://cwiki.apache.org/VCL/vcl-23.html#VCL2.3-ChangeLog Installation instructions are on the Confluence site and in the INSTALLATION file included in the artifact. I was able to successfully do a test install, including image deploying and capture. The directory created by extracting the RC1 artifact is "apache-VCL-2.3-RC1-incubating" (after extracting, you may want to rename it to "apache-VCL-2.3-incubating" so you can copy and paste all of the commands in the installation guide). Licensing information about perl and its required modules, php and its required modules, and mysql are stated as "system requirements" according to the information under "System Requirements" on http://www.apache.org/legal/3party.html. Please vote by the end of the day on Friday, June 1st to publish this release (this allows for 3 business days to vote). Please note that anyone in the VCL community is allowed to vote. [ ] +1 yes, release VCL 2.3 [ ] 0 dunno [ ] -1 no, don't release VCL 2.3 (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.17 (GNU/Linux) iEYEARECAAYFAk/FMzYACgkQV/LQcNdtPQNOIwCfVwta+LYh0W+7tj9B39j5Owb0 LPsAn29HkFQmU3lV2U54VrGsx2C4hZrg =8DZ2 -END PGP SIGNATURE-
Re: [VOTE] release VCL 2.3
+1 On Wed, May 30, 2012 at 9:07 AM, Miller, Tony wrote: > +1 > > -- > Tony Miller > Technology Consultant, ITCS > Austin 106N /\ 737-1515 /\ mill...@ecu.edu /\ http://blog.ecu.edu/techtips > > -Original Message- > From: Josh Thompson [mailto:josh_thomp...@ncsu.edu] > Sent: Tuesday, May 29, 2012 4:36 PM > To: vcl-dev@incubator.apache.org > Subject: [VOTE] release VCL 2.3 > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > We've finally reached a point where we do not seem to be finding any more > bugs. > > I created a release artifact based off of trunk. I copied trunk to a tag > under the tags area of the repo that is named release-2.3-RC1: > > http://svn.apache.org/repos/asf/incubator/vcl/tags/release-2.3-RC1/ > > The artifact is an export from that tag with the addition of Dojo Toolkit > version 1.6.1 with a custom VCL profile bundled in the web code. The > artifact, MD5 and SHA1 sums, and my GPG signature of it are available from my > space on people.a.o: > > http://people.apache.org/~jfthomps/apache-VCL-2.3-RC1-incubating/ > > The list of resolved JIRA issues associated with this release can be found > under Change Log on the VCL 2.3 release page: > > https://cwiki.apache.org/VCL/vcl-23.html#VCL2.3-ChangeLog > > Installation instructions are on the Confluence site and in the INSTALLATION > file included in the artifact. > > I was able to successfully do a test install, including image deploying and > capture. > > The directory created by extracting the RC1 artifact is > "apache-VCL-2.3-RC1-incubating" (after extracting, you may want to rename it > to "apache-VCL-2.3-incubating" so you can copy and paste all of the commands > in the installation guide). Licensing information about perl and its > required modules, php and its required modules, and mysql are stated as > "system requirements" according to the information under "System > Requirements" on http://www.apache.org/legal/3party.html. > > Please vote by the end of the day on Friday, June 1st to publish this release > (this allows for 3 business days to vote). Please note that anyone in the > VCL community is allowed to vote. > > [ ] +1 yes, release VCL 2.3 > [ ] 0 dunno > [ ] -1 no, don't release VCL 2.3 (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.17 (GNU/Linux) > > iEYEARECAAYFAk/FMzYACgkQV/LQcNdtPQNOIwCfVwta+LYh0W+7tj9B39j5Owb0 > LPsAn29HkFQmU3lV2U54VrGsx2C4hZrg > =8DZ2 > -END PGP SIGNATURE- > -- Mark Gardner --
RE: [VOTE] release VCL 2.3
+1 -- Tony Miller Technology Consultant, ITCS Austin 106N /\ 737-1515 /\ mill...@ecu.edu /\ http://blog.ecu.edu/techtips -Original Message- From: Josh Thompson [mailto:josh_thomp...@ncsu.edu] Sent: Tuesday, May 29, 2012 4:36 PM To: vcl-dev@incubator.apache.org Subject: [VOTE] release VCL 2.3 -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 We've finally reached a point where we do not seem to be finding any more bugs. I created a release artifact based off of trunk. I copied trunk to a tag under the tags area of the repo that is named release-2.3-RC1: http://svn.apache.org/repos/asf/incubator/vcl/tags/release-2.3-RC1/ The artifact is an export from that tag with the addition of Dojo Toolkit version 1.6.1 with a custom VCL profile bundled in the web code. The artifact, MD5 and SHA1 sums, and my GPG signature of it are available from my space on people.a.o: http://people.apache.org/~jfthomps/apache-VCL-2.3-RC1-incubating/ The list of resolved JIRA issues associated with this release can be found under Change Log on the VCL 2.3 release page: https://cwiki.apache.org/VCL/vcl-23.html#VCL2.3-ChangeLog Installation instructions are on the Confluence site and in the INSTALLATION file included in the artifact. I was able to successfully do a test install, including image deploying and capture. The directory created by extracting the RC1 artifact is "apache-VCL-2.3-RC1-incubating" (after extracting, you may want to rename it to "apache-VCL-2.3-incubating" so you can copy and paste all of the commands in the installation guide). Licensing information about perl and its required modules, php and its required modules, and mysql are stated as "system requirements" according to the information under "System Requirements" on http://www.apache.org/legal/3party.html. Please vote by the end of the day on Friday, June 1st to publish this release (this allows for 3 business days to vote). Please note that anyone in the VCL community is allowed to vote. [ ] +1 yes, release VCL 2.3 [ ] 0 dunno [ ] -1 no, don't release VCL 2.3 (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.17 (GNU/Linux) iEYEARECAAYFAk/FMzYACgkQV/LQcNdtPQNOIwCfVwta+LYh0W+7tj9B39j5Owb0 LPsAn29HkFQmU3lV2U54VrGsx2C4hZrg =8DZ2 -END PGP SIGNATURE-
Re: [VOTE] release VCL 2.3
[X ] +1 yes, release VCL 2.3 Art Art Vandenberg Georgia State University avandenb...@gsu.edu +1 404 413 4743 MS Information & Computer Science, Georgia Tech MVA Painting & Drawing, Georgia State http://www.gsu.edu/ist/research-computing/art-vandenberg.html On May 29, 2012, at 4:36 PM, Josh Thompson wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > We've finally reached a point where we do not seem to be finding any more > bugs. > > I created a release artifact based off of trunk. I copied trunk to a tag > under the tags area of the repo that is named release-2.3-RC1: > > http://svn.apache.org/repos/asf/incubator/vcl/tags/release-2.3-RC1/ > > The artifact is an export from that tag with the addition of Dojo Toolkit > version 1.6.1 with a custom VCL profile bundled in the web code. The > artifact, MD5 and SHA1 sums, and my GPG signature of it are available from my > space on people.a.o: > > http://people.apache.org/~jfthomps/apache-VCL-2.3-RC1-incubating/ > > The list of resolved JIRA issues associated with this release can be found > under Change Log on the VCL 2.3 release page: > > https://cwiki.apache.org/VCL/vcl-23.html#VCL2.3-ChangeLog > > Installation instructions are on the Confluence site and in the INSTALLATION > file included in the artifact. > > I was able to successfully do a test install, including image deploying and > capture. > > The directory created by extracting the RC1 artifact is > "apache-VCL-2.3-RC1-incubating" (after extracting, you may want to rename it > to "apache-VCL-2.3-incubating" so you can copy and paste all of the commands > in the installation guide). Licensing information about perl and its > required > modules, php and its required modules, and mysql are stated as "system > requirements" according to the information under "System Requirements" on > http://www.apache.org/legal/3party.html. > > Please vote by the end of the day on Friday, June 1st to publish this > release (this allows for 3 business days to vote). Please note that anyone in > the VCL community is allowed to vote. > > [ ] +1 yes, release VCL 2.3 > [ ] 0 dunno > [ ] -1 no, don't release VCL 2.3 (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.17 (GNU/Linux) > > iEYEARECAAYFAk/FMzYACgkQV/LQcNdtPQNOIwCfVwta+LYh0W+7tj9B39j5Owb0 > LPsAn29HkFQmU3lV2U54VrGsx2C4hZrg > =8DZ2 > -END PGP SIGNATURE- > >
Re: [VOTE] release VCL 2.3
+1 regards, Karuna On Tue, May 29, 2012 at 4:36 PM, Josh Thompson wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > We've finally reached a point where we do not seem to be finding any more > bugs. > > I created a release artifact based off of trunk. I copied trunk to a tag > under the tags area of the repo that is named release-2.3-RC1: > > http://svn.apache.org/repos/asf/incubator/vcl/tags/release-2.3-RC1/ > > The artifact is an export from that tag with the addition of Dojo Toolkit > version 1.6.1 with a custom VCL profile bundled in the web code. The > artifact, MD5 and SHA1 sums, and my GPG signature of it are available from > my > space on people.a.o: > > http://people.apache.org/~jfthomps/apache-VCL-2.3-RC1-incubating/ > > The list of resolved JIRA issues associated with this release can be found > under Change Log on the VCL 2.3 release page: > > https://cwiki.apache.org/VCL/vcl-23.html#VCL2.3-ChangeLog > > Installation instructions are on the Confluence site and in the > INSTALLATION > file included in the artifact. > > I was able to successfully do a test install, including image deploying and > capture. > > The directory created by extracting the RC1 artifact is > "apache-VCL-2.3-RC1-incubating" (after extracting, you may want to rename > it > to "apache-VCL-2.3-incubating" so you can copy and paste all of the > commands > in the installation guide). Licensing information about perl and its > required > modules, php and its required modules, and mysql are stated as "system > requirements" according to the information under "System Requirements" on > http://www.apache.org/legal/3party.html. > > Please vote by the end of the day on Friday, June 1st to publish this > release (this allows for 3 business days to vote). Please note that > anyone in > the VCL community is allowed to vote. > > [ ] +1 yes, release VCL 2.3 > [ ] 0 dunno > [ ] -1 no, don't release VCL 2.3 (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.17 (GNU/Linux) > > iEYEARECAAYFAk/FMzYACgkQV/LQcNdtPQNOIwCfVwta+LYh0W+7tj9B39j5Owb0 > LPsAn29HkFQmU3lV2U54VrGsx2C4hZrg > =8DZ2 > -END PGP SIGNATURE- > > -- regards, Karuna Karuna Pande Joshi PhD Candidate, CSEE Dept, UMBC kjos...@umbc.edu, karuna.jo...@umbc.edu
RE: [VOTE] release VCL 2.3
+1 Arbin Darren Sanders IT Manager - Academic Computing North Carolina Central University 712 Cecil Street Suite 3014 Durham, NC 27707 919.530.6307 919.530.5097 (Fax) For the Latest ITS Updates and Tips Join Us Online CONFIDENTIALITY: This email (including any attachments) may contain confidential, proprietary and privileged information, and unauthorized disclosure or use is prohibited. If you received this email in error, please notify the sender and delete this e-mail from your system. -Original Message- From: Josh Thompson [mailto:josh_thomp...@ncsu.edu] Sent: Tuesday, May 29, 2012 4:36 PM To: vcl-dev@incubator.apache.org Subject: [VOTE] release VCL 2.3 -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 We've finally reached a point where we do not seem to be finding any more bugs. I created a release artifact based off of trunk. I copied trunk to a tag under the tags area of the repo that is named release-2.3-RC1: http://svn.apache.org/repos/asf/incubator/vcl/tags/release-2.3-RC1/ The artifact is an export from that tag with the addition of Dojo Toolkit version 1.6.1 with a custom VCL profile bundled in the web code. The artifact, MD5 and SHA1 sums, and my GPG signature of it are available from my space on people.a.o: http://people.apache.org/~jfthomps/apache-VCL-2.3-RC1-incubating/ The list of resolved JIRA issues associated with this release can be found under Change Log on the VCL 2.3 release page: https://cwiki.apache.org/VCL/vcl-23.html#VCL2.3-ChangeLog Installation instructions are on the Confluence site and in the INSTALLATION file included in the artifact. I was able to successfully do a test install, including image deploying and capture. The directory created by extracting the RC1 artifact is "apache-VCL-2.3-RC1-incubating" (after extracting, you may want to rename it to "apache-VCL-2.3-incubating" so you can copy and paste all of the commands in the installation guide). Licensing information about perl and its required modules, php and its required modules, and mysql are stated as "system requirements" according to the information under "System Requirements" on http://www.apache.org/legal/3party.html. Please vote by the end of the day on Friday, June 1st to publish this release (this allows for 3 business days to vote). Please note that anyone in the VCL community is allowed to vote. [ ] +1 yes, release VCL 2.3 [ ] 0 dunno [ ] -1 no, don't release VCL 2.3 (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.17 (GNU/Linux) iEYEARECAAYFAk/FMzYACgkQV/LQcNdtPQNOIwCfVwta+LYh0W+7tj9B39j5Owb0 LPsAn29HkFQmU3lV2U54VrGsx2C4hZrg =8DZ2 -END PGP SIGNATURE- __ This email has been scanned by the Symantec Email Security.cloud service. For more information please visit http://www.symanteccloud.com __ __ This email has been scanned by the Symantec Email Security.cloud service. For more information please visit http://www.symanteccloud.com __
Re: [VOTE] release VCL 2.3
+1, definitely Young Hyun Oh IBM Tivoli CTO Technology and Architecture From: Aaron Peeler To: vcl-dev@incubator.apache.org, Date: 05/29/2012 04:56 PM Subject:Re: [VOTE] release VCL 2.3 +1 On Tue, May 29, 2012 at 4:36 PM, Josh Thompson wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > We've finally reached a point where we do not seem to be finding any more > bugs. > > I created a release artifact based off of trunk. I copied trunk to a tag > under the tags area of the repo that is named release-2.3-RC1: > > http://svn.apache.org/repos/asf/incubator/vcl/tags/release-2.3-RC1/ > > The artifact is an export from that tag with the addition of Dojo Toolkit > version 1.6.1 with a custom VCL profile bundled in the web code. The > artifact, MD5 and SHA1 sums, and my GPG signature of it are available from my > space on people.a.o: > > http://people.apache.org/~jfthomps/apache-VCL-2.3-RC1-incubating/ > > The list of resolved JIRA issues associated with this release can be found > under Change Log on the VCL 2.3 release page: > > https://cwiki.apache.org/VCL/vcl-23.html#VCL2.3-ChangeLog > > Installation instructions are on the Confluence site and in the INSTALLATION > file included in the artifact. > > I was able to successfully do a test install, including image deploying and > capture. > > The directory created by extracting the RC1 artifact is > "apache-VCL-2.3-RC1-incubating" (after extracting, you may want to rename it > to "apache-VCL-2.3-incubating" so you can copy and paste all of the commands > in the installation guide). Licensing information about perl and its required > modules, php and its required modules, and mysql are stated as "system > requirements" according to the information under "System Requirements" on > http://www.apache.org/legal/3party.html. > > Please vote by the end of the day on Friday, June 1st to publish this > release (this allows for 3 business days to vote). Please note that anyone in > the VCL community is allowed to vote. > > [ ] +1 yes, release VCL 2.3 > [ ] 0 dunno > [ ] -1 no, don't release VCL 2.3 (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.17 (GNU/Linux) > > iEYEARECAAYFAk/FMzYACgkQV/LQcNdtPQNOIwCfVwta+LYh0W+7tj9B39j5Owb0 > LPsAn29HkFQmU3lV2U54VrGsx2C4hZrg > =8DZ2 > -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 VCL 2.3
+1 On Tue, May 29, 2012 at 4:36 PM, Josh Thompson wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > We've finally reached a point where we do not seem to be finding any more > bugs. > > I created a release artifact based off of trunk. I copied trunk to a tag > under the tags area of the repo that is named release-2.3-RC1: > > http://svn.apache.org/repos/asf/incubator/vcl/tags/release-2.3-RC1/ > > The artifact is an export from that tag with the addition of Dojo Toolkit > version 1.6.1 with a custom VCL profile bundled in the web code. The > artifact, MD5 and SHA1 sums, and my GPG signature of it are available from my > space on people.a.o: > > http://people.apache.org/~jfthomps/apache-VCL-2.3-RC1-incubating/ > > The list of resolved JIRA issues associated with this release can be found > under Change Log on the VCL 2.3 release page: > > https://cwiki.apache.org/VCL/vcl-23.html#VCL2.3-ChangeLog > > Installation instructions are on the Confluence site and in the INSTALLATION > file included in the artifact. > > I was able to successfully do a test install, including image deploying and > capture. > > The directory created by extracting the RC1 artifact is > "apache-VCL-2.3-RC1-incubating" (after extracting, you may want to rename it > to "apache-VCL-2.3-incubating" so you can copy and paste all of the commands > in the installation guide). Licensing information about perl and its required > modules, php and its required modules, and mysql are stated as "system > requirements" according to the information under "System Requirements" on > http://www.apache.org/legal/3party.html. > > Please vote by the end of the day on Friday, June 1st to publish this > release (this allows for 3 business days to vote). Please note that anyone in > the VCL community is allowed to vote. > > [ ] +1 yes, release VCL 2.3 > [ ] 0 dunno > [ ] -1 no, don't release VCL 2.3 (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.17 (GNU/Linux) > > iEYEARECAAYFAk/FMzYACgkQV/LQcNdtPQNOIwCfVwta+LYh0W+7tj9B39j5Owb0 > LPsAn29HkFQmU3lV2U54VrGsx2C4hZrg > =8DZ2 > -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.
