I forgot to rename the thread so for archive purposes, this.

On Mon, Jan 4, 2021 at 11:18 AM Daan Hoogland <daan.hoogl...@gmail.com>
wrote:

> Hi all,
>
> After 72 hours (+the holidays), the vote for CloudStack 4.15.0.0 *passes* with
> 4 PMC + 1 non-PMC votes.
>
> +1 (PMC / binding)
> * Wei, Boris, Rohit, Gabriel
>
> +1 (non binding)
> * Abhishek
>
> 0
> none
>
> -1
> none
>
> Thanks to everyone participating.
>
> I will now prepare the release announcement to go out after 24 hours to give 
> the mirrors time to catch up.
>
>
> On Wed, Dec 23, 2020 at 5:43 PM Daan Hoogland <daan.hoogl...@gmail.com>
> wrote:
>
>> LS,
>> After fixing another few blockers, we have an RC3, The changes (other
>> than bundling) are mostly interesting for those working with templates and
>> on vmware.
>>
>> We are voting for the new UI and the main code.
>>
>> The candidate release branch is 4.15.0.0-RC20201223T1632. The UI is still
>> separate but as agreed upon before this will be merged in coming releases,
>> at least from a version management point of view.
>> I've created a 4.15.0.0 release candidate, with the following artifacts
>> up for a vote:Git Branches:
>> main code:
>> https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=refs/heads/4.15.0.0-RC20201223T1632
>> <https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=refs/heads/4.15.0.0-RC20201214T1124>
>> ui code:
>> <https://git-wip-us.apache.org/repos/asf?p=cloudstack-primate.git;a=shortlog;h=refs/tags/1.0>
>> https://git-wip-us.apache.org/repos/asf?p=cloudstack-primate.git;a=tag;h=refs/tags/1.0
>> and Commit SH:
>> main code: 01b3e361c7bb81fd1ea822faddd6594e52bb00c1
>> ui code: 0593302dd53ac3203d3ab43b62d890605910f3e1
>>
>> Source release (checksums and signatures are available at the same
>> location):
>> https://dist.apache.org/repos/dist/dev/cloudstack/4.15.0.0/ (rev. 45059)
>> PGP release keys (signed using 7975062401944786):
>> https://dist.apache.org/repos/dist/release/cloudstack/KEYSVote will be
>> open for (at least) 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)
>>
>> I will work with community members to provide convenience packaging over
>> the next few days.
>> The documentation repo will be updated as we move along.
>>
>>
>>
>> --
>> Daan
>>
>
>
> --
> Daan
>


-- 
Daan

Reply via email to