The vote has *passed* with the following results (binding PMC votes
indicated with a "*" next to their name:

+1 : Edison*, Hugo*, Marcus*, David*, Wido*, Ilya, Animesh, Milamber,
     Joe*, Simon, Prasanna*
-0 : John
-1 : Ove

I'm going to proceed with moving the release into the distribution repo
now, and will do the DEB / RPM builds to push Wido's repo site / push
cloudmonkey to pypi on Monday.

I do note Ove's -1, due to upstream Tomcat changes.  I know Prasanna
mentioned that he was going to check with that project to see why the
change happened.  We will need to discuss what (if anything) this
project should do to resolve the issue for users.  This issue will block
users of all prior versions as well, so it's nothing *in* our code that
causes the bug.  This is my logic for not cancelling the vote.

-chip

On Tue, May 28, 2013 at 09:47:40AM -0400, Chip Childers wrote:
> Hi All,
> 
> I've created a 4.1.0 release, with the following artifacts up for a
> vote.
> 
> The changes from round 4 are related to DEB packaging, some 
> translation strings, and a functional patch to make bridge type 
> optional during the agent setup (for backward compatibility).
> 
> Git Branch and Commit SH:
> https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=refs/heads/4.1
> Commit: a5214bee99f6c5582d755c9499f7d99fd7b5b701
> 
> List of changes:
> https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=blob_plain;f=CHANGES;hb=4.1
> 
> Source release (checksums and signatures are available at the same
> location):
> https://dist.apache.org/repos/dist/dev/cloudstack/4.1.0/
> 
> PGP release keys (signed using A99A5D58):
> https://dist.apache.org/repos/dist/release/cloudstack/KEYS
> 
> Testing instructions are here:
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Release+test+procedure
> 
> Vote will be open for 72 hours.
> 
> 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