+1

Building kit from source code OK
Running samples OK

2018-03-22 10:51 GMT+08:00 Eric Lee <eric.lee....@gmail.com>:

> +1
>
> All samples in the kit are passed.
>
> 2018-03-22 10:43 GMT+08:00 kirin wang <wangqilint...@gmail.com>:
>
> > +1
> > LGTM
> >
> > 2018-03-22 10:42 GMT+08:00 郑扬勇 <yangyong.zh...@qq.com>:
> >
> > > +1 Non Binding
> > >
> > >  Signatures and headers are good.
> > >  Built the code from Release Candidate then check all samples using
> > > Staging Repo.
> > >  Run unit tests and integration tests,all passed.
> > >
> > >
> > >
> > >
> > >  ------------------ Original ------------------
> > >   From:  "Mohammad Asif Siddiqui"<asifdxtr...@apache.org>;
> > >  Date:  Tue, Mar 20, 2018 02:13 PM
> > >  To:  "dev"<dev@servicecomb.apache.org>;
> > >
> > >  Subject:  [VOTE] Release Apache ServiceComb Java-Chassis (incubating)
> > > version 1.0.0-m1 - Third Attempt
> > >
> > >
> > >
> > > Hi All,
> > >
> > > This is a call for Vote to release Apache ServiceComb Java-Chassis
> > > (Incubating) version 1.0.0-m1
> > >
> > > Release Notes : https://github.com/apache/incubator-servicecomb-java-
> > > chassis/blob/master/etc/releaseNotes.md
> > >
> > > Release Candidate : https://dist.apache.org/repos/dist/dev/incubator/
> > > servicecomb/incubator-servicecomb-java-chassis/1.0.0-m1/
> > >
> > > Staging Repo : https://repository.apache.org/content/repositories/
> > > orgapacheservicecomb-1196
> > >
> > > Release Tag : https://github.com/apache/incubator-servicecomb-java-
> > > chassis/releases/tag/1.0.0-m1
> > >
> > > Release CommitID : 901869b987c6f65c92b5b8b8f05eaf0f9f6e69cb
> > >
> > > 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, Request all PPMC members to give their vote.
> > >
> > > [ ] +1 Release this package as 1.0.0-m1
> > > [ ] +0 No Opinion
> > > [ ] -1 Do not release this package because....
> > >
> > > Regards
> > > Asif
> > >
> >
>

Reply via email to