[VOTE] release 2.4 (RC3)

[Josh Thompson <jo...@ncsu.edu>]

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

The issues identified in RC2 plus a few minor items have been fixed.  RC3 is 
now available for testing and voting upon.  Again, basically the same email 
with the voting deadline changed.

As Andy mentioned in his reply to the "release nearly ready" thread, all of
the (non-documentation) JIRA issues associated with 2.4 are now resolved.
Here is our first try at voting to release 2.4.

I created a release artifact based off of trunk.  I copied that branch to a
tag under the tags area of the repo that is named release-2.4-RC3:

http://svn.apache.org/repos/asf/vcl/tags/release-2.4-RC3/

The artifact is an export from that tag with the addition of Dojo Toolkit
version 1.6.2 with a custom VCL profile and Spyc both 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.4-RC3/

The list of resolved JIRA issues associated with this release can be found
under 2.4 on the Change Log page in the staging area of the CMS:

http://vcl.staging.apache.org/docs/changelog.html

This is the first release to include an installation script.  Installation
instructions on using the script and doing things manually are on the
following page in the staging area of the CMS:

http://vcl.staging.apache.org/docs/VCL24InstallGuide.html

The INSTALLATION file in the release artifact only contains information on
using the script.

*NOTE* To use the installation script with RC3, you need to give it the
- --rc=1 option (which is not included in the output of --help).

I was able to successfully do test installs and upgrades, including image
deploying and capture.

The directory created by extracting the RC3 artifact is "apache-VCL-2.4-RC3"
(after extracting, you may want to rename it to "apache-VCL-2.4" if you want
to test the manual instruction from the online installation guide).  Licensing
information about perl and its required modules, php and its required modules,
and mysql are stated as "system requirements" according to the information
under "System Requirements" on http://www.apache.org/legal/3party.html.

After we finalize a release vote, the staging part of the CMS will be
published to update the production site.

Please vote by 5pm (EST) on Tuesday, March 17th to publish this release.  
Everyone in the community is encouraged to vote if you have at least done some 
testing.  However, only votes by members of the PMC are binding votes.

[ ] +1 yes, release VCL 2.4
[ ] 0 dunno
[ ] -1 no, don't release VCL 2.4 (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

iEYEARECAAYFAlUDRJEACgkQV/LQcNdtPQNoaQCfXFvaia5zrXMgXInZ0HjShY9e
JrUAniNVC/Qwnc16uXZkhXw2DMA0zlZR
=HBn9
-----END PGP SIGNATURE-----

Re: [VOTE] release 2.4 (RC3)

[Andy Kurth <an...@ncsu.edu>]

We have been running the code from trunk on our production system since
this morning.  I have made a few reservations and captured an image.  I
have not encountered any problems.
-Andy

On Thu, Mar 19, 2015 at 4:31 PM, Andy Kurth <an...@ncsu.edu> wrote:

