H,

We've started running our custom 4.2.1 build 24 hours ago on our internal 
projects/employees system. The build is based on the last fix by Kishan's fix 
for CLOUDSTACK-5145. The environment is a hybrid xen/vmware environment with 
nicira networking and nexenta storage.

No issues have come up so far so:
+1 (binding)

I have done a rebase on the specified commit with a smoke test in a dev-env and 
am satisfied with it.

Regards,
Daan

-----Original Message-----
From: Srikanteswararao Talluri [mailto:srikanteswararao.tall...@citrix.com] 
Sent: woensdag 18 december 2013 9:37
To: dev@cloudstack.apache.org
Subject: Re: [VOTE] 3rd round of voting for ASF 4.2.1 RC

+1

~Talluri

On 18/12/13 10:57 am, "Sailaja Mada" <sailaja.m...@citrix.com> wrote:

>+1
>
>Validated from the specified commit id.
>
>Thanks,
>Sailaja.M
>
>-----Original Message-----
>From: Abhinandan Prateek [mailto:abhinandan.prat...@citrix.com]
>Sent: 17 December 2013 19:19
>To: CloudStack Dev
>Subject: [VOTE] 3rd round of voting for ASF 4.2.1 RC
>
>The 4.2.1 is re-spun mainly because the commit that was used to 
>generate the previous RC did not get pushed to repo.
>
>Following are the particulars to vote for this time around:
>
>https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=r
>efs
>/heads/4.2
>commit: 1b2b58fe352a19aee1721bd79b9d023d36e80ec5
>
>List of changes are available in Release Notes, a summary can be 
>accessed
>here:
>https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=blob_plain;f
>=CH
>ANGES;hb=4.2
>
>Source release revision 3911 (checksums and signatures are available at 
>the same location):
>https://dist.apache.org/repos/dist/dev/cloudstack/4.2.1/
>
>PGP release keys (signed using RSA Key ID = 42443AA1):
>https://dist.apache.org/repos/dist/release/cloudstack/KEYS
>
>Vote will be open for 72 hours (until 20 Dec 2013 End of day PST).
>
>For sanity in tallying the vote, can PMC members please be sure to 
>indicate "(binding)" with their vote?
>
>[ ] +1  approve
>[ ] +0  no opinion
>[ ] -1  disapprove (and reason why)
>

Reply via email to