Fantastic! Thanks Kevin.

Still hoping to hear from John and Noah!

-chip

On Fri, Oct 26, 2012 at 3:52 PM, Kevin Kluge <kevin.kl...@citrix.com> wrote:
> +1 (binding)
>
> CentOS 6.2 for MS + XS 6.0.2 and NFS for primary.
>
> The docs are vastly improved from what I saw in the last vote round.  I have 
> a few nits but will just file them as bugs.
>
> -kevin
>
>
>> -----Original Message-----
>> From: Chip Childers [mailto:chip.child...@sungard.com]
>> Sent: Thursday, October 25, 2012 8:42 AM
>> To: cloudstack-dev@incubator.apache.org; Edison Su; Will Chan; Kevin Kluge;
>> John Kinsella; nsla...@apache.org
>> Subject: Re: [VOTE] Apache Cloudstack 4.0.0-incubating Release, third round
>>
>> Hi all,
>>
>> Thanks again to everyone that has tested and voted!
>>
>> It looks like we have all of the required votes at this point, but I'm going 
>> to hold
>> the vote thread open until I see more of the PPMC members vote.  
>> Specifically,
>> I'd like to see Edison, Will, Kevin, John and hopefully Noah.
>>
>> If I can at least get 4 of the 5 folks to vote, I'll close it out.
>> Ideally, we would close it out today...
>>
>> -chip
>>
>> On Tue, Oct 23, 2012 at 5:18 PM, Chip Childers <chip.child...@sungard.com>
>> wrote:
>> > On Mon, Oct 22, 2012 at 12:16 PM, Chip Childers (ASF)
>> > <chipchild...@apache.org> wrote:
>> >> Hi All,
>> >>
>> >> I would like to call a vote for Apache CloudStack (Incubating)
>> >> Release 4.0.0-incubating (third round).
>> >>
>> >> We encourage the whole community to download and test these release
>> >> artifacts, so that any critical issues can be resolved before the
>> >> release is made. The more time that each individual spends reviewing
>> >> the artifacts, the higher confidence we can have in both the release
>> >> itself and our ability to pass an IPMC vote later on.  Everyone is
>> >> free to vote on this release, so please give it a shot.
>> >>
>> >> Instructions for Validating and Testing the artifacts can be found here:
>> >> https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+4.0
>> >> +test+procedure
>> >>
>> >> If you have any trouble setting up a test environment using the
>> >> procedure above, please ask on the cloudstack-dev@i.a.o list.
>> >> Someone will be sure to help, and we'll improve our test procedure
>> >> documentation at the same time!
>> >>
>> >> Now, on to the specifics of what we are voting on...
>> >>
>> >>
>> >> The following artifacts are up for the vote:
>> >> http://people.apache.org/~chipchilders/dist/cloudstack/releases/4.0.0
>> >> -incubating/
>> >>
>> >> PGP release keys (signed using A99A5D58):
>> >> http://people.apache.org/~chipchilders/dist/cloudstack/KEYS
>> >>
>> >> Branch: 4.0
>> >> Commit: 6355965dcd956811dd471a9d03c73dadcf68f480
>> >>
>> >>
>> >> List of changes:
>> >> https://git-wip-us.apache.org/repos/asf?p=incubator-cloudstack.git;a=
>> >> blob_plain;f=CHANGES;hb=refs/heads/4.0
>> >>
>> >> The artifacts being voted on during this round also include the
>> >> following additional fixes (most were identified as part of testing
>> >> during the last round of voting):
>> >>
>> >> * Many documentation fixes (particularly the release notes and
>> >> installation guide)
>> >> * CLOUDSTACK-341: Failing to display Management Traffic Details on
>> >> the UI
>> >> * CLOUDSTACK-349: Russian l10n not properly displaying
>> >> * Correction to the devcloud rdeploy build target, to make testing
>> >> easier
>> >> * CLOUDSTACK-363: Upgrades from 2.2.14, 3.0.2 to the Current build
>> >> will fail
>> >> * CLOUDSTACK-118: Status of host resorce stuck in "ErrorInMaintenance"
>> >> * DISCLAIMER added to the Marvin tool dir
>> >>
>> >>
>> >> The vote will be open for 72 hours.
>> >>
>> >>
>> >> For sanity in tallying the vote, can PPMC and IPMC members please be
>> >> sure to indicate "(binding)" with their vote?
>> >> [ ] +1  approve
>> >> [ ] +0  no opinion
>> >> [ ] -1  disapprove (and reason why)
>> >>
>> >> Thanks!
>> >
>> > Hi all,
>> >
>> > 1 day down, and we have 2 +1 votes so far.  Please take an opportunity
>> > to test and cast your vote!
>> >
>> > -chip
>

Reply via email to