> We’ve received 3 +1 binding votes and one +1 non-binding vote:
> 
> +1 binding, Ian Luo
> +1 binding, Huxing Zhang
> +1 binding, Jun Liu
> +1 non-binding, Jerrick

72+ hours has passed, the votes are as listed before above. Let me bring it to 
the Apache community.

Best regards,
Jun

> On 1 Sep 2018, at 10:19, Jun Liu <[email protected]> wrote:
> 
> We’ve received 3 +1 binding votes and one +1 non-binding vote:
> 
> +1 binding, Ian Luo
> +1 binding, Huxing Zhang
> +1 binding, Jun Liu
> +1 non-binding, Jerrick
> 
> I will create a new vote thread in Apache community now.
> 
> Best regards,
> Jun
> 
>> On 29 Aug 2018, at 13:14, Jun Liu <[email protected]> wrote:
>> 
>> Hello Dubbo Community,
>> 
>> This is a call for vote to release Apache Dubbo (Incubating) version 2.6.3.
>> 
>> The release candidates (RC5):
>> https://dist.apache.org/repos/dist/dev/incubator/dubbo/2.6.3
>> 
>> Git tag for the release (RC5):
>> https://github.com/apache/incubator-dubbo/tree/dubbo-2.6.3 
>> Hash for the release tag:
>> 3963d8fd93642398375ea92acb7ed4d2bc1b0518
>> 
>> Release Notes:
>> https://github.com/apache/incubator-dubbo/blob/dubbo-2.6.3/CHANGES.md
>> 
>> The artifacts have been signed with Key : 28681CB1, which can be found in 
>> the keys file:
>> https://dist.apache.org/repos/dist/dev/incubator/dubbo/KEYS
>> 
>> The vote will be open for at least 72 hours or until necessary number of 
>> votes are reached.
>> 
>> Please vote accordingly:
>> 
>> [ ] +1 approve 
>> [ ] +0 no opinion 
>> [ ] -1 disapprove with the reason
>> 
>> Notice: no changes in code level of release candidate has changed compared 
>> to RC4, only remove two useless signature files in distribution/ directory.
>> 
>> The previously RC4 vote thread:
>> https://lists.apache.org/thread.html/1714c7aa24bc7b8bf6f6c12a52e2ac79172beddf24d9f33cf6ccfe67@%3Cdev.dubbo.apache.org%3E
>> The previously RC3 vote thread:
>> https://lists.apache.org/thread.html/44a55f1a981b7ec4e766531b586ed9def5d7940892d8fb7a7f72d1c9@%3Cgeneral.incubator.apache.org%3E
>> 
>> Jun 
>> Best Regards
>> 
> 

Reply via email to