> I believe the problems described in VCL-839 are fixed in trunk.  I did not
> make any changes to vcl-install.sh, but updated the backend code to not
> rely on the management node's private IP address.  Please test it out.  The
> changes only affect Linux images.  When testing, be sure to verify the
> firewall is correct:
>
> -after an image loads, before post_load is executed (22 should be open to
> all IPs)
> -after post_load is executed (22 should be closed, all of management
> node's IPs should be allowed to connect to any port)
> -after a user clicks Connect but before connecting (22 should be open to
> any IP, management node access shouldn't change)
> -after a user connects (22 should be locked down to user's IP, management
> node access shouldn't change)
> -after a user clicks Connect and the reservation times out due to no
> initial connection, after sanitize is executed (22 should be closed to all,
> management node should still be allowed from any of its IPs to any port)
> -after pre_capture is executed (22 should be open to all)
> -after a user clicks Connect from a different remote IP address (22 should
> be allowed from user's original and new remote IP)
>
> It is also beneficial to test the outcome if the management node is only
> allowed to connect on port 22.  Manually change iptables and check the
> various stages.  Under no condition should the management node be locked
> out.
>
> We are essentially running 2.4 in production right now.  I'll update all
> of our management nodes tomorrow morning to trunk and we will watch things
> closely.  If no problems are identified, I think a release candidate could
> be created late in the day tomorrow.
>
> Thanks,
> Andy
>
> On Wed, Mar 18, 2015 at 4:09 PM, Andy Kurth <an...@ncsu.edu> wrote:
>
>>
>> On Wed, Mar 18, 2015 at 11:08 AM, Aaron Coburn <ac...@amherst.edu>
>> wrote:
>>
>>> I'm in favor of whatever would be least confusing to users. And that
>>> probably means waiting until a 2.4.1 release before announcing it on the
>>> a.o mailing list.
>>>
>>
>> Agree.
>>
>> Regarding 2.4.1, the problem discovered yesterday has been fixed in
>> trunk.  I tested a few 15-VM reservations using the code in trunk and
>> cluster_info was correct.
>>
>> However, I found another problem described in
>> https://issues.apache.org/jira/browse/VCL-839.  Using a slightly
>> modified vcl-install.sh, I installed a new CentOS 6.5 VM with VCL 2.4 and
>> then updated it with the code in trunk.  I was able to create a CentOS 6.5
>> base image and make reservations without any problems.  When I attempted to
>> capture one of the reservations, it failed because the management node had
>> locked itself out after the first user connection was detected.  This is
>> described ad nauseam in the Jira issue.
>>
>> The problem is partially due to vcl-install.sh using localhost by default
>> as the management node name.  We could change the script to use something
>> else.  Regardless, the management node name must resolve to the private IP
>> address or problems will occur.  The script should add an entry to
>> /etc/hosts so the MN's hostname in vcld.conf and the management node table
>> resolves to the MN's private IP address.  Josh primarily developed the
>> script but is travelling this week.  I can try to address the issues with
>> the script tomorrow.
>>
>> This will fix the install script but there are still problems with the
>> code.  A management node should never lock itself out.  These problems can
>> be pushed off in my opinion but we need to add to the install documentation
>> a step to make sure the MN's hostname resolves to its private IP address.
>>
>> Thought?
>>
>> Regards,
>> Andy
>>
>
>

Re: [VOTE] release 2.4 (RC3)

[Andy Kurth <an...@ncsu.edu>]

I believe the problems described in VCL-839 are fixed in trunk.  I did not
make any changes to vcl-install.sh, but updated the backend code to not
rely on the management node's private IP address.  Please test it out.  The
changes only affect Linux images.  When testing, be sure to verify the
firewall is correct:

-after an image loads, before post_load is executed (22 should be open to
all IPs)
-after post_load is executed (22 should be closed, all of management node's
IPs should be allowed to connect to any port)
-after a user clicks Connect but before connecting (22 should be open to
any IP, management node access shouldn't change)
-after a user connects (22 should be locked down to user's IP, management
node access shouldn't change)
-after a user clicks Connect and the reservation times out due to no
initial connection, after sanitize is executed (22 should be closed to all,
management node should still be allowed from any of its IPs to any port)
-after pre_capture is executed (22 should be open to all)
-after a user clicks Connect from a different remote IP address (22 should
be allowed from user's original and new remote IP)

It is also beneficial to test the outcome if the management node is only
allowed to connect on port 22.  Manually change iptables and check the
various stages.  Under no condition should the management node be locked
out.

We are essentially running 2.4 in production right now.  I'll update all of
our management nodes tomorrow morning to trunk and we will watch things
closely.  If no problems are identified, I think a release candidate could
be created late in the day tomorrow.

Thanks,
Andy

On Wed, Mar 18, 2015 at 4:09 PM, Andy Kurth <an...@ncsu.edu> wrote:

>
> On Wed, Mar 18, 2015 at 11:08 AM, Aaron Coburn <ac...@amherst.edu>
> wrote:
>
>> I'm in favor of whatever would be least confusing to users. And that
>> probably means waiting until a 2.4.1 release before announcing it on the
>> a.o mailing list.
>>
>
> Agree.
>
> Regarding 2.4.1, the problem discovered yesterday has been fixed in
> trunk.  I tested a few 15-VM reservations using the code in trunk and
> cluster_info was correct.
>
> However, I found another problem described in
> https://issues.apache.org/jira/browse/VCL-839.  Using a slightly modified
> vcl-install.sh, I installed a new CentOS 6.5 VM with VCL 2.4 and then
> updated it with the code in trunk.  I was able to create a CentOS 6.5 base
> image and make reservations without any problems.  When I attempted to
> capture one of the reservations, it failed because the management node had
> locked itself out after the first user connection was detected.  This is
> described ad nauseam in the Jira issue.
>
> The problem is partially due to vcl-install.sh using localhost by default
> as the management node name.  We could change the script to use something
> else.  Regardless, the management node name must resolve to the private IP
> address or problems will occur.  The script should add an entry to
> /etc/hosts so the MN's hostname in vcld.conf and the management node table
> resolves to the MN's private IP address.  Josh primarily developed the
> script but is travelling this week.  I can try to address the issues with
> the script tomorrow.
>
> This will fix the install script but there are still problems with the
> code.  A management node should never lock itself out.  These problems can
> be pushed off in my opinion but we need to add to the install documentation
> a step to make sure the MN's hostname resolves to its private IP address.
>
> Thought?
>
> Regards,
> Andy
>

Re: [VOTE] release 2.4 (RC3)

[Andy Kurth <an...@ncsu.edu>]

On Wed, Mar 18, 2015 at 11:08 AM, Aaron Coburn <ac...@amherst.edu> wrote:

> I'm in favor of whatever would be least confusing to users. And that
> probably means waiting until a 2.4.1 release before announcing it on the
> a.o mailing list.
>

Agree.

Regarding 2.4.1, the problem discovered yesterday has been fixed in trunk.
I tested a few 15-VM reservations using the code in trunk and cluster_info
was correct.

However, I found another problem described in
https://issues.apache.org/jira/browse/VCL-839.  Using a slightly modified
vcl-install.sh, I installed a new CentOS 6.5 VM with VCL 2.4 and then
updated it with the code in trunk.  I was able to create a CentOS 6.5 base
image and make reservations without any problems.  When I attempted to
capture one of the reservations, it failed because the management node had
locked itself out after the first user connection was detected.  This is
described ad nauseam in the Jira issue.

The problem is partially due to vcl-install.sh using localhost by default
as the management node name.  We could change the script to use something
else.  Regardless, the management node name must resolve to the private IP
address or problems will occur.  The script should add an entry to
/etc/hosts so the MN's hostname in vcld.conf and the management node table
resolves to the MN's private IP address.  Josh primarily developed the
script but is travelling this week.  I can try to address the issues with
the script tomorrow.

This will fix the install script but there are still problems with the
code.  A management node should never lock itself out.  These problems can
be pushed off in my opinion but we need to add to the install documentation
a step to make sure the MN's hostname resolves to its private IP address.

Thought?

Regards,
Andy

Re: [VOTE] release 2.4 (RC3)

[Aaron Coburn <ac...@amherst.edu>]

I'm in favor of whatever would be least confusing to users. And that probably means waiting until a 2.4.1 release before announcing it on the a.o mailing list.

Also, on the downloads page, we make note of previous releases, but I don't see that we provide links to them. So, I don't think this would be any different (make note of a 2.4.0 release, but only link to a 2.4.1 release)

Aaron Coburn

> On Mar 18, 2015, at 10:49 AM, Josh Thompson <jo...@ncsu.edu> wrote:
> 
> Signed PGP part
> I don't think we should. It's not something we want anyone using. We could send
> an email to the user@ list just to explain the situation though. It may also be
> worth creating a page in the CMS or WIKI that explains things.
> 
> Josh
> 
> 
> On Wed, Mar 18, 2015 at 10:01 AM, Aaron Coburn <ac...@amherst.edu> wrote:
> > Thanks, Josh.
> >
> > I think we should still announce the 2.4 release, even if we're in the midst of cutting 2.4.1
> >
> > Thoughts?
> >
> > -Aaron Coburn
> >
> >> On Mar 18, 2015, at 9:32 AM, Josh Thompson <jo...@ncsu.edu> wrote:
> >>
> >> The release is already out even though it is not officially announced. At
> >> this point we need to move to 2.4.1.
> >>
> >> This is at the bottom of our release process page at
> >>
> >> https://cwiki.apache.org/confluence/display/VCL/VCL+Release+Procedures
> >>
> >> "IMPORTANT: Once a release is copied to the dist location, it must not be
> >> modified. This can signal that an attack is being performed. If an error is
> >> found, a new .Z release should be made."
> >>
> >> That is also expressed under Understanding Release
> >> Distribution->Security->Modifications here
> >>
> >> http://incubator.apache.org/guides/releasemanagement.html
> >>
> >> Once things are fixed, I can cut 2.4.1-RC1. If that's by around 1:45pm
> >> (EDT), I should be able to get it out today. Otherwise, it will be sometime
> >> tomorrow.
> >>
> >> Josh
> >> On Mar 18, 2015 3:09 AM, "Andy Kurth" <an...@ncsu.edu> wrote:
> >>
> >>> Sorry for not sending this earlier.  Aaron P. and I identified a problem
> >>> today affecting cluster reservations when DHCP is used for public IP
> >>> addresses.  The IP addresses in the cluster_info file added to each node
> >>> may be wrong.  Essentially, vcld is caching some information to lessen the
> >>> load on the database.  As a result, an old IP address may be saved in the
> >>> cluster_info file and scripts an image creator saved in a cluster image
> >>> will certainly fail.  The fix to the backend code is trivial.
> >>>
> >>> Because this problem would cause unpredictable results for end users and
> >>> may cause certain cluster environments to be unusable, I would advise
> >>> against using 2.4 RC3 without modifying the code.  How should we handle
> >>> this?  I could be mistaken, but I am not aware of any hard-set rules
> >>> compelling us to release a version after a voting period ended if a known
> >>> problem is identified before the general public can obtain the release.
> >>> Unless there is a policy standing in the way, I propose creating RC4
> >>> tomorrow morning and closing a vote Monday 3/23 at the same time of day the
> >>> candidate is created.
> >>>
> >>> Thoughts?
> >>>
> >>> Regards,
> >>> Andy
> >>>
> >>>
> >>>
> >>> On Tue, Mar 17, 2015 at 6:37 PM, Josh Thompson <jo...@ncsu.edu>
> >>> wrote:
> >>>
> >>>> -----BEGIN PGP SIGNED MESSAGE-----
> >>>> Hash: SHA1
> >>>>
> >>>> Based on the following votes, the Apache VCL community has voted to
> >>> release
> >>>> Apache VCL 2.4:
> >>>>
> >>>> Josh Thompson (PMC member)
> >>>> Dmitri Chebotarov (PMC member)
> >>>> Alexander Patterson
> >>>> Aaron Coburn (PMC member)
> >>>> Andy Kurth (PMC chair)
> >>>> Aaron Peeler (PMC member)
> >>>>
> >>>> That's +5 from PMC members and another +1 from the community.  There were
> >>>> no 0
> >>>> or -1 votes.  That gives a total of 6 to pass the vote.
> >>>>
> >>>> I'll go ahead and create the release artifact and publish it to our
> >>>> distribution location. I'll give it around 24 hours for all of the
> >>> mirrors
> >>>> to
> >>>> pick it up and then send out an [ANNOUNCE] message.
> >>>>
> >>>> Thanks,
> >>>> Josh
> >>>>
> >>>> On Friday, March 13, 2015 4:11:56 PM you wrote:
> >>>>> The issues identified in RC2 plus a few minor items have been fixed.
> >>>> RC3 is
> >>>>> now available for testing and voting upon.  Again, basically the same
> >>>> email
> >>>>> with the voting deadline changed.
> >>>>>
> >>>>> As Andy mentioned in his reply to the "release nearly ready" thread,
> >>> all
> >>>> of
> >>>>> the (non-documentation) JIRA issues associated with 2.4 are now
> >>> resolved.
> >>>>> Here is our first try at voting to release 2.4.
> >>>>>
> >>>>> I created a release artifact based off of trunk.  I copied that branch
> >>>> to a
> >>>>> tag under the tags area of the repo that is named release-2.4-RC3:
> >>>>>
> >>>>> http://svn.apache.org/repos/asf/vcl/tags/release-2.4-RC3/
> >>>>>
> >>>>> The artifact is an export from that tag with the addition of Dojo
> >>> Toolkit
> >>>>> version 1.6.2 with a custom VCL profile and Spyc both 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.4-RC3/
> >>>>>
> >>>>> The list of resolved JIRA issues associated with this release can be
> >>>> found
> >>>>> under 2.4 on the Change Log page in the staging area of the CMS:
> >>>>>
> >>>>> http://vcl.staging.apache.org/docs/changelog.html
> >>>>>
> >>>>> This is the first release to include an installation script.
> >>>> Installation
> >>>>> instructions on using the script and doing things manually are on the
> >>>>> following page in the staging area of the CMS:
> >>>>>
> >>>>> http://vcl.staging.apache.org/docs/VCL24InstallGuide.html
> >>>>>
> >>>>> The INSTALLATION file in the release artifact only contains information
> >>>> on
> >>>>> using the script.
> >>>>>
> >>>>> *NOTE* To use the installation script with RC3, you need to give it the
> >>>>> --rc=1 option (which is not included in the output of --help).
> >>>>>
> >>>>> I was able to successfully do test installs and upgrades, including
> >>> image
> >>>>> deploying and capture.
> >>>>>
> >>>>> The directory created by extracting the RC3 artifact is
> >>>> "apache-VCL-2.4-RC3"
> >>>>> (after extracting, you may want to rename it to "apache-VCL-2.4" if you
> >>>>> want to test the manual instruction from the online installation
> >>> guide).
> >>>>> Licensing information about perl and its required modules, php and its
> >>>>> required modules, and mysql are stated as "system requirements"
> >>> according
> >>>>> to the information under "System Requirements" on
> >>>>> http://www.apache.org/legal/3party.html.
> >>>>>
> >>>>> After we finalize a release vote, the staging part of the CMS will be
> >>>>> published to update the production site.
> >>>>>
> >>>>> Please vote by 5pm (EST) on Tuesday, March 17th to publish this
> >>> release.
> >>>>> Everyone in the community is encouraged to vote if you have at least
> >>> done
> >>>>> some testing.  However, only votes by members of the PMC are binding
> >>>> votes.
> >>>>>
> >>>>> [ ] +1 yes, release VCL 2.4
> >>>>> [ ] 0 dunno
> >>>>> [ ] -1 no, don't release VCL 2.4 (provide reasons if this is your vote)
> >>>> - --
> >>>> - -------------------------------
> >>>> 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
> >>>>
> >>>> iEYEARECAAYFAlUIqywACgkQV/LQcNdtPQMqKACfVhK/zapJUkJu6K6snOAj9OB7
> >>>> j+0AnRlRcNHgUaznbz26+FauRV9+Z5M5
> >>>> =btE8
> >>>> -----END PGP SIGNATURE-----
> >>>>
> >>>
> >
> 
> 
> 
> --
> --
> -------------------------------
> Josh Thompson
> Systems Programmer
> Advanced Computing | VCL Developer
> North Carolina State University
> 
> Josh_Thompson@ncsu.edu
> 919-515-5323
> 
> (message not signed because it was sent through Gmail web interface)
> 
> All electronic mail messages in connection with State business which
> are sent to or received by this account are subject to the NC Public
> Records Law and may be disclosed to third parties.

Re: [VOTE] release 2.4 (RC3)

[Josh Thompson <jo...@ncsu.edu>]

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

I don't think we should. It's not something we want anyone using. We could send
an email to the user@ list just to explain the situation though. It may also be
worth creating a page in the CMS or WIKI that explains things.

Josh
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iEYEARECAAYFAlUJkF8ACgkQV/LQcNdtPQMI0ACdHv/jSDw7I64aY3pV+lQF0+zM
BTYAn2SNewvmBBcZexGrUbAk6wbXNyI8
=MIt5
-----END PGP SIGNATURE-----

On Wed, Mar 18, 2015 at 10:01 AM, Aaron Coburn <ac...@amherst.edu> wrote:
> Thanks, Josh.
>
> I think we should still announce the 2.4 release, even if we're in the midst of cutting 2.4.1
>
> Thoughts?
>
> -Aaron Coburn
>
>> On Mar 18, 2015, at 9:32 AM, Josh Thompson <jo...@ncsu.edu> wrote:
>>
>> The release is already out even though it is not officially announced. At
>> this point we need to move to 2.4.1.
>>
>> This is at the bottom of our release process page at
>>
>> https://cwiki.apache.org/confluence/display/VCL/VCL+Release+Procedures
>>
>> "IMPORTANT: Once a release is copied to the dist location, it must not be
>> modified. This can signal that an attack is being performed. If an error is
>> found, a new .Z release should be made."
>>
>> That is also expressed under Understanding Release
>> Distribution->Security->Modifications here
>>
>> http://incubator.apache.org/guides/releasemanagement.html
>>
>> Once things are fixed, I can cut 2.4.1-RC1. If that's by around 1:45pm
>> (EDT), I should be able to get it out today. Otherwise, it will be sometime
>> tomorrow.
>>
>> Josh
>> On Mar 18, 2015 3:09 AM, "Andy Kurth" <an...@ncsu.edu> wrote:
>>
>>> Sorry for not sending this earlier.  Aaron P. and I identified a problem
>>> today affecting cluster reservations when DHCP is used for public IP
>>> addresses.  The IP addresses in the cluster_info file added to each node
>>> may be wrong.  Essentially, vcld is caching some information to lessen the
>>> load on the database.  As a result, an old IP address may be saved in the
>>> cluster_info file and scripts an image creator saved in a cluster image
>>> will certainly fail.  The fix to the backend code is trivial.
>>>
>>> Because this problem would cause unpredictable results for end users and
>>> may cause certain cluster environments to be unusable, I would advise
>>> against using 2.4 RC3 without modifying the code.  How should we handle
>>> this?  I could be mistaken, but I am not aware of any hard-set rules
>>> compelling us to release a version after a voting period ended if a known
>>> problem is identified before the general public can obtain the release.
>>> Unless there is a policy standing in the way, I propose creating RC4
>>> tomorrow morning and closing a vote Monday 3/23 at the same time of day the
>>> candidate is created.
>>>
>>> Thoughts?
>>>
>>> Regards,
>>> Andy
>>>
>>>
>>>
>>> On Tue, Mar 17, 2015 at 6:37 PM, Josh Thompson <jo...@ncsu.edu>
>>> wrote:
>>>
>>>> -----BEGIN PGP SIGNED MESSAGE-----
>>>> Hash: SHA1
>>>>
>>>> Based on the following votes, the Apache VCL community has voted to
>>> release
>>>> Apache VCL 2.4:
>>>>
>>>> Josh Thompson (PMC member)
>>>> Dmitri Chebotarov (PMC member)
>>>> Alexander Patterson
>>>> Aaron Coburn (PMC member)
>>>> Andy Kurth (PMC chair)
>>>> Aaron Peeler (PMC member)
>>>>
>>>> That's +5 from PMC members and another +1 from the community.  There were
>>>> no 0
>>>> or -1 votes.  That gives a total of 6 to pass the vote.
>>>>
>>>> I'll go ahead and create the release artifact and publish it to our
>>>> distribution location. I'll give it around 24 hours for all of the
>>> mirrors
>>>> to
>>>> pick it up and then send out an [ANNOUNCE] message.
>>>>
>>>> Thanks,
>>>> Josh
>>>>
>>>> On Friday, March 13, 2015 4:11:56 PM you wrote:
>>>>> The issues identified in RC2 plus a few minor items have been fixed.
>>>> RC3 is
>>>>> now available for testing and voting upon.  Again, basically the same
>>>> email
>>>>> with the voting deadline changed.
>>>>>
>>>>> As Andy mentioned in his reply to the "release nearly ready" thread,
>>> all
>>>> of
>>>>> the (non-documentation) JIRA issues associated with 2.4 are now
>>> resolved.
>>>>> Here is our first try at voting to release 2.4.
>>>>>
>>>>> I created a release artifact based off of trunk.  I copied that branch
>>>> to a
>>>>> tag under the tags area of the repo that is named release-2.4-RC3:
>>>>>
>>>>> http://svn.apache.org/repos/asf/vcl/tags/release-2.4-RC3/
>>>>>
>>>>> The artifact is an export from that tag with the addition of Dojo
>>> Toolkit
>>>>> version 1.6.2 with a custom VCL profile and Spyc both 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.4-RC3/
>>>>>
>>>>> The list of resolved JIRA issues associated with this release can be
>>>> found
>>>>> under 2.4 on the Change Log page in the staging area of the CMS:
>>>>>
>>>>> http://vcl.staging.apache.org/docs/changelog.html
>>>>>
>>>>> This is the first release to include an installation script.
>>>> Installation
>>>>> instructions on using the script and doing things manually are on the
>>>>> following page in the staging area of the CMS:
>>>>>
>>>>> http://vcl.staging.apache.org/docs/VCL24InstallGuide.html
>>>>>
>>>>> The INSTALLATION file in the release artifact only contains information
>>>> on
>>>>> using the script.
>>>>>
>>>>> *NOTE* To use the installation script with RC3, you need to give it the
>>>>> --rc=1 option (which is not included in the output of --help).
>>>>>
>>>>> I was able to successfully do test installs and upgrades, including
>>> image
>>>>> deploying and capture.
>>>>>
>>>>> The directory created by extracting the RC3 artifact is
>>>> "apache-VCL-2.4-RC3"
>>>>> (after extracting, you may want to rename it to "apache-VCL-2.4" if you
>>>>> want to test the manual instruction from the online installation
>>> guide).
>>>>> Licensing information about perl and its required modules, php and its
>>>>> required modules, and mysql are stated as "system requirements"
>>> according
>>>>> to the information under "System Requirements" on
>>>>> http://www.apache.org/legal/3party.html.
>>>>>
>>>>> After we finalize a release vote, the staging part of the CMS will be
>>>>> published to update the production site.
>>>>>
>>>>> Please vote by 5pm (EST) on Tuesday, March 17th to publish this
>>> release.
>>>>> Everyone in the community is encouraged to vote if you have at least
>>> done
>>>>> some testing.  However, only votes by members of the PMC are binding
>>>> votes.
>>>>>
>>>>> [ ] +1 yes, release VCL 2.4
>>>>> [ ] 0 dunno
>>>>> [ ] -1 no, don't release VCL 2.4 (provide reasons if this is your vote)
>>>> - --
>>>> - -------------------------------
>>>> 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
>>>>
>>>> iEYEARECAAYFAlUIqywACgkQV/LQcNdtPQMqKACfVhK/zapJUkJu6K6snOAj9OB7
>>>> j+0AnRlRcNHgUaznbz26+FauRV9+Z5M5
>>>> =btE8
>>>> -----END PGP SIGNATURE-----
>>>>
>>>
>



-- 
--
-------------------------------
Josh Thompson
Systems Programmer
Advanced Computing | VCL Developer
North Carolina State University

Josh_Thompson@ncsu.edu
919-515-5323

(message not signed because it was sent through Gmail web interface)

All electronic mail messages in connection with State business which
are sent to or received by this account are subject to the NC Public
Records Law and may be disclosed to third parties.

Re: [VOTE] release 2.4 (RC3)

[Aaron Coburn <ac...@amherst.edu>]

Thanks, Josh.

I think we should still announce the 2.4 release, even if we're in the midst of cutting 2.4.1

Thoughts?

-Aaron Coburn

> On Mar 18, 2015, at 9:32 AM, Josh Thompson <jo...@ncsu.edu> wrote:
> 
> The release is already out even though it is not officially announced. At
> this point we need to move to 2.4.1.
> 
> This is at the bottom of our release process page at
> 
> https://cwiki.apache.org/confluence/display/VCL/VCL+Release+Procedures
> 
> "IMPORTANT: Once a release is copied to the dist location, it must not be
> modified. This can signal that an attack is being performed. If an error is
> found, a new .Z release should be made."
> 
> That is also expressed under Understanding Release
> Distribution->Security->Modifications here
> 
> http://incubator.apache.org/guides/releasemanagement.html
> 
> Once things are fixed, I can cut 2.4.1-RC1. If that's by around 1:45pm
> (EDT), I should be able to get it out today. Otherwise, it will be sometime
> tomorrow.
> 
> Josh
> On Mar 18, 2015 3:09 AM, "Andy Kurth" <an...@ncsu.edu> wrote:
> 
>> Sorry for not sending this earlier.  Aaron P. and I identified a problem
>> today affecting cluster reservations when DHCP is used for public IP
>> addresses.  The IP addresses in the cluster_info file added to each node
>> may be wrong.  Essentially, vcld is caching some information to lessen the
>> load on the database.  As a result, an old IP address may be saved in the
>> cluster_info file and scripts an image creator saved in a cluster image
>> will certainly fail.  The fix to the backend code is trivial.
>> 
>> Because this problem would cause unpredictable results for end users and
>> may cause certain cluster environments to be unusable, I would advise
>> against using 2.4 RC3 without modifying the code.  How should we handle
>> this?  I could be mistaken, but I am not aware of any hard-set rules
>> compelling us to release a version after a voting period ended if a known
>> problem is identified before the general public can obtain the release.
>> Unless there is a policy standing in the way, I propose creating RC4
>> tomorrow morning and closing a vote Monday 3/23 at the same time of day the
>> candidate is created.
>> 
>> Thoughts?
>> 
>> Regards,
>> Andy
>> 
>> 
>> 
>> On Tue, Mar 17, 2015 at 6:37 PM, Josh Thompson <jo...@ncsu.edu>
>> wrote:
>> 
>>> -----BEGIN PGP SIGNED MESSAGE-----
>>> Hash: SHA1
>>> 
>>> Based on the following votes, the Apache VCL community has voted to
>> release
>>> Apache VCL 2.4:
>>> 
>>> Josh Thompson (PMC member)
>>> Dmitri Chebotarov (PMC member)
>>> Alexander Patterson
>>> Aaron Coburn (PMC member)
>>> Andy Kurth (PMC chair)
>>> Aaron Peeler (PMC member)
>>> 
>>> That's +5 from PMC members and another +1 from the community.  There were
>>> no 0
>>> or -1 votes.  That gives a total of 6 to pass the vote.
>>> 
>>> I'll go ahead and create the release artifact and publish it to our
>>> distribution location. I'll give it around 24 hours for all of the
>> mirrors
>>> to
>>> pick it up and then send out an [ANNOUNCE] message.
>>> 
>>> Thanks,
>>> Josh
>>> 
>>> On Friday, March 13, 2015 4:11:56 PM you wrote:
>>>> The issues identified in RC2 plus a few minor items have been fixed.
>>> RC3 is
>>>> now available for testing and voting upon.  Again, basically the same
>>> email
>>>> with the voting deadline changed.
>>>> 
>>>> As Andy mentioned in his reply to the "release nearly ready" thread,
>> all
>>> of
>>>> the (non-documentation) JIRA issues associated with 2.4 are now
>> resolved.
>>>> Here is our first try at voting to release 2.4.
>>>> 
>>>> I created a release artifact based off of trunk.  I copied that branch
>>> to a
>>>> tag under the tags area of the repo that is named release-2.4-RC3:
>>>> 
>>>> http://svn.apache.org/repos/asf/vcl/tags/release-2.4-RC3/
>>>> 
>>>> The artifact is an export from that tag with the addition of Dojo
>> Toolkit
>>>> version 1.6.2 with a custom VCL profile and Spyc both 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.4-RC3/
>>>> 
>>>> The list of resolved JIRA issues associated with this release can be
>>> found
>>>> under 2.4 on the Change Log page in the staging area of the CMS:
>>>> 
>>>> http://vcl.staging.apache.org/docs/changelog.html
>>>> 
>>>> This is the first release to include an installation script.
>>> Installation
>>>> instructions on using the script and doing things manually are on the
>>>> following page in the staging area of the CMS:
>>>> 
>>>> http://vcl.staging.apache.org/docs/VCL24InstallGuide.html
>>>> 
>>>> The INSTALLATION file in the release artifact only contains information
>>> on
>>>> using the script.
>>>> 
>>>> *NOTE* To use the installation script with RC3, you need to give it the
>>>> --rc=1 option (which is not included in the output of --help).
>>>> 
>>>> I was able to successfully do test installs and upgrades, including
>> image
>>>> deploying and capture.
>>>> 
>>>> The directory created by extracting the RC3 artifact is
>>> "apache-VCL-2.4-RC3"
>>>> (after extracting, you may want to rename it to "apache-VCL-2.4" if you
>>>> want to test the manual instruction from the online installation
>> guide).
>>>> Licensing information about perl and its required modules, php and its
>>>> required modules, and mysql are stated as "system requirements"
>> according
>>>> to the information under "System Requirements" on
>>>> http://www.apache.org/legal/3party.html.
>>>> 
>>>> After we finalize a release vote, the staging part of the CMS will be
>>>> published to update the production site.
>>>> 
>>>> Please vote by 5pm (EST) on Tuesday, March 17th to publish this
>> release.
>>>> Everyone in the community is encouraged to vote if you have at least
>> done
>>>> some testing.  However, only votes by members of the PMC are binding
>>> votes.
>>>> 
>>>> [ ] +1 yes, release VCL 2.4
>>>> [ ] 0 dunno
>>>> [ ] -1 no, don't release VCL 2.4 (provide reasons if this is your vote)
>>> - --
>>> - -------------------------------
>>> 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
>>> 
>>> iEYEARECAAYFAlUIqywACgkQV/LQcNdtPQMqKACfVhK/zapJUkJu6K6snOAj9OB7
>>> j+0AnRlRcNHgUaznbz26+FauRV9+Z5M5
>>> =btE8
>>> -----END PGP SIGNATURE-----
>>> 
>> 

Re: [VOTE] release 2.4 (RC3)

[Josh Thompson <jo...@ncsu.edu>]

The release is already out even though it is not officially announced. At
this point we need to move to 2.4.1.

This is at the bottom of our release process page at

https://cwiki.apache.org/confluence/display/VCL/VCL+Release+Procedures

"IMPORTANT: Once a release is copied to the dist location, it must not be
modified. This can signal that an attack is being performed. If an error is
found, a new .Z release should be made."

That is also expressed under Understanding Release
Distribution->Security->Modifications here

http://incubator.apache.org/guides/releasemanagement.html

Once things are fixed, I can cut 2.4.1-RC1. If that's by around 1:45pm
(EDT), I should be able to get it out today. Otherwise, it will be sometime
tomorrow.

Josh
On Mar 18, 2015 3:09 AM, "Andy Kurth" <an...@ncsu.edu> wrote:

> Sorry for not sending this earlier.  Aaron P. and I identified a problem
> today affecting cluster reservations when DHCP is used for public IP
> addresses.  The IP addresses in the cluster_info file added to each node
> may be wrong.  Essentially, vcld is caching some information to lessen the
> load on the database.  As a result, an old IP address may be saved in the
> cluster_info file and scripts an image creator saved in a cluster image
> will certainly fail.  The fix to the backend code is trivial.
>
> Because this problem would cause unpredictable results for end users and
> may cause certain cluster environments to be unusable, I would advise
> against using 2.4 RC3 without modifying the code.  How should we handle
> this?  I could be mistaken, but I am not aware of any hard-set rules
> compelling us to release a version after a voting period ended if a known
> problem is identified before the general public can obtain the release.
> Unless there is a policy standing in the way, I propose creating RC4
> tomorrow morning and closing a vote Monday 3/23 at the same time of day the
> candidate is created.
>
> Thoughts?
>
> Regards,
> Andy
>
>
>
> On Tue, Mar 17, 2015 at 6:37 PM, Josh Thompson <jo...@ncsu.edu>
> wrote:
>
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > Based on the following votes, the Apache VCL community has voted to
> release
> > Apache VCL 2.4:
> >
> > Josh Thompson (PMC member)
> > Dmitri Chebotarov (PMC member)
> > Alexander Patterson
> > Aaron Coburn (PMC member)
> > Andy Kurth (PMC chair)
> > Aaron Peeler (PMC member)
> >
> > That's +5 from PMC members and another +1 from the community.  There were
> > no 0
> > or -1 votes.  That gives a total of 6 to pass the vote.
> >
> > I'll go ahead and create the release artifact and publish it to our
> > distribution location. I'll give it around 24 hours for all of the
> mirrors
> > to
> > pick it up and then send out an [ANNOUNCE] message.
> >
> > Thanks,
> > Josh
> >
> > On Friday, March 13, 2015 4:11:56 PM you wrote:
> > > The issues identified in RC2 plus a few minor items have been fixed.
> > RC3 is
> > > now available for testing and voting upon.  Again, basically the same
> > email
> > > with the voting deadline changed.
> > >
> > > As Andy mentioned in his reply to the "release nearly ready" thread,
> all
> > of
> > > the (non-documentation) JIRA issues associated with 2.4 are now
> resolved.
> > > Here is our first try at voting to release 2.4.
> > >
> > > I created a release artifact based off of trunk.  I copied that branch
> > to a
> > > tag under the tags area of the repo that is named release-2.4-RC3:
> > >
> > > http://svn.apache.org/repos/asf/vcl/tags/release-2.4-RC3/
> > >
> > > The artifact is an export from that tag with the addition of Dojo
> Toolkit
> > > version 1.6.2 with a custom VCL profile and Spyc both 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.4-RC3/
> > >
> > > The list of resolved JIRA issues associated with this release can be
> > found
> > > under 2.4 on the Change Log page in the staging area of the CMS:
> > >
> > > http://vcl.staging.apache.org/docs/changelog.html
> > >
> > > This is the first release to include an installation script.
> > Installation
> > > instructions on using the script and doing things manually are on the
> > > following page in the staging area of the CMS:
> > >
> > > http://vcl.staging.apache.org/docs/VCL24InstallGuide.html
> > >
> > > The INSTALLATION file in the release artifact only contains information
> > on
> > > using the script.
> > >
> > > *NOTE* To use the installation script with RC3, you need to give it the
> > > --rc=1 option (which is not included in the output of --help).
> > >
> > > I was able to successfully do test installs and upgrades, including
> image
> > > deploying and capture.
> > >
> > > The directory created by extracting the RC3 artifact is
> > "apache-VCL-2.4-RC3"
> > > (after extracting, you may want to rename it to "apache-VCL-2.4" if you
> > > want to test the manual instruction from the online installation
> guide).
> > > Licensing information about perl and its required modules, php and its
> > > required modules, and mysql are stated as "system requirements"
> according
> > > to the information under "System Requirements" on
> > > http://www.apache.org/legal/3party.html.
> > >
> > > After we finalize a release vote, the staging part of the CMS will be
> > > published to update the production site.
> > >
> > > Please vote by 5pm (EST) on Tuesday, March 17th to publish this
> release.
> > > Everyone in the community is encouraged to vote if you have at least
> done
> > > some testing.  However, only votes by members of the PMC are binding
> > votes.
> > >
> > > [ ] +1 yes, release VCL 2.4
> > > [ ] 0 dunno
> > > [ ] -1 no, don't release VCL 2.4 (provide reasons if this is your vote)
> > - --
> > - -------------------------------
> > 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
> >
> > iEYEARECAAYFAlUIqywACgkQV/LQcNdtPQMqKACfVhK/zapJUkJu6K6snOAj9OB7
> > j+0AnRlRcNHgUaznbz26+FauRV9+Z5M5
> > =btE8
> > -----END PGP SIGNATURE-----
> >
>

Re: [VOTE] release 2.4 (RC3)

[Andy Kurth <an...@ncsu.edu>]

That makes sense.  I have added a 2.4.1 version to Jira and created this
issue:
https://issues.apache.org/jira/browse/VCL-836

The fix has been committed to trunk.

-Andy



On Wed, Mar 18, 2015 at 9:14 AM, Aaron Coburn <ac...@amherst.edu> wrote:

> I think that, since the vote for 2.4 has already concluded and the
> artifacts have been published to the apache.org mirrors, we would need to
> cut a 2.4.1 release.
>
> -Aaron Coburn
>
>
> > On Mar 17, 2015, at 9:05 PM, Andy Kurth <an...@ncsu.edu> wrote:
> >
> > Sorry for not sending this earlier.  Aaron P. and I identified a problem
> > today affecting cluster reservations when DHCP is used for public IP
> > addresses.  The IP addresses in the cluster_info file added to each node
> > may be wrong.  Essentially, vcld is caching some information to lessen
> the
> > load on the database.  As a result, an old IP address may be saved in the
> > cluster_info file and scripts an image creator saved in a cluster image
> > will certainly fail.  The fix to the backend code is trivial.
> >
> > Because this problem would cause unpredictable results for end users and
> > may cause certain cluster environments to be unusable, I would advise
> > against using 2.4 RC3 without modifying the code.  How should we handle
> > this?  I could be mistaken, but I am not aware of any hard-set rules
> > compelling us to release a version after a voting period ended if a known
> > problem is identified before the general public can obtain the release.
> > Unless there is a policy standing in the way, I propose creating RC4
> > tomorrow morning and closing a vote Monday 3/23 at the same time of day
> the
> > candidate is created.
> >
> > Thoughts?
> >
> > Regards,
> > Andy
> >
> >
> >
> > On Tue, Mar 17, 2015 at 6:37 PM, Josh Thompson <jo...@ncsu.edu>
> > wrote:
> >
> >> -----BEGIN PGP SIGNED MESSAGE-----
> >> Hash: SHA1
> >>
> >> Based on the following votes, the Apache VCL community has voted to
> release
> >> Apache VCL 2.4:
> >>
> >> Josh Thompson (PMC member)
> >> Dmitri Chebotarov (PMC member)
> >> Alexander Patterson
> >> Aaron Coburn (PMC member)
> >> Andy Kurth (PMC chair)
> >> Aaron Peeler (PMC member)
> >>
> >> That's +5 from PMC members and another +1 from the community.  There
> were
> >> no 0
> >> or -1 votes.  That gives a total of 6 to pass the vote.
> >>
> >> I'll go ahead and create the release artifact and publish it to our
> >> distribution location. I'll give it around 24 hours for all of the
> mirrors
> >> to
> >> pick it up and then send out an [ANNOUNCE] message.
> >>
> >> Thanks,
> >> Josh
> >>
> >> On Friday, March 13, 2015 4:11:56 PM you wrote:
> >>> The issues identified in RC2 plus a few minor items have been fixed.
> >> RC3 is
> >>> now available for testing and voting upon.  Again, basically the same
> >> email
> >>> with the voting deadline changed.
> >>>
> >>> As Andy mentioned in his reply to the "release nearly ready" thread,
> all
> >> of
> >>> the (non-documentation) JIRA issues associated with 2.4 are now
> resolved.
> >>> Here is our first try at voting to release 2.4.
> >>>
> >>> I created a release artifact based off of trunk.  I copied that branch
> >> to a
> >>> tag under the tags area of the repo that is named release-2.4-RC3:
> >>>
> >>> http://svn.apache.org/repos/asf/vcl/tags/release-2.4-RC3/
> >>>
> >>> The artifact is an export from that tag with the addition of Dojo
> Toolkit
> >>> version 1.6.2 with a custom VCL profile and Spyc both 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.4-RC3/
> >>>
> >>> The list of resolved JIRA issues associated with this release can be
> >> found
> >>> under 2.4 on the Change Log page in the staging area of the CMS:
> >>>
> >>> http://vcl.staging.apache.org/docs/changelog.html
> >>>
> >>> This is the first release to include an installation script.
> >> Installation
> >>> instructions on using the script and doing things manually are on the
> >>> following page in the staging area of the CMS:
> >>>
> >>> http://vcl.staging.apache.org/docs/VCL24InstallGuide.html
> >>>
> >>> The INSTALLATION file in the release artifact only contains information
> >> on
> >>> using the script.
> >>>
> >>> *NOTE* To use the installation script with RC3, you need to give it the
> >>> --rc=1 option (which is not included in the output of --help).
> >>>
> >>> I was able to successfully do test installs and upgrades, including
> image
> >>> deploying and capture.
> >>>
> >>> The directory created by extracting the RC3 artifact is
> >> "apache-VCL-2.4-RC3"
> >>> (after extracting, you may want to rename it to "apache-VCL-2.4" if you
> >>> want to test the manual instruction from the online installation
> guide).
> >>> Licensing information about perl and its required modules, php and its
> >>> required modules, and mysql are stated as "system requirements"
> according
> >>> to the information under "System Requirements" on
> >>> http://www.apache.org/legal/3party.html.
> >>>
> >>> After we finalize a release vote, the staging part of the CMS will be
> >>> published to update the production site.
> >>>
> >>> Please vote by 5pm (EST) on Tuesday, March 17th to publish this
> release.
> >>> Everyone in the community is encouraged to vote if you have at least
> done
> >>> some testing.  However, only votes by members of the PMC are binding
> >> votes.
> >>>
> >>> [ ] +1 yes, release VCL 2.4
> >>> [ ] 0 dunno
> >>> [ ] -1 no, don't release VCL 2.4 (provide reasons if this is your vote)
> >> - --
> >> - -------------------------------
> >> 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
> >>
> >> iEYEARECAAYFAlUIqywACgkQV/LQcNdtPQMqKACfVhK/zapJUkJu6K6snOAj9OB7
> >> j+0AnRlRcNHgUaznbz26+FauRV9+Z5M5
> >> =btE8
> >> -----END PGP SIGNATURE-----
>
>

Re: [VOTE] release 2.4 (RC3)

[Aaron Coburn <ac...@amherst.edu>]

I think that, since the vote for 2.4 has already concluded and the artifacts have been published to the apache.org mirrors, we would need to cut a 2.4.1 release.

-Aaron Coburn


> On Mar 17, 2015, at 9:05 PM, Andy Kurth <an...@ncsu.edu> wrote:
> 
> Sorry for not sending this earlier.  Aaron P. and I identified a problem
> today affecting cluster reservations when DHCP is used for public IP
> addresses.  The IP addresses in the cluster_info file added to each node
> may be wrong.  Essentially, vcld is caching some information to lessen the
> load on the database.  As a result, an old IP address may be saved in the
> cluster_info file and scripts an image creator saved in a cluster image
> will certainly fail.  The fix to the backend code is trivial.
> 
> Because this problem would cause unpredictable results for end users and
> may cause certain cluster environments to be unusable, I would advise
> against using 2.4 RC3 without modifying the code.  How should we handle
> this?  I could be mistaken, but I am not aware of any hard-set rules
> compelling us to release a version after a voting period ended if a known
> problem is identified before the general public can obtain the release.
> Unless there is a policy standing in the way, I propose creating RC4
> tomorrow morning and closing a vote Monday 3/23 at the same time of day the
> candidate is created.
> 
> Thoughts?
> 
> Regards,
> Andy
> 
> 
> 
> On Tue, Mar 17, 2015 at 6:37 PM, Josh Thompson <jo...@ncsu.edu>
> wrote:
> 
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>> 
>> Based on the following votes, the Apache VCL community has voted to release
>> Apache VCL 2.4:
>> 
>> Josh Thompson (PMC member)
>> Dmitri Chebotarov (PMC member)
>> Alexander Patterson
>> Aaron Coburn (PMC member)
>> Andy Kurth (PMC chair)
>> Aaron Peeler (PMC member)
>> 
>> That's +5 from PMC members and another +1 from the community.  There were
>> no 0
>> or -1 votes.  That gives a total of 6 to pass the vote.
>> 
>> I'll go ahead and create the release artifact and publish it to our
>> distribution location. I'll give it around 24 hours for all of the mirrors
>> to
>> pick it up and then send out an [ANNOUNCE] message.
>> 
>> Thanks,
>> Josh
>> 
>> On Friday, March 13, 2015 4:11:56 PM you wrote:
>>> The issues identified in RC2 plus a few minor items have been fixed.
>> RC3 is
>>> now available for testing and voting upon.  Again, basically the same
>> email
>>> with the voting deadline changed.
>>> 
>>> As Andy mentioned in his reply to the "release nearly ready" thread, all
>> of
>>> the (non-documentation) JIRA issues associated with 2.4 are now resolved.
>>> Here is our first try at voting to release 2.4.
>>> 
>>> I created a release artifact based off of trunk.  I copied that branch
>> to a
>>> tag under the tags area of the repo that is named release-2.4-RC3:
>>> 
>>> http://svn.apache.org/repos/asf/vcl/tags/release-2.4-RC3/
>>> 
>>> The artifact is an export from that tag with the addition of Dojo Toolkit
>>> version 1.6.2 with a custom VCL profile and Spyc both 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.4-RC3/
>>> 
>>> The list of resolved JIRA issues associated with this release can be
>> found
>>> under 2.4 on the Change Log page in the staging area of the CMS:
>>> 
>>> http://vcl.staging.apache.org/docs/changelog.html
>>> 
>>> This is the first release to include an installation script.
>> Installation
>>> instructions on using the script and doing things manually are on the
>>> following page in the staging area of the CMS:
>>> 
>>> http://vcl.staging.apache.org/docs/VCL24InstallGuide.html
>>> 
>>> The INSTALLATION file in the release artifact only contains information
>> on
>>> using the script.
>>> 
>>> *NOTE* To use the installation script with RC3, you need to give it the
>>> --rc=1 option (which is not included in the output of --help).
>>> 
>>> I was able to successfully do test installs and upgrades, including image
>>> deploying and capture.
>>> 
>>> The directory created by extracting the RC3 artifact is
>> "apache-VCL-2.4-RC3"
>>> (after extracting, you may want to rename it to "apache-VCL-2.4" if you
>>> want to test the manual instruction from the online installation guide).
>>> Licensing information about perl and its required modules, php and its
>>> required modules, and mysql are stated as "system requirements" according
>>> to the information under "System Requirements" on
>>> http://www.apache.org/legal/3party.html.
>>> 
>>> After we finalize a release vote, the staging part of the CMS will be
>>> published to update the production site.
>>> 
>>> Please vote by 5pm (EST) on Tuesday, March 17th to publish this release.
>>> Everyone in the community is encouraged to vote if you have at least done
>>> some testing.  However, only votes by members of the PMC are binding
>> votes.
>>> 
>>> [ ] +1 yes, release VCL 2.4
>>> [ ] 0 dunno
>>> [ ] -1 no, don't release VCL 2.4 (provide reasons if this is your vote)
>> - --
>> - -------------------------------
>> 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
>> 
>> iEYEARECAAYFAlUIqywACgkQV/LQcNdtPQMqKACfVhK/zapJUkJu6K6snOAj9OB7
>> j+0AnRlRcNHgUaznbz26+FauRV9+Z5M5
>> =btE8
>> -----END PGP SIGNATURE-----

Re: [VOTE] release 2.4 (RC3)

[Andy Kurth <an...@ncsu.edu>]

Sorry for not sending this earlier.  Aaron P. and I identified a problem
today affecting cluster reservations when DHCP is used for public IP
addresses.  The IP addresses in the cluster_info file added to each node
may be wrong.  Essentially, vcld is caching some information to lessen the
load on the database.  As a result, an old IP address may be saved in the
cluster_info file and scripts an image creator saved in a cluster image
will certainly fail.  The fix to the backend code is trivial.

Because this problem would cause unpredictable results for end users and
may cause certain cluster environments to be unusable, I would advise
against using 2.4 RC3 without modifying the code.  How should we handle
this?  I could be mistaken, but I am not aware of any hard-set rules
compelling us to release a version after a voting period ended if a known
problem is identified before the general public can obtain the release.
Unless there is a policy standing in the way, I propose creating RC4
tomorrow morning and closing a vote Monday 3/23 at the same time of day the
candidate is created.

Thoughts?

Regards,
Andy



On Tue, Mar 17, 2015 at 6:37 PM, Josh Thompson <jo...@ncsu.edu>
wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Based on the following votes, the Apache VCL community has voted to release
> Apache VCL 2.4:
>
> Josh Thompson (PMC member)
> Dmitri Chebotarov (PMC member)
> Alexander Patterson
> Aaron Coburn (PMC member)
> Andy Kurth (PMC chair)
> Aaron Peeler (PMC member)
>
> That's +5 from PMC members and another +1 from the community.  There were
> no 0
> or -1 votes.  That gives a total of 6 to pass the vote.
>
> I'll go ahead and create the release artifact and publish it to our
> distribution location. I'll give it around 24 hours for all of the mirrors
> to
> pick it up and then send out an [ANNOUNCE] message.
>
> Thanks,
> Josh
>
> On Friday, March 13, 2015 4:11:56 PM you wrote:
> > The issues identified in RC2 plus a few minor items have been fixed.
> RC3 is
> > now available for testing and voting upon.  Again, basically the same
> email
> > with the voting deadline changed.
> >
> > As Andy mentioned in his reply to the "release nearly ready" thread, all
> of
> > the (non-documentation) JIRA issues associated with 2.4 are now resolved.
> > Here is our first try at voting to release 2.4.
> >
> > I created a release artifact based off of trunk.  I copied that branch
> to a
> > tag under the tags area of the repo that is named release-2.4-RC3:
> >
> > http://svn.apache.org/repos/asf/vcl/tags/release-2.4-RC3/
> >
> > The artifact is an export from that tag with the addition of Dojo Toolkit
> > version 1.6.2 with a custom VCL profile and Spyc both 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.4-RC3/
> >
> > The list of resolved JIRA issues associated with this release can be
> found
> > under 2.4 on the Change Log page in the staging area of the CMS:
> >
> > http://vcl.staging.apache.org/docs/changelog.html
> >
> > This is the first release to include an installation script.
> Installation
> > instructions on using the script and doing things manually are on the
> > following page in the staging area of the CMS:
> >
> > http://vcl.staging.apache.org/docs/VCL24InstallGuide.html
> >
> > The INSTALLATION file in the release artifact only contains information
> on
> > using the script.
> >
> > *NOTE* To use the installation script with RC3, you need to give it the
> > --rc=1 option (which is not included in the output of --help).
> >
> > I was able to successfully do test installs and upgrades, including image
> > deploying and capture.
> >
> > The directory created by extracting the RC3 artifact is
> "apache-VCL-2.4-RC3"
> > (after extracting, you may want to rename it to "apache-VCL-2.4" if you
> > want to test the manual instruction from the online installation guide).
> > Licensing information about perl and its required modules, php and its
> > required modules, and mysql are stated as "system requirements" according
> > to the information under "System Requirements" on
> > http://www.apache.org/legal/3party.html.
> >
> > After we finalize a release vote, the staging part of the CMS will be
> > published to update the production site.
> >
> > Please vote by 5pm (EST) on Tuesday, March 17th to publish this release.
> > Everyone in the community is encouraged to vote if you have at least done
> > some testing.  However, only votes by members of the PMC are binding
> votes.
> >
> > [ ] +1 yes, release VCL 2.4
> > [ ] 0 dunno
> > [ ] -1 no, don't release VCL 2.4 (provide reasons if this is your vote)
> - --
> - -------------------------------
> 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
>
> iEYEARECAAYFAlUIqywACgkQV/LQcNdtPQMqKACfVhK/zapJUkJu6K6snOAj9OB7
> j+0AnRlRcNHgUaznbz26+FauRV9+Z5M5
> =btE8
> -----END PGP SIGNATURE-----
>

Re: [VOTE] release 2.4 (RC3)

[Josh Thompson <jo...@ncsu.edu>]

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

Based on the following votes, the Apache VCL community has voted to release
Apache VCL 2.4:

Josh Thompson (PMC member)
Dmitri Chebotarov (PMC member)
Alexander Patterson
Aaron Coburn (PMC member)
Andy Kurth (PMC chair)
Aaron Peeler (PMC member)

That's +5 from PMC members and another +1 from the community.  There were no 0
or -1 votes.  That gives a total of 6 to pass the vote.

I'll go ahead and create the release artifact and publish it to our
distribution location. I'll give it around 24 hours for all of the mirrors to
pick it up and then send out an [ANNOUNCE] message.

Thanks,
Josh

On Friday, March 13, 2015 4:11:56 PM you wrote:
> The issues identified in RC2 plus a few minor items have been fixed.  RC3 is
> now available for testing and voting upon.  Again, basically the same email
> with the voting deadline changed.
>
> As Andy mentioned in his reply to the "release nearly ready" thread, all of
> the (non-documentation) JIRA issues associated with 2.4 are now resolved.
> Here is our first try at voting to release 2.4.
>
> I created a release artifact based off of trunk.  I copied that branch to a
> tag under the tags area of the repo that is named release-2.4-RC3:
>
> http://svn.apache.org/repos/asf/vcl/tags/release-2.4-RC3/
>
> The artifact is an export from that tag with the addition of Dojo Toolkit
> version 1.6.2 with a custom VCL profile and Spyc both 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.4-RC3/
>
> The list of resolved JIRA issues associated with this release can be found
> under 2.4 on the Change Log page in the staging area of the CMS:
>
> http://vcl.staging.apache.org/docs/changelog.html
>
> This is the first release to include an installation script.  Installation
> instructions on using the script and doing things manually are on the
> following page in the staging area of the CMS:
>
> http://vcl.staging.apache.org/docs/VCL24InstallGuide.html
>
> The INSTALLATION file in the release artifact only contains information on
> using the script.
>
> *NOTE* To use the installation script with RC3, you need to give it the
> --rc=1 option (which is not included in the output of --help).
>
> I was able to successfully do test installs and upgrades, including image
> deploying and capture.
>
> The directory created by extracting the RC3 artifact is "apache-VCL-2.4-RC3"
> (after extracting, you may want to rename it to "apache-VCL-2.4" if you
> want to test the manual instruction from the online installation guide).
> Licensing information about perl and its required modules, php and its
> required modules, and mysql are stated as "system requirements" according
> to the information under "System Requirements" on
> http://www.apache.org/legal/3party.html.
>
> After we finalize a release vote, the staging part of the CMS will be
> published to update the production site.
>
> Please vote by 5pm (EST) on Tuesday, March 17th to publish this release.
> Everyone in the community is encouraged to vote if you have at least done
> some testing.  However, only votes by members of the PMC are binding votes.
>
> [ ] +1 yes, release VCL 2.4
> [ ] 0 dunno
> [ ] -1 no, don't release VCL 2.4 (provide reasons if this is your vote)
- --
- -------------------------------
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

iEYEARECAAYFAlUIqywACgkQV/LQcNdtPQMqKACfVhK/zapJUkJu6K6snOAj9OB7
j+0AnRlRcNHgUaznbz26+FauRV9+Z5M5
=btE8
-----END PGP SIGNATURE-----

Re: [VOTE] release 2.4 (RC3)

[Aaron Peeler <fa...@ncsu.edu>]

+1

Aaron Peeler

On Fri, Mar 13, 2015 at 4:11 PM, Josh Thompson <jo...@ncsu.edu> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> The issues identified in RC2 plus a few minor items have been fixed.  RC3 is
> now available for testing and voting upon.  Again, basically the same email
> with the voting deadline changed.
>
> As Andy mentioned in his reply to the "release nearly ready" thread, all of
> the (non-documentation) JIRA issues associated with 2.4 are now resolved.
> Here is our first try at voting to release 2.4.
>
> I created a release artifact based off of trunk.  I copied that branch to a
> tag under the tags area of the repo that is named release-2.4-RC3:
>
> http://svn.apache.org/repos/asf/vcl/tags/release-2.4-RC3/
>
> The artifact is an export from that tag with the addition of Dojo Toolkit
> version 1.6.2 with a custom VCL profile and Spyc both 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.4-RC3/
>
> The list of resolved JIRA issues associated with this release can be found
> under 2.4 on the Change Log page in the staging area of the CMS:
>
> http://vcl.staging.apache.org/docs/changelog.html
>
> This is the first release to include an installation script.  Installation
> instructions on using the script and doing things manually are on the
> following page in the staging area of the CMS:
>
> http://vcl.staging.apache.org/docs/VCL24InstallGuide.html
>
> The INSTALLATION file in the release artifact only contains information on
> using the script.
>
> *NOTE* To use the installation script with RC3, you need to give it the
> - --rc=1 option (which is not included in the output of --help).
>
> I was able to successfully do test installs and upgrades, including image
> deploying and capture.
>
> The directory created by extracting the RC3 artifact is "apache-VCL-2.4-RC3"
> (after extracting, you may want to rename it to "apache-VCL-2.4" if you want
> to test the manual instruction from the online installation guide).  Licensing
> information about perl and its required modules, php and its required modules,
> and mysql are stated as "system requirements" according to the information
> under "System Requirements" on http://www.apache.org/legal/3party.html.
>
> After we finalize a release vote, the staging part of the CMS will be
> published to update the production site.
>
> Please vote by 5pm (EST) on Tuesday, March 17th to publish this release.
> Everyone in the community is encouraged to vote if you have at least done some
> testing.  However, only votes by members of the PMC are binding votes.
>
> [ ] +1 yes, release VCL 2.4
> [ ] 0 dunno
> [ ] -1 no, don't release VCL 2.4 (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
>
> iEYEARECAAYFAlUDRJEACgkQV/LQcNdtPQNoaQCfXFvaia5zrXMgXInZ0HjShY9e
> JrUAniNVC/Qwnc16uXZkhXw2DMA0zlZR
> =HBn9
> -----END PGP SIGNATURE-----
>



-- 
Aaron Peeler
Program Manager
Virtual Computing Lab
NC State University

All electronic mail messages in connection with State business which
are sent to or received by this account are subject to the NC Public
Records Law and may be disclosed to third parties.

Re: [VOTE] release 2.4 (RC3)

[Aaron Coburn <ac...@amherst.edu>]

+1 

Aaron Coburn


> On Mar 13, 2015, at 4:11 PM, Josh Thompson <jo...@ncsu.edu> wrote:
> 
> Signed PGP part
> The issues identified in RC2 plus a few minor items have been fixed.  RC3 is
> now available for testing and voting upon.  Again, basically the same email
> with the voting deadline changed.
> 
> As Andy mentioned in his reply to the "release nearly ready" thread, all of
> the (non-documentation) JIRA issues associated with 2.4 are now resolved.
> Here is our first try at voting to release 2.4.
> 
> I created a release artifact based off of trunk.  I copied that branch to a
> tag under the tags area of the repo that is named release-2.4-RC3:
> 
> http://svn.apache.org/repos/asf/vcl/tags/release-2.4-RC3/
> 
> The artifact is an export from that tag with the addition of Dojo Toolkit
> version 1.6.2 with a custom VCL profile and Spyc both 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.4-RC3/
> 
> The list of resolved JIRA issues associated with this release can be found
> under 2.4 on the Change Log page in the staging area of the CMS:
> 
> http://vcl.staging.apache.org/docs/changelog.html
> 
> This is the first release to include an installation script.  Installation
> instructions on using the script and doing things manually are on the
> following page in the staging area of the CMS:
> 
> http://vcl.staging.apache.org/docs/VCL24InstallGuide.html
> 
> The INSTALLATION file in the release artifact only contains information on
> using the script.
> 
> *NOTE* To use the installation script with RC3, you need to give it the
> --rc=1 option (which is not included in the output of --help).
> 
> I was able to successfully do test installs and upgrades, including image
> deploying and capture.
> 
> The directory created by extracting the RC3 artifact is "apache-VCL-2.4-RC3"
> (after extracting, you may want to rename it to "apache-VCL-2.4" if you want
> to test the manual instruction from the online installation guide).  Licensing
> information about perl and its required modules, php and its required modules,
> and mysql are stated as "system requirements" according to the information
> under "System Requirements" on http://www.apache.org/legal/3party.html.
> 
> After we finalize a release vote, the staging part of the CMS will be
> published to update the production site.
> 
> Please vote by 5pm (EST) on Tuesday, March 17th to publish this release.
> Everyone in the community is encouraged to vote if you have at least done some
> testing.  However, only votes by members of the PMC are binding votes.
> 
> [ ] +1 yes, release VCL 2.4
> [ ] 0 dunno
> [ ] -1 no, don't release VCL 2.4 (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.
> 
> 

Re: [VOTE] release 2.4 (RC3)

[Josh Thompson <jo...@ncsu.edu>]

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

I'll go ahead and put my vote in early this time.

+1 yes, release VCL 2.4

Josh

On Friday, March 13, 2015 4:11:56 PM you wrote:
> The issues identified in RC2 plus a few minor items have been fixed.  RC3 is
> now available for testing and voting upon.  Again, basically the same email
> with the voting deadline changed.
> 
> As Andy mentioned in his reply to the "release nearly ready" thread, all of
> the (non-documentation) JIRA issues associated with 2.4 are now resolved.
> Here is our first try at voting to release 2.4.
> 
> I created a release artifact based off of trunk.  I copied that branch to a
> tag under the tags area of the repo that is named release-2.4-RC3:
> 
> http://svn.apache.org/repos/asf/vcl/tags/release-2.4-RC3/
> 
> The artifact is an export from that tag with the addition of Dojo Toolkit
> version 1.6.2 with a custom VCL profile and Spyc both 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.4-RC3/
> 
> The list of resolved JIRA issues associated with this release can be found
> under 2.4 on the Change Log page in the staging area of the CMS:
> 
> http://vcl.staging.apache.org/docs/changelog.html
> 
> This is the first release to include an installation script.  Installation
> instructions on using the script and doing things manually are on the
> following page in the staging area of the CMS:
> 
> http://vcl.staging.apache.org/docs/VCL24InstallGuide.html
> 
> The INSTALLATION file in the release artifact only contains information on
> using the script.
> 
> *NOTE* To use the installation script with RC3, you need to give it the
> --rc=1 option (which is not included in the output of --help).
> 
> I was able to successfully do test installs and upgrades, including image
> deploying and capture.
> 
> The directory created by extracting the RC3 artifact is "apache-VCL-2.4-RC3"
> (after extracting, you may want to rename it to "apache-VCL-2.4" if you
> want to test the manual instruction from the online installation guide). 
> Licensing information about perl and its required modules, php and its
> required modules, and mysql are stated as "system requirements" according
> to the information under "System Requirements" on
> http://www.apache.org/legal/3party.html.
> 
> After we finalize a release vote, the staging part of the CMS will be
> published to update the production site.
> 
> Please vote by 5pm (EST) on Tuesday, March 17th to publish this release.
> Everyone in the community is encouraged to vote if you have at least done
> some testing.  However, only votes by members of the PMC are binding votes.
> 
> [ ] +1 yes, release VCL 2.4
> [ ] 0 dunno
> [ ] -1 no, don't release VCL 2.4 (provide reasons if this is your vote)
> 
> Josh
> --
> -------------------------------
> Josh Thompson
> VCL Developer
> North Carolina State University
> 
> my GPG/PGP key can be found at pgp.mit.edu
> 
> All electronic mail messages in connection with State business which
> are sent to or received by this account are subject to the NC Public
> Records Law and may be disclosed to third parties.
- -- 
- -------------------------------
Josh Thompson
VCL Developer
North Carolina State University

my GPG/PGP key can be found at pgp.mit.edu

All electronic mail messages in connection with State business which
are sent to or received by this account are subject to the NC Public
Records Law and may be disclosed to third parties.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iEYEARECAAYFAlUDRXQACgkQV/LQcNdtPQOGKQCePPurvgPdd/LAMUKKZuAGp0YC
pb4AnRFg21+XmCJIiO9uOu42oPm9TDsf
=Pbqu
-----END PGP SIGNATURE-----

Re: [VOTE] release 2.4 (RC3)

[Andy Kurth <an...@ncsu.edu>]

+1
-Andy

On Fri, Mar 13, 2015 at 4:11 PM, Josh Thompson <jo...@ncsu.edu>
wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> The issues identified in RC2 plus a few minor items have been fixed.  RC3
> is
> now available for testing and voting upon.  Again, basically the same email
> with the voting deadline changed.
>
> As Andy mentioned in his reply to the "release nearly ready" thread, all of
> the (non-documentation) JIRA issues associated with 2.4 are now resolved.
> Here is our first try at voting to release 2.4.
>
> I created a release artifact based off of trunk.  I copied that branch to a
> tag under the tags area of the repo that is named release-2.4-RC3:
>
> http://svn.apache.org/repos/asf/vcl/tags/release-2.4-RC3/
>
> The artifact is an export from that tag with the addition of Dojo Toolkit
> version 1.6.2 with a custom VCL profile and Spyc both 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.4-RC3/
>
> The list of resolved JIRA issues associated with this release can be found
> under 2.4 on the Change Log page in the staging area of the CMS:
>
> http://vcl.staging.apache.org/docs/changelog.html
>
> This is the first release to include an installation script.  Installation
> instructions on using the script and doing things manually are on the
> following page in the staging area of the CMS:
>
> http://vcl.staging.apache.org/docs/VCL24InstallGuide.html
>
> The INSTALLATION file in the release artifact only contains information on
> using the script.
>
> *NOTE* To use the installation script with RC3, you need to give it the
> - --rc=1 option (which is not included in the output of --help).
>
> I was able to successfully do test installs and upgrades, including image
> deploying and capture.
>
> The directory created by extracting the RC3 artifact is
> "apache-VCL-2.4-RC3"
> (after extracting, you may want to rename it to "apache-VCL-2.4" if you
> want
> to test the manual instruction from the online installation guide).
> Licensing
> information about perl and its required modules, php and its required
> modules,
> and mysql are stated as "system requirements" according to the information
> under "System Requirements" on http://www.apache.org/legal/3party.html.
>
> After we finalize a release vote, the staging part of the CMS will be
> published to update the production site.
>
> Please vote by 5pm (EST) on Tuesday, March 17th to publish this release.
> Everyone in the community is encouraged to vote if you have at least done
> some
> testing.  However, only votes by members of the PMC are binding votes.
>
> [ ] +1 yes, release VCL 2.4
> [ ] 0 dunno
> [ ] -1 no, don't release VCL 2.4 (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
>
> iEYEARECAAYFAlUDRJEACgkQV/LQcNdtPQNoaQCfXFvaia5zrXMgXInZ0HjShY9e
> JrUAniNVC/Qwnc16uXZkhXw2DMA0zlZR
> =HBn9
> -----END PGP SIGNATURE-----
>
>

Re: [VOTE] release 2.4 (RC3)

[Dmitri Chebotarov <dc...@gmu.edu>]

+1


--
Thank you,

Dmitri Chebotarov
VCL Sys Eng, Engineering & Architectural Support, TSD - Ent Servers & Messaging
223 Aquia Building, Ffx, MSN: 1B5
Phone: (703) 993-6175 | Fax: (703) 993-3404


> On Mar 13, 2015, at 16:11 , Josh Thompson <jo...@ncsu.edu> wrote:
> 
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> The issues identified in RC2 plus a few minor items have been fixed.  RC3 is 
> now available for testing and voting upon.  Again, basically the same email 
> with the voting deadline changed.
> 
> As Andy mentioned in his reply to the "release nearly ready" thread, all of
> the (non-documentation) JIRA issues associated with 2.4 are now resolved.
> Here is our first try at voting to release 2.4.
> 
> I created a release artifact based off of trunk.  I copied that branch to a
> tag under the tags area of the repo that is named release-2.4-RC3:
> 
> http://svn.apache.org/repos/asf/vcl/tags/release-2.4-RC3/
> 
> The artifact is an export from that tag with the addition of Dojo Toolkit
> version 1.6.2 with a custom VCL profile and Spyc both 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.4-RC3/
> 
> The list of resolved JIRA issues associated with this release can be found
> under 2.4 on the Change Log page in the staging area of the CMS:
> 
> http://vcl.staging.apache.org/docs/changelog.html
> 
> This is the first release to include an installation script.  Installation
> instructions on using the script and doing things manually are on the
> following page in the staging area of the CMS:
> 
> http://vcl.staging.apache.org/docs/VCL24InstallGuide.html
> 
> The INSTALLATION file in the release artifact only contains information on
> using the script.
> 
> *NOTE* To use the installation script with RC3, you need to give it the
> - --rc=1 option (which is not included in the output of --help).
> 
> I was able to successfully do test installs and upgrades, including image
> deploying and capture.
> 
> The directory created by extracting the RC3 artifact is "apache-VCL-2.4-RC3"
> (after extracting, you may want to rename it to "apache-VCL-2.4" if you want
> to test the manual instruction from the online installation guide).  Licensing
> information about perl and its required modules, php and its required modules,
> and mysql are stated as "system requirements" according to the information
> under "System Requirements" on http://www.apache.org/legal/3party.html.
> 
> After we finalize a release vote, the staging part of the CMS will be
> published to update the production site.
> 
> Please vote by 5pm (EST) on Tuesday, March 17th to publish this release.  
> Everyone in the community is encouraged to vote if you have at least done some 
> testing.  However, only votes by members of the PMC are binding votes.
> 
> [ ] +1 yes, release VCL 2.4
> [ ] 0 dunno
> [ ] -1 no, don't release VCL 2.4 (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
> 
> iEYEARECAAYFAlUDRJEACgkQV/LQcNdtPQNoaQCfXFvaia5zrXMgXInZ0HjShY9e
> JrUAniNVC/Qwnc16uXZkhXw2DMA0zlZR
> =HBn9
> -----END PGP SIGNATURE-----
>