Hi

 +1 (binding)

Here are the checks I did:

Checked the signed Keys and checksum.
Checked the binary with the examples.
Run the rat to verify the License header issue.
DISCLAIMER exists
Verify the nexus Staging repo by running the demo example
Compiled from source
Checked for archive matching git tag



Willem Jiang

Blog: http://willemjiang.blogspot.com (English)
          http://jnn.iteye.com  (Chinese)
Twitter: willemjiang
Weibo: 姜宁willem

On Tue, Mar 20, 2018 at 12:41 PM, Mohammad Asif Siddiqui <
[email protected]> wrote:

> Hello All,
>
> This is a call for vote to release Apache ServiceComb Saga (Incubating)
> version 0.1.0
>
> Apache ServiceComb (Incubating) Community has voted and approved the
> release.
>
> Vote Thread : https://lists.apache.org/thread.html/
> 46b2a639306ed5260f1aec5a3749eeb9112cc666069842e8aad1862d@%
> 3Cdev.servicecomb.apache.org%3E
>
> Result Thread : https://lists.apache.org/thread.html/
> 1b60c2a2542b9a3358e16b8960c4f925fc7b3c25bc382771b97c5567@%
> 3Cdev.servicecomb.apache.org%3E
>
> Release Notes : https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> projectId=12321626&version=12342353
>
> Release Candidate : https://dist.apache.org/repos/dist/dev/incubator/
> servicecomb/incubator-servicecomb-saga/0.1.0/
>
> Staging Repo : https://repository.apache.org/content/repositories/
> orgapacheservicecomb-1166
>
> Release Tag : https://github.com/apache/incubator-servicecomb-saga/
> releases/tag/0.1.0
>
> Release CommitID : 708eec092988dfd4a5960ca5f232fb7421d5fbdd
>
> Keys to verify the Release Candidate : https://dist.apache.org/repos/
> dist/dev/incubator/servicecomb/KEYS
>
> Voting will start now ( Tuesday, 20th March, 2018) and will remain open
> for next 72 hours, We request all IPMC members to give their vote.
>
> [ ] +1 Release this package as 0.1.0
> [ ] +0 No Opinion
> [ ] -1 Do not release this package because....
>
> Regards
> Asif
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>

Reply via email to