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 <[email protected]> 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 <[email protected]> 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 <[email protected]> > > 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----- > >
