Re: [ANN] New ServiceComb committer: Zhu Chen(陈铸)

[Bin Ma]

Welcome! @ZhuChen


Wishes & Regards
---
Mabin



zhongyuan zhou  于2020年5月29日周五 下午3:36写道：

> Congratulations!!!
>
> sen sun  于2020年5月29日周五 下午12:28写道：
>
> > Congratulations!!! Welcome!!!
> >
> > On Fri, May 29, 2020, 11:05 AM victor chan 
> > wrote:
> >
> > >  Hi all,
> > >
> > > It is an honour to join the Apache ServiceComb community.
> > > I have benefited a lot and thanks for your help, in the past year.
> > > I hope to witness the further growth of ServiceComb with you.
> > >
> > > Wishes & Regards
> > > ---
> > > ZhuChen
> > >
> > >
> > > Willem Jiang  于2020年5月28日周四 下午6:19写道：
> > >
> > > > Welcome aboard Zhu Chen, looking forward to working with you on
> > > > ServiceComb projects.
> > > >
> > > > Willem Jiang
> > > >
> > > > Twitter: willemjiang
> > > > Weibo: 姜宁willem
> > > >
> > > > On Thu, May 28, 2020 at 2:44 PM Zen Lin  >
> > > > wrote:
> > > > >
> > > > > Please join me and the rest of the ServiceComb PMC members in
> > welcoming
> > > > our
> > > > > new ServiceComb committer: Zhu Chen(陈铸).
> > > > >
> > > > > Zhu Chen has been around the ServiceComb almost a year by
> > > > > contributing patches for servicecomb-service-center,
> > > > > servicecomb-mesher, servicecomb-website and
> > > > > discussion techniques issue in the mailing list. Recently
> > > > > he contributed key features such as Syncer and SC-Client to
> > > > > servicecomb-service-center and commit on it frequently.
> > > > >
> > > > > Congratulations to  Zhu Chen ! Welcome!
> > > > >
> > > > > The Apache ServiceComb PMC.
> > > >
> > >
> >
>

Re: [VOTE] Release Apache ServiceComb Toolkit version 0.2.0 [RC2]

[Bin Ma]

+1 binding

I checked:
1. all issues for toolkit 0.2.0 are closed
2. all the links above are fine.
3. git tag and commit id are OK.
4. hashes and signature are good.
5. license and Notice exist
6. mvn clean install build OK.
7. toolkit-maven-plugin running is OK.


Wishes & Regards
---
Mabin



Liubao (A)  于2020年1月2日周四 下午8:24写道：

> +1
>
> I checked the release binaries and release notes, seems good to me.
>
> Bug I got one small improvement for artifacts deployed by toolkit. May of
> the artifacts have very general name and may cause conflicts easily. e.g.
> toolkit*jar, core*jar, common*jar. Although the have unit group id, java
> packagers will put them all in one flat folder.
>
> -邮件原件-
> 发件人: sen sun [mailto:asd992825...@gmail.com]
> 发送时间: 2019年12月31日 18:18
> 收件人: dev@servicecomb.apache.org
> 主题: [VOTE] Release Apache ServiceComb Toolkit version 0.2.0 [RC2]
>
> Hi All,
>
> This is a call for Vote to release Apache ServiceComb Toolkit version 0.2.0
>
>
> Release Candidate :
>
> https://dist.apache.org/repos/dist/dev/servicecomb/servicecomb-toolkit/0.2.0/rc-02/
>
> Staging Repository :
>
> https://repository.apache.org/content/repositories/orgapacheservicecomb-1411
>
> Release Tag :
> https://github.com/apache/servicecomb-toolkit/releases/tag/0.2.0
>
> Release CommitID : da3b3b6333e1c776d4e39513e39e328596d9b40f
>
> Release Notes :
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12321626=12346158
>
> Keys to verify the Release Candidate :
> https://dist.apache.org/repos/dist/dev/servicecomb/KEYS
>
> Voting will start now ( Tuesday, 31nd Dec, 2019) and will remain open for
> at-least 72 hours, Request all PMC members to give their vote.
>
> [ ] +1 Release this package as 0.2.0
> [ ] +0 No Opinion
> [ ] -1 Do not release this package because
>
> On the behalf of ServiceComb Team
>
> Best Wishes & Regards
>

[ANN] New ServiceComb committer:Sun Lisen(孙丽森)

[Bin Ma]

Please join me and the rest of the ServiceComb PMC members in welcoming our
new ServiceComb committer: Sun Lisen(孙丽森).

Sun Lisen has been around the ServiceComb almost a year by
contributing patches for servicecomb-toolkit,
servicecomb-java-chassis,servicecomb-website and
discussion techniques issue in the mailing list. Recently
he contributed key features such as OAIV3 and SpringCloud to
servicecomb-toolkit and commit on it frequently.

Congratulations to Sun Lisen! Welcome!

The Apache ServiceComb PMC.

Re: [VOTE] Release Apache ServiceComb Toolkit version 0.2.0

[Bin Ma]

OK, Thanks @Willem

This vote would be canceled.
We will start a new vote after the issues is fixed.



Wishes & Regards
---
Mabin



Willem Jiang  于2019年12月11日周三 下午7:41写道：

> -1. (binding)
> I can build the kit on mac OSX.
> I just found there are lots of jars which are listed in the License
> file in the binary release kit.
> Such as netty, vertx and zipkin.
> I don't think toolkit need to use this jar to run.
> Please double check the release kit about it.
>
> Willem Jiang
>
> Twitter: willemjiang
> Weibo: 姜宁willem
> On Fri, Dec 6, 2019 at 9:09 AM Bin Ma  wrote:
> >
> > Hi All,
> >
> > This is a call for Vote to release Apache ServiceComb Toolkit version
> 0.2.0
> >
> >
> > Release Candidate :
> >
> https://dist.apache.org/repos/dist/dev/servicecomb/servicecomb-toolkit/0.2.0/rc-01/
> >
> > Staging Repository :
> >
> https://repository.apache.org/content/repositories/orgapacheservicecomb-1409
> >
> > Release Tag :
> > https://github.com/apache/servicecomb-toolkit/releases/tag/0.2.0
> >
> > Release CommitID : e95ba3c7b27673ee4e360d64cc1ccce43f70f18e
> >
> > Release Notes :
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12321626=12346158
> >
> > Keys to verify the Release Candidate :
> > https://dist.apache.org/repos/dist/dev/servicecomb/KEYS
> >
> > Voting will start now ( Friday, 6nd Dec, 2019) and will remain open for
> > at-least 72 hours, Request all PMC members to give their vote.
> >
> > [ ] +1 Release this package as 0.2.0
> > [ ] +0 No Opinion
> > [ ] -1 Do not release this package because
> >
> > On the behalf of ServiceComb Team
> >
> >
> > Wishes & Regards
> > ---
> > Mabin
>

Re: [VOTE] Release Apache ServiceComb Toolkit version 0.2.0

[Bin Ma]

The issues involve in the test code and CI, and do not affect
the functions of the binary and maven plugin.

I suggest to go on to vote 0.2.0, the issues[1] can be fixed
in the next version.

any thought?@PMCs

[1] https://issues.apache.org/jira/browse/SCB-1657

Wishes & Regards
---
Mabin



sen sun  于2019年12月10日周二 上午11:38写道：

> I have created the JIRA: https://issues.apache.org/jira/browse/SCB-1657
> Whether this issue affects the current release? Can we fix it in the next
> version?
>
> Willem Jiang  于2019年12月10日周二 上午10:38写道：
>
> > Please create a JIRA to check this issue.
> > We may consider to enable the Action in Github to running the CI with
> > windows.
> >
> > Willem Jiang
> >
> > Twitter: willemjiang
> > Weibo: 姜宁willem
> >
> > On Tue, Dec 10, 2019 at 9:46 AM sen sun  wrote:
> > >
> > > Hi, @yhs0092
> > >
> > > I have checked this unit test code.  It uses File.size to get the size
> of
> > > the directory.
> > > In Windows, it always returns zero and causes the assertion to fail
> > > In Linux, it is ok
> > > This is because their file systems are different and Files.size only
> > > guarantee the correctness of the file
> > >
> > > yhs0092  于2019年12月10日周二 上午12:16写道：
> > >
> > > > Hello, I find that the `mvn clean install` build is not OK in my
> > > > development environment. I use a Windows computer to run it.
> > > > Here is the error log:
> > > > ```
> > > > [INFO] Running org.apache.servicecomb.toolkit.cli.CliTest
> > > > [ERROR] Tests run: 6, Failures: 2, Errors: 0, Skipped: 0, Time
> elapsed:
> > > > 2.884 s <<< FAILURE! - in org.apache.servicecomb.toolkit.cli.CliTest
> > > > [ERROR]
> > > >
> >
> testGenerateServiceCombCodeFromSingleContract(org.apache.servicecomb.toolkit.cli.CliTest)
> > > > Time elapsed: 0.834 s  <<< FAILURE!
> > > > java.lang.AssertionError
> > > > at
> > > >
> >
> org.apache.servicecomb.toolkit.cli.CliTest.lambda$testGenerateServiceCombCodeFromSingleContract$0(CliTest.java:54)
> > > > at
> > > >
> >
> org.apache.servicecomb.toolkit.cli.CliTest.testGenerateServiceCombCodeFromSingleContract(CliTest.java:36)
> > > >
> > > >
> > > > [ERROR]
> > > >
> >
> testGenerateCodeFromMultiContract(org.apache.servicecomb.toolkit.cli.CliTest)
> > > > Time elapsed: 0.602 s  <<< FAILURE!
> > > > java.lang.AssertionError
> > > > at
> > > >
> >
> org.apache.servicecomb.toolkit.cli.CliTest.testGenerateCodeFromMultiContract(CliTest.java:89)
> > > >
> > > >
> > > > [INFO]
> > > > [INFO] Results:
> > > > [INFO]
> > > > [ERROR] Failures:
> > > > [ERROR]   CliTest.testGenerateCodeFromMultiContract:89
> > > > [ERROR]
> > > >
> >
> CliTest.testGenerateServiceCombCodeFromSingleContract:36->lambda$testGenerateServiceCombCodeFromSingleContract$0:54
> > > > [INFO]
> > > > [ERROR] Tests run: 6, Failures: 2, Errors: 0, Skipped: 0
> > > > ```
> > > >
> > > >
> > > > Yours sincerely
> > > >
> > > >
> > > > Yao Haishi
> > > > yhs0...@163.com
> > > >
> > > >
> > > > On 12/6/2019 09:09，Bin Ma wrote：
> > > > Hi All,
> > > >
> > > > This is a call for Vote to release Apache ServiceComb Toolkit version
> > 0.2.0
> > > >
> > > >
> > > > Release Candidate :
> > > >
> > > >
> >
> https://dist.apache.org/repos/dist/dev/servicecomb/servicecomb-toolkit/0.2.0/rc-01/
> > > >
> > > > Staging Repository :
> > > >
> > > >
> >
> https://repository.apache.org/content/repositories/orgapacheservicecomb-1409
> > > >
> > > > Release Tag :
> > > > https://github.com/apache/servicecomb-toolkit/releases/tag/0.2.0
> > > >
> > > > Release CommitID : e95ba3c7b27673ee4e360d64cc1ccce43f70f18e
> > > >
> > > > Release Notes :
> > > >
> > > >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12321626=12346158
> > > >
> > > > Keys to verify the Release Candidate :
> > > > https://dist.apache.org/repos/dist/dev/servicecomb/KEYS
> > > >
> > > > Voting will start now ( Friday, 6nd Dec, 2019) and will remain open
> for
> > > > at-least 72 hours, Request all PMC members to give their vote.
> > > >
> > > > [ ] +1 Release this package as 0.2.0
> > > > [ ] +0 No Opinion
> > > > [ ] -1 Do not release this package because
> > > >
> > > > On the behalf of ServiceComb Team
> > > >
> > > >
> > > > Wishes & Regards
> > > > ---
> > > > Mabin
> > > >
> >
>

[VOTE] Release Apache ServiceComb Toolkit version 0.2.0

[Bin Ma]

Hi All,

This is a call for Vote to release Apache ServiceComb Toolkit version 0.2.0


Release Candidate :
https://dist.apache.org/repos/dist/dev/servicecomb/servicecomb-toolkit/0.2.0/rc-01/

Staging Repository :
https://repository.apache.org/content/repositories/orgapacheservicecomb-1409

Release Tag :
https://github.com/apache/servicecomb-toolkit/releases/tag/0.2.0

Release CommitID : e95ba3c7b27673ee4e360d64cc1ccce43f70f18e

Release Notes :
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12321626=12346158

Keys to verify the Release Candidate :
https://dist.apache.org/repos/dist/dev/servicecomb/KEYS

Voting will start now ( Friday, 6nd Dec, 2019) and will remain open for
at-least 72 hours, Request all PMC members to give their vote.

[ ] +1 Release this package as 0.2.0
[ ] +0 No Opinion
[ ] -1 Do not release this package because

On the behalf of ServiceComb Team


Wishes & Regards
---
Mabin

Re: [DISCUSSION][Toolkit] Prepare to release 0.2.0

[Bin Ma]

Hi Daniel,

I will start an issue to describe them soon.


Daniel Qian  于 2019年11月27日周三 17:01写道：

> Hi Ma, would you like to point out which part doesn't match?
>
> Bin Ma  于2019年11月27日周三 下午2:53写道：
> >
> > I checked servicecomb-toolkit README[1] and found that it is not match
> with
> > the latest code.
> > I think we can start a vote for 0.2.0 release after the README is
> updated.
> >
> > [1]  <https://github.com/apache/servicecomb-toolkit>
> > https://github.com/apache/servicecomb-toolkit/blob/master/README.md
> >
> https://github.com/apache/servicecomb-toolkit/blob/master/README-ZH.md
> >
> >
> >
> > Wishes & Regards
> > ---
> > Mabin
> >
> >
> >
> >
> > Shuo Chen  于2019年11月26日周二 下午3:54写道：
> >
> > > +1 looking forward to  corresponding articles too
> > >
> > > Daniel Qian  于2019年11月26日周二 下午3:34写道：
> > >
> > > > +1 looking forward to toolkit 0.2.0
> > > >
> > > > sen sun  于2019年11月26日周二 上午11:16写道：
> > > > >
> > > > > Hi toolkit team,
> > > > >
> > > > > We have developed many new features, I think it's time to release
> 0.2.0
> > > > > Our new features are as follows:
> > > > >  * oas-validator for compliance check
> > > > >  * oas-validator for compatibility check
> > > > >  * new oas-generator for generating contract from code
> > > > >  * support openapi v3
> > > > >  * support generate springcloud microservice project
> > > > >  * etc ...  I may not list enough, I hope everyone can add what you
> > > know
> > > > >
> > > > > What do you think about releasing 0.2.0?
> > > > >
> > > > > If everyone agrees to release a new version, we may start to do
> some
> > > > work:
> > > > >  * make sure the license is ok
> > > > >  * make sure our features are complete
> > > > >  * make sure our tests are complete
> > > > >  * etc ... I may not list enough, I hope everyone can add what you
> know
> > > > >
> > > > > If not, maybe we need to discuss what needs to be done to get it to
> > > > release
> > > > >
> > > > >
> > > > > And I attach the information for reference. This is the roadmap
> for the
> > > > > previous community discussions：
> > > > >  *
> > > > >
> > > >
> > >
> https://lists.apache.org/thread.html/5048ca4aa778b13952cefcd32ec25be24eb38eb8424f24c80340183b@%3Cdev.servicecomb.apache.org%3E
> > > > >
> > > > > Any ideas are welcome
> > > >
> > > >
> > > >
> > > > --
> > > > Daniel Qian
> > > > Apache Committer(chanjarster)
> > > > blog：https://chanjarster.github.io
> > > > github：https://github.com/chanjarster
> > > > segmentfault: https://segmentfault.com/u/chanjarster
> > > >
> > >
>
>
>
> --
> Daniel Qian
> Apache Committer(chanjarster)
> blog：https://chanjarster.github.io
> github：https://github.com/chanjarster
> segmentfault: https://segmentfault.com/u/chanjarster
>

Re: [VOTE] Release Apache ServiceComb Service-Center version 1.3.0

[Bin Ma]

@Willem @Asif,

Is it time for us to finish this vote?


Wishes & Regards
---
Mabin



Bin Ma  于2019年11月6日周三 下午7:58写道：

> +1
>
> I used syncer binary[1] to do some test in my personal project[2]. The
> function of syncer is OK.
>
> [1]
> https://dist.apache.org/repos/dist/dev/servicecomb/servicecomb-service-center/1.3.0
>
> [2] https://github.com/MabinGo/servicecomb-toolkit-sample
>
>
> Wishes & Regards
> ---
> Mabin
>
>
>
>
> victor chan  于2019年11月5日周二 下午11:20写道：
>
>> @Willem Jiang
>> I will do it later.
>>
>> Willem Jiang  于2019年11月5日周二 下午7:10写道：
>>
>> > We need to do some functional test on the new added sync module.
>> > Please spend some time on it.
>> >
>> > Willem Jiang
>> >
>> > Twitter: willemjiang
>> > Weibo: 姜宁willem
>> >
>> > On Tue, Nov 5, 2019 at 6:41 PM Yihua Cui  wrote:
>> > >
>> > > +1 binding
>> > >
>> > > 1. signature verification is OK
>> > > 2. binary is OK
>> > > 3. ASF headers is OK
>> > >
>> > > On 2019/11/05 01:54:43, Willem Jiang  wrote:
>> > > > If the vote is not closed, we can still keep voting it.
>> > > > As Asif just update the artifacts without changing the release tag
>> we
>> > > > can still use the last vote thread.
>> > > >
>> > > > Let's verify the kit as soon as possible.
>> > > >
>> > > > Willem Jiang
>> > > >
>> > > > Twitter: willemjiang
>> > > > Weibo: 姜宁willem
>> > > >
>> > > > On Tue, Nov 5, 2019 at 1:06 AM Bin Ma  wrote:
>> > > > >
>> > > > > Hi Asif,
>> > > > >
>> > > > > Voting time has expired and no result,maybe we should
>> > > > > start a new voting for Service-Center version 1.3.0?
>> > > > >
>> > > > >
>> > > > > Wishes & Regards
>> > > > > ---
>> > > > > Mabin
>> > > > >
>> > > > >
>> > > > >
>> > > > > Liubao (A)  于2019年11月4日周一 下午4:14写道：
>> > > > >
>> > > > > > +1
>> > > > > >
>> > > > > > I have checked the release notes and binaries. Do some basic
>> tests
>> > with
>> > > > > > windows version.
>> > > > > >
>> > > > > > -邮件原件-
>> > > > > > 发件人: Mohammad Asif Siddiqui [mailto:asifdxtr...@apache.org]
>> > > > > > 发送时间: 2019年10月31日 22:06
>> > > > > > 收件人: dev@servicecomb.apache.org
>> > > > > > 主题: Re: [VOTE] Release Apache ServiceComb Service-Center version
>> > 1.3.0
>> > > > > >
>> > > > > > Hi All,
>> > > > > >
>> > > > > > I faced some network problem with my SVN client so the packages
>> > which were
>> > > > > > uploaded were outdated, I have uploaded the correct rc in the
>> svn
>> > now, hope
>> > > > > > we can go ahead with the voting now.
>> > > > > >
>> > > > > > Here is my +1 (Binding)
>> > > > > >
>> > > > > > Checks Done:
>> > > > > >  - verify hash and signature
>> > > > > >  - ran the test cases on linux
>> > > > > >  - check with RAT tool for ASF headers
>> > > > > >
>> > > > > > Regards
>> > > > > > Asif
>> > > > > >
>> > > > > > On 2019/10/30 01:17:21, victor chan 
>> > wrote:
>> > > > > > > Hi Asif，
>> > > > > > > gpg --verify also fails, the following is the error message,
>> > > > > > >
>> > > > > > > root@chenzhu:~/chan/release# gpg --verify
>> > > > > > > apache-servicecomb-service-center-1.3.0-src.zip.asc
>> > > > > > > apache-servicecomb-service-center-1.3.0-src.zip
>> > > > > > > gpg: Signature made Sun 27 Oct 2019 05:03:20 PM CST using RSA
>> > key ID
>> > > > > > > BD7A4D69
>> > > > > > > gpg: Good signature from "Mohammad Asif Siddiqui (ServiceComb

Re: [VOTE] Release Apache ServiceComb Service-Center version 1.3.0

[Bin Ma]

+1

I used syncer binary[1] to do some test in my personal project[2]. The
function of syncer is OK.

[1]
https://dist.apache.org/repos/dist/dev/servicecomb/servicecomb-service-center/1.3.0

[2] https://github.com/MabinGo/servicecomb-toolkit-sample


Wishes & Regards
---
Mabin




victor chan  于2019年11月5日周二 下午11:20写道：

> @Willem Jiang
> I will do it later.
>
> Willem Jiang  于2019年11月5日周二 下午7:10写道：
>
> > We need to do some functional test on the new added sync module.
> > Please spend some time on it.
> >
> > Willem Jiang
> >
> > Twitter: willemjiang
> > Weibo: 姜宁willem
> >
> > On Tue, Nov 5, 2019 at 6:41 PM Yihua Cui  wrote:
> > >
> > > +1 binding
> > >
> > > 1. signature verification is OK
> > > 2. binary is OK
> > > 3. ASF headers is OK
> > >
> > > On 2019/11/05 01:54:43, Willem Jiang  wrote:
> > > > If the vote is not closed, we can still keep voting it.
> > > > As Asif just update the artifacts without changing the release tag we
> > > > can still use the last vote thread.
> > > >
> > > > Let's verify the kit as soon as possible.
> > > >
> > > > Willem Jiang
> > > >
> > > > Twitter: willemjiang
> > > > Weibo: 姜宁willem
> > > >
> > > > On Tue, Nov 5, 2019 at 1:06 AM Bin Ma  wrote:
> > > > >
> > > > > Hi Asif,
> > > > >
> > > > > Voting time has expired and no result,maybe we should
> > > > > start a new voting for Service-Center version 1.3.0?
> > > > >
> > > > >
> > > > > Wishes & Regards
> > > > > ---
> > > > > Mabin
> > > > >
> > > > >
> > > > >
> > > > > Liubao (A)  于2019年11月4日周一 下午4:14写道：
> > > > >
> > > > > > +1
> > > > > >
> > > > > > I have checked the release notes and binaries. Do some basic
> tests
> > with
> > > > > > windows version.
> > > > > >
> > > > > > -邮件原件-
> > > > > > 发件人: Mohammad Asif Siddiqui [mailto:asifdxtr...@apache.org]
> > > > > > 发送时间: 2019年10月31日 22:06
> > > > > > 收件人: dev@servicecomb.apache.org
> > > > > > 主题: Re: [VOTE] Release Apache ServiceComb Service-Center version
> > 1.3.0
> > > > > >
> > > > > > Hi All,
> > > > > >
> > > > > > I faced some network problem with my SVN client so the packages
> > which were
> > > > > > uploaded were outdated, I have uploaded the correct rc in the svn
> > now, hope
> > > > > > we can go ahead with the voting now.
> > > > > >
> > > > > > Here is my +1 (Binding)
> > > > > >
> > > > > > Checks Done:
> > > > > >  - verify hash and signature
> > > > > >  - ran the test cases on linux
> > > > > >  - check with RAT tool for ASF headers
> > > > > >
> > > > > > Regards
> > > > > > Asif
> > > > > >
> > > > > > On 2019/10/30 01:17:21, victor chan 
> > wrote:
> > > > > > > Hi Asif，
> > > > > > > gpg --verify also fails, the following is the error message,
> > > > > > >
> > > > > > > root@chenzhu:~/chan/release# gpg --verify
> > > > > > > apache-servicecomb-service-center-1.3.0-src.zip.asc
> > > > > > > apache-servicecomb-service-center-1.3.0-src.zip
> > > > > > > gpg: Signature made Sun 27 Oct 2019 05:03:20 PM CST using RSA
> > key ID
> > > > > > > BD7A4D69
> > > > > > > gpg: Good signature from "Mohammad Asif Siddiqui (ServiceComb
> > Code
> > > > > > > Signing
> > > > > > > Key) "
> > > > > > > gpg: WARNING: This key is not certified with a trusted
> signature!
> > > > > > > gpg:  There is no indication that the signature belongs
> > to the
> > > > > > > owner.
> > > > > > > Primary key fingerprint: 42C0 D794 0FCD E5E6 30E4  AAE3 DC93
> > F696 BD7A
> > > > > > > 4D69 root@chenzhu:~/chan/release# gpg --verify
> > > > > > > apache-servicecomb-service-c

Re: [DISCUSSION][Toolkit] Integrate oas-validator compliance functionality

[Bin Ma]

Sure,I think it is feasible.


Wishes & Regards
---
Mabin



Daniel Qian  于2019年11月5日周二 下午1:43写道：

> Hi Ma, since we discussed about compatibility check sub command to be:
> cc / checkcompatibility .[1]
> So, we can also use cs / checkstyle here.
>
> [1]:
> https://lists.apache.org/thread.html/c88cda03ec52182482679bd9be36b9ad57bc8d03ee43a4912ad38d90@%3Cdev.servicecomb.apache.org%3E
>
> Daniel Qian  于2019年11月1日周五 下午5:11写道：
> >
> > PR[1] created
> >
> > [1] https://github.com/apache/servicecomb-toolkit/pull/42
> >
> > Willem Jiang  于2019年11月1日周五 下午12:26写道：
> > >
> > > Hi Daniel
> > >
> > > Yeah, I think it's a very good idea.
> > > Looking forward your PR.
> > >
> > > Willem Jiang
> > >
> > > Twitter: willemjiang
> > > Weibo: 姜宁willem
> > >
> > > On Wed, Oct 30, 2019 at 10:31 AM Daniel Qian 
> wrote:
> > > >
> > > > I created an issue SCB-1553[1] to integrate oas-validator compliance
> > > > check to toolkit cli.
> > > >
> > > > I suggest the usage like this:
> > > >
> > > > java -jar toolkit-cli-{version}.jar checkstyle
> /path/to/openapiv3.yaml
> > > >
> > > > I prefer checksytle because of it's clearer than compliance.
> > > >
> > > > oas-validator compliance doc could be found here[2]
> > > >
> > > > [1] https://issues.apache.org/jira/projects/SCB/issues/SCB-1553
> > > > [2]
> https://github.com/apache/servicecomb-toolkit/blob/import-oas-validator/oas-validator/README.md#%E5%90%88%E8%A7%84%E6%80%A7%E6%A0%A1%E9%AA%8C
> > > >
> > > > --
> > > > Daniel Qian
> > > >
> > > > 博客：https://segmentfault.com/u/chanjarster
> > > > github：https://github.com/chanjarster
> >
> >
> >
> > --
> > Daniel Qian
> >
> > 博客：https://segmentfault.com/u/chanjarster
> > github：https://github.com/chanjarster
>
>
>
> --
> Daniel Qian
>
> 博客：https://segmentfault.com/u/chanjarster
> github：https://github.com/chanjarster
>

Re: [DISCUSSION][Toolkit] Integrate oas-validator compability check functionality

[Bin Ma]

Hi Daniel,

Sorry, I misread the question.

I think it's better to support both checkcompatibility and cc as
subcommands.

Wishes & Regards
---
Mabin



sen sun  于2019年11月5日周二 上午9:40写道：

> I think Ma just made an example of the option naming style instead of the
> subcommand.
> I think it's a good idea to support both checkcompatibility and cc as
> subcommands.
>
> Daniel Qian  于2019年11月5日周二 上午7:28写道：
>
> > Hello Ma, found current cli style is  .
> > So if we do --check-compatability then which subcommand should we use?
> >
> > Bin Ma  于2019年11月5日周二 上午12:44写道：
> > >
> > > I recommend keeping the same as the current option naming style,
> > > such as "-c", "-- check-compability "
> > >
> > >
> > > Wishes & Regards
> > > ---
> > > Mabin
> > >
> > >
> > >
> > > Willem Jiang  于2019年11月1日周五 下午12:31写道：
> > >
> > > > I think we can support checkcompatibility and the short one cc at the
> > same
> > > > time.
> > > > Any thoughts?
> > > >
> > > > Willem Jiang
> > > >
> > > > Twitter: willemjiang
> > > > Weibo: 姜宁willem
> > > >
> > > > On Wed, Oct 30, 2019 at 10:37 AM Daniel Qian 
> > > > wrote:
> > > > >
> > > > > I created an issue SCB-1555[1] to integrate oas-validator
> > > > > compatibility check to toolkit cli.
> > > > >
> > > > > I suggest usage like this:
> > > > > java -jar toolkit-cli-{version}.jar checkcompability
> > > > > /path/to/openapiv3-1.yaml /path/to/openapiv3-2.yaml
> > > > >
> > > > > But the subcommand checkcompability is too long, maybe we can use a
> > > > > abbr for it, such as cc?
> > > > >
> > > > > Any ideas?
> > > > >
> > > > > [1] https://issues.apache.org/jira/browse/SCB-1555
> > > > > [2]
> > > >
> >
> https://github.com/apache/servicecomb-toolkit/blob/import-oas-validator/oas-validator/README.md#%E5%85%BC%E5%AE%B9%E6%80%A7%E6%A3%80%E6%9F%A5
> > > > >
> > > > > --
> > > > > Daniel Qian
> > > > >
> > > > > 博客：https://segmentfault.com/u/chanjarster
> > > > > github：https://github.com/chanjarster
> > > >
> >
> >
> >
> > --
> > Daniel Qian
> >
> > 博客：https://segmentfault.com/u/chanjarster
> > github：https://github.com/chanjarster
> >
>

Re: [VOTE] Release Apache ServiceComb Service-Center version 1.3.0

[Bin Ma]

Hi Asif,

Voting time has expired and no result,maybe we should
start a new voting for Service-Center version 1.3.0?


Wishes & Regards
---
Mabin



Liubao (A)  于2019年11月4日周一 下午4:14写道：

> +1
>
> I have checked the release notes and binaries. Do some basic tests with
> windows version.
>
> -邮件原件-
> 发件人: Mohammad Asif Siddiqui [mailto:asifdxtr...@apache.org]
> 发送时间: 2019年10月31日 22:06
> 收件人: dev@servicecomb.apache.org
> 主题: Re: [VOTE] Release Apache ServiceComb Service-Center version 1.3.0
>
> Hi All,
>
> I faced some network problem with my SVN client so the packages which were
> uploaded were outdated, I have uploaded the correct rc in the svn now, hope
> we can go ahead with the voting now.
>
> Here is my +1 (Binding)
>
> Checks Done:
>  - verify hash and signature
>  - ran the test cases on linux
>  - check with RAT tool for ASF headers
>
> Regards
> Asif
>
> On 2019/10/30 01:17:21, victor chan  wrote:
> > Hi Asif，
> > gpg --verify also fails, the following is the error message,
> >
> > root@chenzhu:~/chan/release# gpg --verify
> > apache-servicecomb-service-center-1.3.0-src.zip.asc
> > apache-servicecomb-service-center-1.3.0-src.zip
> > gpg: Signature made Sun 27 Oct 2019 05:03:20 PM CST using RSA key ID
> > BD7A4D69
> > gpg: Good signature from "Mohammad Asif Siddiqui (ServiceComb Code
> > Signing
> > Key) "
> > gpg: WARNING: This key is not certified with a trusted signature!
> > gpg:  There is no indication that the signature belongs to the
> > owner.
> > Primary key fingerprint: 42C0 D794 0FCD E5E6 30E4  AAE3 DC93 F696 BD7A
> > 4D69 root@chenzhu:~/chan/release# gpg --verify
> > apache-servicecomb-service-center-1.3.0-darwin-amd64.tar.gz.asc
> > apache-servicecomb-service-center-1.3.0-darwin-amd64.tar.gz
> > gpg: Signature made Sun 27 Oct 2019 05:04:00 PM CST using RSA key ID
> > BD7A4D69
> > gpg: BAD signature from "Mohammad Asif Siddiqui (ServiceComb Code
> > Signing
> > Key) "
> > root@chenzhu:~/chan/release# gpg --verify
> > apache-servicecomb-service-center-1.3.0-linux-amd64.tar.gz.asc
> > apache-servicecomb-service-center-1.3.0-linux-amd64.tar.gz
> > gpg: Signature made Sun 27 Oct 2019 05:03:44 PM CST using RSA key ID
> > BD7A4D69
> > gpg: BAD signature from "Mohammad Asif Siddiqui (ServiceComb Code
> > Signing
> > Key) "
> > root@chenzhu:~/chan/release# gpg --verify
> > apache-servicecomb-service-center-1.3.0-windows-amd64.tar.gz.asc
> > apache-servicecomb-service-center-1.3.0-windows-amd64.tar.gz
> > gpg: Signature made Sun 27 Oct 2019 05:03:55 PM CST using RSA key ID
> > BD7A4D69
> > gpg: BAD signature from "Mohammad Asif Siddiqui (ServiceComb Code
> > Signing
> > Key) "
> > root@chenzhu:~/chan/release# gpg --list-keys /root/.gnupg/pubring.gpg
> > 
> > pub   4096R/BD7A4D69 2018-03-11
> > uid  Mohammad Asif Siddiqui (ServiceComb Code Signing
> Key) <
> > asifdxtr...@apache.org>
> > sub   4096R/DF1487F5 2018-03-11
> >
> > pub   4096R/50764CEC 2019-08-23
> > uid  mabin 
> > sub   4096R/973DAB8F 2019-08-23
> >
> >
> > root@chenzhu:~/chan/release# sha512sum -c
> > apache-servicecomb-service-center-1.3.0-src.zip.sha512
> > apache-servicecomb-service-center-1.3.0-src.zip: OK
> > root@chenzhu:~/chan/release# sha512sum -c
> > apache-servicecomb-service-center-1.3.0-darwin-amd64.tar.gz.sha512
> > apache-servicecomb-service-center-1.3.0-darwin-amd64.tar.gz: FAILED
> > sha512sum: WARNING: 1 computed checksum did NOT match
> > root@chenzhu:~/chan/release# sha512sum -c
> > apache-servicecomb-service-center-1.3.0-linux-amd64.tar.gz.sha512
> > apache-servicecomb-service-center-1.3.0-linux-amd64.tar.gz: FAILED
> > sha512sum: WARNING: 1 computed checksum did NOT match
> > root@chenzhu:~/chan/release# sha512sum -c
> > apache-servicecomb-service-center-1.3.0-windows-amd64.tar.gz.sha512
> > apache-servicecomb-service-center-1.3.0-windows-amd64.tar.gz: FAILED
> > sha512sum: WARNING: 1 computed checksum did NOT match
> >
> > Wishes & Regards
> >
> > Mohammad Asif Siddiqui  于2019年10月27日周日
> > 下午5:14写道：
> >
> > > Hi All,
> > >
> > > This is a call for a Vote to release Apache ServiceComb
> > > Service-Center version 1.3.0
> > >
> > > Release Notes :
> > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=123
> > > 21626=12345385
> > >
> > >
> > > Release Candidate :
> > > https://dist.apache.org/repos/dist/dev/servicecomb/servicecomb-servi
> > > ce-center/1.3.0
> > >
> > >
> > > Release Tag :
> > > https://github.com/apache/servicecomb-service-center/releases/tag/1.
> > > 3.0
> > >
> > > Release CommitID : c2dc0caef7069ff38cd7395582cf0883d4172dc4
> > >
> > > Keys to verify the Release Candidate :
> > > https://dist.apache.org/repos/dist/dev/servicecomb/KEYS
> > >
> > > Guide to build the release from source :
> > > https://github.com/apache/servicecomb-service-center/tree/master/scr
> > > ipts/release
> > >
> > >
> > > Voting will start now ( Sunday, 27th October, 2019) and will remain
> > > open for 

Re: [DISCUSSION][Toolkit] Integrate oas-validator compability check functionality

[Bin Ma]

I recommend keeping the same as the current option naming style,
such as "-c", "-- check-compability "


Wishes & Regards
---
Mabin



Willem Jiang  于2019年11月1日周五 下午12:31写道：

> I think we can support checkcompatibility and the short one cc at the same
> time.
> Any thoughts?
>
> Willem Jiang
>
> Twitter: willemjiang
> Weibo: 姜宁willem
>
> On Wed, Oct 30, 2019 at 10:37 AM Daniel Qian 
> wrote:
> >
> > I created an issue SCB-1555[1] to integrate oas-validator
> > compatibility check to toolkit cli.
> >
> > I suggest usage like this:
> > java -jar toolkit-cli-{version}.jar checkcompability
> > /path/to/openapiv3-1.yaml /path/to/openapiv3-2.yaml
> >
> > But the subcommand checkcompability is too long, maybe we can use a
> > abbr for it, such as cc?
> >
> > Any ideas?
> >
> > [1] https://issues.apache.org/jira/browse/SCB-1555
> > [2]
> https://github.com/apache/servicecomb-toolkit/blob/import-oas-validator/oas-validator/README.md#%E5%85%BC%E5%AE%B9%E6%80%A7%E6%A3%80%E6%9F%A5
> >
> > --
> > Daniel Qian
> >
> > 博客：https://segmentfault.com/u/chanjarster
> > github：https://github.com/chanjarster
>

Re: [VOTE] Release Apache ServiceComb Java-Chassis version 1.3.0

[Bin Ma]

Got it.

+1

Wishes & Regards
-- -
Mabin



Willem Jiang < willem.ji...@gmail.com >于2019年10月29日周二上午8:02写道：

> Hi MaBin,
>
> You just need to
> Please check out this link[1] for the release note of ServiceComb Java
> Chassis 1.3.0.
>
> [1] https://issues.apache.org/ jira/secure/ReleaseNote.jspa? version=
> 12345462=& projectId=12321626= Create
> <https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12345462==12321626=Create>
>
> Willem Jiang
>
> Twitter: willemjiang
> Weibo:姜宁willem
>
> On Mon, Oct 28, 2019 at 11:13 PM Bin Ma < mabin1...@gmail.com > wrote:
> >
> > Hi bismy,
> >
> > I checked the Release Notes,but I could not find
> > the issues lists for Java-Chassis version 1.3.0.
> >
> > Compared with the previous version ServiceComb Java-Chassis 1.2.1,
> > version 1.3.0
> > no solve any issues?
> >
> > Wishes & Regards
> > -- -
> > Mabin
> >
> >
> >
> >
> > Willem Jiang < willem.ji...@gmail.com >于2019年10月28日周一下午2:28写道：
> >
> > > +1. (Binding)
> > >
> > > Checked the release candidate of source and binary,
> > > Checked staging repo.
> > >
> > > Thanks for the LiuBao's hard work to cut the release kit.
> > >
> > > Willem Jiang
> > >
> > > Twitter: willemjiang
> > > Weibo:姜宁willem
> > >
> >> On Sat, Oct 26, 2019 at 5 :33 PM bismy < bi...@qq.com> wrote:
> > > >
> > > > Hello All,
> > > >
> > > >
> > > > This is a call for a Vote to release Apache ServiceComb Java-Chassis
> > > version 1.3.0
> > > >
> > > >
> > > > Release Notes :
> > > > https:// issues.apache.org/ jira/secure/ReleaseNote.jspa?
> projectId=12321626&
> > > version=12345462
> > > < https://issues.apache.org/ jira/secure/ReleaseNote .jspa? 
> > > projectId=12321626&
> version=12345462
> <https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12321626version=12345462>
> >
> > > >
> > > >
> > > > Release Candidate :
> > > >https://dist.apache.org/ repos/ <https://dist.apache.org/repos/>
> dist/dev/servicecomb/ servicecomb-java-chassis/1.3.
> > > 0/rc01/
> > > < https://dist.apache.org/ repos/dist/dev/servicecomb/ 
> > > servicecomb-java-chassis/1.3.
> 0/rc01/
> <https://dist.apache.org/repos/dist/dev/servicecomb/servicecomb-java-chassis/1.3.0/rc01/>
> >
> > > >
> > > >
> > > > Staging Repo :
> > > > https://repository.apache.org/ content/repositories /
> > > orgapacheservicecomb-1408
> > > < https://repository.apache. org/content/repositories/
> orgapacheservicecomb-1408
> <https://repository.apache.org/content/repositories/orgapacheservicecomb-1408>
> >
> > > >
> > > >
> > > > Release Tag :
> > > > https://github.com/apache/ servicecomb-java-chassis/
> releases/tag/1.3.0
> > > <https://github.com/apache/ servicecomb-java-chassis/
> releases/tag/1.3.0
> <https://github.com/apache/servicecomb-java-chassis/releases/tag/1.3.0> >
> > > >
> > > >
> > > > Release CommitID : 3896be3afdfd51256e59ec8ceed0f1 aa04c3b035
> > > >
> > > >
> > > > Keys to verify the Release Candidate :
> > > > https://dist.apache.org /repos/ <https://dist.apache.org/repos/>
> dist/dev/servicecomb/KEYS
> > > < https://dist.apache.org/ repos/dist/dev/servicecomb/ KEYS
> <https://dist.apache.org/repos/dist/dev/servicecomb/KEYS> >
> > > >
> > > >
> > > > Voting will start now ( Friday, 26 October, 2019) and will remain
> open
> > > > for at-least 72 hours, Request all PMC members to give their vote.
> > > >
> > > >
> > >> [ ] +1 Release this package as 1.3.0
> > > > [ ] +0 No Opinion
> > > > [ ] -1 Do not release this package because
> > > >
> > > >
> > > > On the behalf of ServiceComb Team
> > > > Liu Bao
> > >
>

Re: [DISCUSSION] How to import oas-validator to toolkit project

[Bin Ma]

@Daniel done,enjoy it


Wishes & Regards
---
Mabin



Daniel Qian  于2019年10月29日周二 上午8:59写道：

> Ok, let's do option 2.
> Please tell me when the branch is created, so I can make a PR for it,
> is suggest the branch name be import-oas-validator
>
> Willem Jiang  于2019年10月29日周二 上午8:10写道：
> >
> > +1 for Option2.
> > Option 2 is much better, as it won't block the development of the
> > master branch.
> >
> >
> > Willem Jiang
> >
> > Twitter: willemjiang
> > Weibo: 姜宁willem
> >
> > On Mon, Oct 28, 2019 at 2:24 PM Daniel Qian 
> wrote:
> > >
> > > Since oas-validator donation process is finished (see this [1]) so
> > > next is to decide how to import oas-validator code into toolkit
> > > project.
> > >
> > > IMO, the first thing is merging the code ASAP, after that we will
> > > discuss how to integrating.
> > >
> > > I have two options:
> > >
> > > 1. Unzip the code archive and create a directory for it, push it to
> > > toolkit master branch
> > > 2. Create a branch on toolkit repo, unzip the code archive and create
> > > a directory for it, push it to that branch, after integration finished
> > > merge that branch to master
> > >
> > > Any ideas?
> > >
> > > [1] https://issues.apache.org/jira/browse/INCUBATOR-247
> > >
> > >
> > > --
> > > Daniel Qian
> > >
> > > 博客：https://segmentfault.com/u/chanjarster
> > > github：https://github.com/chanjarster
>
>
>
> --
> Daniel Qian
>
> 博客：https://segmentfault.com/u/chanjarster
> github：https://github.com/chanjarster
>

Re: [VOTE] Release Apache ServiceComb Service-Center version 1.3.0

[Bin Ma]

Hi Asif,

The issues[1] for Service-Center version 1.3.0 are not all close,maybe we
need to update their status.


[1] https://issues.apache.org/jira/projects/SCB/versions/12345385


Wishes & Regards
---
Mabin




Mohammad Asif Siddiqui  于2019年10月27日周日 下午5:14写道：

> Hi All,
>
> This is a call for a Vote to release Apache ServiceComb Service-Center
> version 1.3.0
>
> Release Notes :
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12321626=12345385
>
>
> Release Candidate :
> https://dist.apache.org/repos/dist/dev/servicecomb/servicecomb-service-center/1.3.0
>
>
> Release Tag :
> https://github.com/apache/servicecomb-service-center/releases/tag/1.3.0
>
> Release CommitID : c2dc0caef7069ff38cd7395582cf0883d4172dc4
>
> Keys to verify the Release Candidate :
> https://dist.apache.org/repos/dist/dev/servicecomb/KEYS
>
> Guide to build the release from source :
> https://github.com/apache/servicecomb-service-center/tree/master/scripts/release
>
>
> Voting will start now ( Sunday, 27th October, 2019) and will remain open
> for at-least 72 hours, Request all PMC members to give their vote.
>
> [ ] +1 Release this package as 1.3.0
> [ ] +0 No Opinion
> [ ] -1 Do not release this package because
>
> On the behalf of ServiceComb Team
> Mohammad Asif Siddiqui
>

Re: [DISCUSSION] How to import oas-validator to toolkit project

[Bin Ma]

Hi Daniel ,

Thanks for your donation, I choose 2.
: )


Wishes & Regards
---
Mabin



Daniel Qian  于2019年10月28日周一 下午2:24写道：

> Since oas-validator donation process is finished (see this [1]) so
> next is to decide how to import oas-validator code into toolkit
> project.
>
> IMO, the first thing is merging the code ASAP, after that we will
> discuss how to integrating.
>
> I have two options:
>
> 1. Unzip the code archive and create a directory for it, push it to
> toolkit master branch
> 2. Create a branch on toolkit repo, unzip the code archive and create
> a directory for it, push it to that branch, after integration finished
> merge that branch to master
>
> Any ideas?
>
> [1] https://issues.apache.org/jira/browse/INCUBATOR-247
>
>
> --
> Daniel Qian
>
> 博客：https://segmentfault.com/u/chanjarster
> github：https://github.com/chanjarster
>

Re: [VOTE] Release Apache ServiceComb Java-Chassis version 1.3.0

[Bin Ma]

Hi bismy,

I checked the Release Notes,but I could not find
the issues lists for Java-Chassis version 1.3.0.

Compared with the previous version ServiceComb Java-Chassis 1.2.1,
version 1.3.0
no solve any issues?

Wishes & Regards
-- -
Mabin




Willem Jiang < willem.ji...@gmail.com >于2019年10月28日周一下午2:28写道：

> +1. (Binding)
>
> Checked the release candidate of source and binary,
> Checked staging repo.
>
> Thanks for the LiuBao's hard work to cut the release kit.
>
> Willem Jiang
>
> Twitter: willemjiang
> Weibo:姜宁willem
>
> On Sat, Oct 26, 2019 at 5 :33 PM bismy < bi...@qq.com > wrote:
> >
> > Hello All,
> >
> >
> > This is a call for a Vote to release Apache ServiceComb Java-Chassis
> version 1.3.0
> >
> >
> > Release Notes :
> > https:// issues.apache.org/ jira/secure/ReleaseNote.jspa? 
> > projectId=12321626&
> version=12345462
> 
> >
> >
> > Release Candidate :
> >https://dist.apache.org/repos/ dist/dev/servicecomb/ 
> >servicecomb-java-chassis/1.3.
> 0/rc01/
> 
> >
> >
> > Staging Repo :
> > https://repository.apache.org/ content/repositories /
> orgapacheservicecomb-1408
> 
> >
> >
> > Release Tag :
> > https://github.com/apache/ servicecomb-java-chassis/ releases/tag/1.3.0
> 
> >
> >
> > Release CommitID : 3896be3afdfd51256e59ec8ceed0f1 aa04c3b035
> >
> >
> > Keys to verify the Release Candidate :
> > https://dist.apache.org/repos/ dist/dev/servicecomb/KEYS
> 
> >
> >
> > Voting will start now ( Friday, 26 October, 2019) and will remain open
> > for at-least 72 hours, Request all PMC members to give their vote.
> >
> >
> > [ ] +1 Release this package as 1.3.0
> > [ ] +0 No Opinion
> > [ ] -1 Do not release this package because
> >
> >
> > On the behalf of ServiceComb Team
> > Liu Bao
>

Re: Swagger Codegen

[Bin Ma]

As you wish, no problem at that time : )


Wishes & Regards
---
Mabin



William Cheng  于2019年10月24日周四 下午8:59写道：

> Please enjoy the weekend instead
>
> From what I understand this is not urgent, what about next Tuesday
> afternoon say 3pm HKT?
>
> Cheers,
> William
>
>
>
> On Thu, 24 Oct 2019 at 20:13, Bin Ma  wrote:
>
>>
>> Sorry,I',m not free on this Friday,
>>
>> how about this Saturday(Beijing time)?
>>
>>
>> Wishes & Regards
>> ---
>> Mabin
>>
>>
>>
>> William Cheng  于2019年10月24日周四 上午8:14写道：
>>
>>> Are you free for a quick chat (IM) tomorrow (Friday)?
>>>
>>> My timezone is +0800.
>>>
>>> We can use Google Hangout or other IM channels you prefer (e.g. WeChat).
>>>
>>> Best regards,
>>> William
>>>
>>> On Wed, 23 Oct 2019 at 19:59, Bin Ma  wrote:
>>>
>>>> Hi William Cheng,
>>>>
>>>> Thanks for your interest in the servicecomb-toolkit project, the
>>>> codegen of the servicecomb-toolkit project implements the microservices
>>>> code template[1] base on ServiceComb, and I learned that the
>>>> OpenAPITools/openapi-generator project [2] also provides a
>>>> collection of code templates, so I think maybe we can form some
>>>> cooperation
>>>>  on this, I'd like to hear from you, looking forward to your reply.
>>>>
>>>> Thanks: )
>>>>
>>>> [1]
>>>> https://github.com/apache/servicecomb-toolkit/tree/master/codegen/src/main/resources/ServiceComb
>>>>
>>>> [2]
>>>> https://github.com/OpenAPITools/openapi-generator/tree/master/modules/openapi-generator/src/main/resources
>>>>
>>>> Wishes & Regards
>>>> ---
>>>> Mabin
>>>>
>>>>
>>>>
>>>> sen sun  于2019年10月23日周三 下午3:34写道：
>>>>
>>>>> Hi William,
>>>>>
>>>>> I have read your email in detail. I have learned about the relationship
>>>>> between openapi-generator(
>>>>> https://github.com/OpenAPITools/openapi-generator)
>>>>>  and swagger-codegen(https://github.com/swagger-api/swagger-codegen)
>>>>> . When
>>>>> upgrading to openapi v3, we used openapi-generator in our project(
>>>>>
>>>>> https://github.com/apache/servicecomb-toolkit/blob/fa55b53ae66e5e6323dba88339b1eb0014003c15/toolkit-distribution/src/release/LICENSE#L347
>>>>> ).
>>>>> There are no hard-to-solve problems in the current use. If there is a
>>>>> problem, I will give feedback in time. Thanks
>>>>>
>>>>> Willem Jiang  于2019年10月21日周一 下午5:06写道：
>>>>>
>>>>> > Hi William，
>>>>> >
>>>>> > Thanks for your information. It's good to know there are some new
>>>>> > features of OpenAPI Generator.
>>>>> > Current we are leverage OpenAPI to do the contract first web service
>>>>> > development, and we just upgrade to use OpenAPI V3  in the toolkit.
>>>>> > I'm not the writer of toolkit, so I just forward the mail to the
>>>>> > dev@servicecomb, maybe Sun LiShen can answer your questions.
>>>>> >
>>>>> > Willem Jiang
>>>>> >
>>>>> > Twitter: willemjiang
>>>>> > Weibo: 姜宁willem
>>>>> >
>>>>> > On Mon, Oct 21, 2019 at 12:35 AM William Cheng 
>>>>> > wrote:
>>>>> > >
>>>>> > > Hi,
>>>>> > >
>>>>> > > Understood that you're busy. I've an important news to share with
>>>>> you:
>>>>> > >
>>>>> > > In May 2018, myself and other top contributors (40+) have decided
>>>>> to
>>>>> > fork Swagger Codegen to maintain a community-driven version called
>>>>> "OpenAPI
>>>>> > Generator" (https://openapi-generator.tech), which supports both
>>>>> > OpenAPI/Swagger spec v2 and v3.
>>>>> > >
>>>>> > > For the reasons behind the fork, please refer to the Q:
>>>>> >
>>>>> https://github.com/OpenAPITools/openapi-generator/blob/master/docs/qna.md
>>>>> .
>>>>> > For migration, please refer to
>>>>> >
>>>>> https://github.com/OpenAPITools/openapi-generator/blob/master/docs/migration-from-swagger-codegen.md
>>>>> > >
>>>>> > > 2 weeks ago we released OpenAPI Generator v4.1.3 with 4 new
>>>>> generators -
>>>>> > https://twitter.com/oas_generator/status/1180123829626003456. Please
>>>>> > check it out and let us know if you've any feedback or questions.
>>>>> > >
>>>>> > > Best regards,
>>>>> > > William
>>>>> > > https://github.com/wing328
>>>>> > >
>>>>> > > On Fri, 18 Oct 2019 at 02:14, William Cheng 
>>>>> wrote:
>>>>> > >>
>>>>> > >> Hi Willem,
>>>>> > >>
>>>>> > >> Sorry for reaching out to you directly. I saw you using Swagger
>>>>> > Codegen:
>>>>> >
>>>>> https://github.com/apache/servicecomb-toolkit/blob/fa55b53ae66e5e6323dba88339b1eb0014003c15/toolkit-distribution/src/release/LICENSE#L357
>>>>> > >>
>>>>> > >> I'm the top contributor to Swagger Codegen. May I know how's your
>>>>> > experience with Swagger Codegen so far? Did you find it easy to use
>>>>> and
>>>>> > customize?
>>>>> > >>
>>>>> > >> Best regards,
>>>>> > >> William
>>>>> > >> https://github.com/wing328
>>>>> >
>>>>>
>>>>

Re: Swagger Codegen

[Bin Ma]

Sorry,I',m not free on this Friday,

how about this Saturday(Beijing time)?


Wishes & Regards
---
Mabin



William Cheng  于2019年10月24日周四 上午8:14写道：

> Are you free for a quick chat (IM) tomorrow (Friday)?
>
> My timezone is +0800.
>
> We can use Google Hangout or other IM channels you prefer (e.g. WeChat).
>
> Best regards,
> William
>
> On Wed, 23 Oct 2019 at 19:59, Bin Ma  wrote:
>
>> Hi William Cheng,
>>
>> Thanks for your interest in the servicecomb-toolkit project, the
>> codegen of the servicecomb-toolkit project implements the microservices
>> code template[1] base on ServiceComb, and I learned that the
>> OpenAPITools/openapi-generator project [2] also provides a
>> collection of code templates, so I think maybe we can form some
>> cooperation
>>  on this, I'd like to hear from you, looking forward to your reply.
>>
>> Thanks: )
>>
>> [1]
>> https://github.com/apache/servicecomb-toolkit/tree/master/codegen/src/main/resources/ServiceComb
>>
>> [2]
>> https://github.com/OpenAPITools/openapi-generator/tree/master/modules/openapi-generator/src/main/resources
>>
>> Wishes & Regards
>> ---
>> Mabin
>>
>>
>>
>> sen sun  于2019年10月23日周三 下午3:34写道：
>>
>>> Hi William,
>>>
>>> I have read your email in detail. I have learned about the relationship
>>> between openapi-generator(
>>> https://github.com/OpenAPITools/openapi-generator)
>>>  and swagger-codegen(https://github.com/swagger-api/swagger-codegen) .
>>> When
>>> upgrading to openapi v3, we used openapi-generator in our project(
>>>
>>> https://github.com/apache/servicecomb-toolkit/blob/fa55b53ae66e5e6323dba88339b1eb0014003c15/toolkit-distribution/src/release/LICENSE#L347
>>> ).
>>> There are no hard-to-solve problems in the current use. If there is a
>>> problem, I will give feedback in time. Thanks
>>>
>>> Willem Jiang  于2019年10月21日周一 下午5:06写道：
>>>
>>> > Hi William，
>>> >
>>> > Thanks for your information. It's good to know there are some new
>>> > features of OpenAPI Generator.
>>> > Current we are leverage OpenAPI to do the contract first web service
>>> > development, and we just upgrade to use OpenAPI V3  in the toolkit.
>>> > I'm not the writer of toolkit, so I just forward the mail to the
>>> > dev@servicecomb, maybe Sun LiShen can answer your questions.
>>> >
>>> > Willem Jiang
>>> >
>>> > Twitter: willemjiang
>>> > Weibo: 姜宁willem
>>> >
>>> > On Mon, Oct 21, 2019 at 12:35 AM William Cheng 
>>> > wrote:
>>> > >
>>> > > Hi,
>>> > >
>>> > > Understood that you're busy. I've an important news to share with
>>> you:
>>> > >
>>> > > In May 2018, myself and other top contributors (40+) have decided to
>>> > fork Swagger Codegen to maintain a community-driven version called
>>> "OpenAPI
>>> > Generator" (https://openapi-generator.tech), which supports both
>>> > OpenAPI/Swagger spec v2 and v3.
>>> > >
>>> > > For the reasons behind the fork, please refer to the Q:
>>> >
>>> https://github.com/OpenAPITools/openapi-generator/blob/master/docs/qna.md
>>> .
>>> > For migration, please refer to
>>> >
>>> https://github.com/OpenAPITools/openapi-generator/blob/master/docs/migration-from-swagger-codegen.md
>>> > >
>>> > > 2 weeks ago we released OpenAPI Generator v4.1.3 with 4 new
>>> generators -
>>> > https://twitter.com/oas_generator/status/1180123829626003456. Please
>>> > check it out and let us know if you've any feedback or questions.
>>> > >
>>> > > Best regards,
>>> > > William
>>> > > https://github.com/wing328
>>> > >
>>> > > On Fri, 18 Oct 2019 at 02:14, William Cheng 
>>> wrote:
>>> > >>
>>> > >> Hi Willem,
>>> > >>
>>> > >> Sorry for reaching out to you directly. I saw you using Swagger
>>> > Codegen:
>>> >
>>> https://github.com/apache/servicecomb-toolkit/blob/fa55b53ae66e5e6323dba88339b1eb0014003c15/toolkit-distribution/src/release/LICENSE#L357
>>> > >>
>>> > >> I'm the top contributor to Swagger Codegen. May I know how's your
>>> > experience with Swagger Codegen so far? Did you find it easy to use and
>>> > customize?
>>> > >>
>>> > >> Best regards,
>>> > >> William
>>> > >> https://github.com/wing328
>>> >
>>>
>>

Re: [discuss] some log question

[Bin Ma]

Hi,

The debug log will be printed in dev mode, maybe you can try to run in prod
mode.

open conf\app.conf and configure runmode as below:
runmode = prod

Best Wishes & Regards
---
Mabin



yp  于2019年10月23日周三 下午1:21写道：

> Hey guys:
>
>  The are a lot of duplicate logs after starting servicecomb-sc,
>
>
>  Some like :
>
>
> **
> 2019-10-23T13:12:18.807+0800DEBUGetcd/cacher_kv.go:83[244.81µs]finish to
> cache key /cse-sr/ms/dep-rules/, 2 items, rev: 28
> 2019-10-23T13:12:18.807+0800DEBUGetcd/cacher_kv.go:83[231.643µs]finish to
> cache key /cse-sr/domains/, 1 items, rev: 28
> 2019-10-23T13:12:18.807+0800DEBUGetcd/cacher_kv.go:83[231.243µs]finish to
> cache key /cse-sr/ms/tags/, 0 items, rev: 28
> 2019-10-23T13:12:18.807+0800DEBUGetcd/cacher_kv.go:83[187.147µs]finish to
> cache key /cse-sr/inst/leases/, 1 items, rev: 28
> 2019-10-23T13:12:18.807+0800DEBUGetcd/cacher_kv.go:83[166.848µs]finish to
> cache key /cse-sr/ms/rules/, 0 items, rev: 28
> 2019-10-23T13:12:18.807+0800DEBUGetcd/cacher_kv.go:83[277.301µs]finish to
> cache key /cse-sr/ms/alias/, 1 items, rev: 28
> 2019-10-23T13:12:18.810+0800DEBUGetcd/cacher_kv.go:83[1.613854ms]finish to
> cache key /cse-sr/ms/schema-sum/, 1 items, rev: 28
> 2019-10-23T13:12:18.807+0800DEBUGetcd/cacher_kv.go:83[165.661µs]finish to
> cache key /cse-pact/version/, 0 items, rev: 28
> 2019-10-23T13:12:18.807+0800DEBUGetcd/cacher_kv.go:83[229.101µs]finish to
> cache key /cse-sr/inst/files/, 1 items, rev: 28
> 2019-10-23T13:12:18.808+0800DEBUGetcd/cacher_kv.go:83[129.673µs]finish to
> cache key /cse-pact/latest/, 0 items, rev: 28
> 2019-10-23T13:12:18.808+0800DEBUGetcd/cacher_kv.go:83[172.488µs]finish to
> cache key /cse-sr/ms/indexes/, 3 items, rev: 28
> 2019-10-23T13:12:18.810+0800DEBUGetcd/cacher_kv.go:83[1.082668ms]finish to
> cache key /cse-sr/projects/, 1 items, rev: 28
> 2019-10-23T13:12:18.810+0800DEBUGetcd/cacher_kv.go:83[838.669µs]finish to
> cache key /cse-sr/ms/rule-indexes/, 0 items, rev: 28
> 2019-10-23T13:12:18.811+0800DEBUGetcd/cacher_kv.go:83[2.386158ms]finish to
> cache key /cse-sr/ms/dep-queue/, 0 items, rev: 28
> 2019-10-23T13:12:18.810+0800DEBUGetcd/cacher_kv.go:83[484.118µs]finish to
> cache key /cse-pact/participant/, 0 items, rev: 28
> 2019-10-23T13:12:18.810+0800DEBUGetcd/cacher_kv.go:83[1.9711ms]finish to
> cache key /cse-sr/ms/files/, 3 items, rev: 28
> 2019-10-23T13:12:18.811+0800DEBUGetcd/cacher_kv.go:83[2.135947ms]finish to
> cache key /cse-pact/pact-version/, 0 items, rev: 28
> 2019-10-23T13:12:18.810+0800DEBUGetcd/cacher_kv.go:83[601.773µs]finish to
> cache key /cse-pact/pact/, 0 items, rev: 28
> 2019-10-23T13:12:18.810+0800DEBUGetcd/cacher_kv.go:83[1.593579ms]finish to
> cache key /cse-pact/pact-tag/, 0 items, rev: 28
> 2019-10-23T13:12:18.811+0800DEBUGetcd/cacher_kv.go:83[2.548803ms]finish to
> cache key /cse-pact/verification/, 0 items, rev: 28
> 2019-10-23T13:12:19.792+0800DEBUGalarm/service.go:85alarm[BackendConnectionRefuse]
> CLEARED, map[]
> 2019-10-23T13:12:48.817+0800INFOservice/instance.go:323heartbeat
> successful, renew
> instance[7062417bf9ebd4c646bb23059003cea42180894a/24e02f56f4d611e9a30f8c8590750471]
> ttl to 120. operator
> 2019-10-23T13:12:48.818+0800DEBUGbackend/registry.go:216update service
> center
> instance[7062417bf9ebd4c646bb23059003cea42180894a/24e02f56f4d611e9a30f8c8590750471]
> heartbeat
> 2019-10-23T13:12:49.797+0800DEBUGalarm/service.go:85alarm[BackendConnectionRefuse]
> CLEARED, map[]
> 2019-10-23T13:13:18.820+0800INFOservice/instance.go:323heartbeat
> successful, renew
> instance[7062417bf9ebd4c646bb23059003cea42180894a/24e02f56f4d611e9a30f8c8590750471]
> ttl to 120. operator
> 2019-10-23T13:13:18.820+0800DEBUGbackend/registry.go:216update service
> center
> instance[7062417bf9ebd4c646bb23059003cea42180894a/24e02f56f4d611e9a30f8c8590750471]
> heartbeat
> 2019-10-23T13:13:19.798+0800DEBUGalarm/service.go:85alarm[BackendConnectionRefuse]
> CLEARED, map[]
> 2019-10-23T13:13:48.823+0800INFOservice/instance.go:323heartbeat
> successful, renew
> instance[7062417bf9ebd4c646bb23059003cea42180894a/24e02f56f4d611e9a30f8c8590750471]
> ttl to 120. operator
> 2019-10-23T13:13:48.823+0800DEBUGbackend/registry.go:216update service
> center
> instance[7062417bf9ebd4c646bb23059003cea42180894a/24e02f56f4d611e9a30f8c8590750471]
> heartbeat
> 2019-10-23T13:13:49.800+0800DEBUGalarm/service.go:85alarm[BackendConnectionRefuse]
> CLEARED, map[]
> **
>
>
> I have't started any apps yet, Is this the expected effect?
>
>
> One more,why do you need to display the go file in the sc log? Is it
> necessary?
>
>
> It’s weird in my opinion.
>
>
> If i missed something, remind me please! Thanks!
>
>
> - lan.liang
>
>

Re: [discuss] some log question

[Bin Ma]

By the way, if you have any requirements, welcome feedback to the
community,thanks : )


Best Wishes & Regards
---
Mabin



Bin Ma  于2019年10月23日周三 下午8:23写道：

> Hi,
>
> The debug log will be printed in dev mode, maybe you can try to run in prod
> mode.
>
> open conf\app.conf and configure runmode as below:
> runmode = prod
>
> Best Wishes & Regards
> ---
> Mabin
>
>
>
> yp  于2019年10月23日周三 下午1:21写道：
>
>> Hey guys:
>>
>>  The are a lot of duplicate logs after starting servicecomb-sc,
>>
>>
>>  Some like :
>>
>>
>> **
>> 2019-10-23T13:12:18.807+0800DEBUGetcd/cacher_kv.go:83[244.81µs]finish to
>> cache key /cse-sr/ms/dep-rules/, 2 items, rev: 28
>> 2019-10-23T13:12:18.807+0800DEBUGetcd/cacher_kv.go:83[231.643µs]finish to
>> cache key /cse-sr/domains/, 1 items, rev: 28
>> 2019-10-23T13:12:18.807+0800DEBUGetcd/cacher_kv.go:83[231.243µs]finish to
>> cache key /cse-sr/ms/tags/, 0 items, rev: 28
>> 2019-10-23T13:12:18.807+0800DEBUGetcd/cacher_kv.go:83[187.147µs]finish to
>> cache key /cse-sr/inst/leases/, 1 items, rev: 28
>> 2019-10-23T13:12:18.807+0800DEBUGetcd/cacher_kv.go:83[166.848µs]finish to
>> cache key /cse-sr/ms/rules/, 0 items, rev: 28
>> 2019-10-23T13:12:18.807+0800DEBUGetcd/cacher_kv.go:83[277.301µs]finish to
>> cache key /cse-sr/ms/alias/, 1 items, rev: 28
>> 2019-10-23T13:12:18.810+0800DEBUGetcd/cacher_kv.go:83[1.613854ms]finish
>> to cache key /cse-sr/ms/schema-sum/, 1 items, rev: 28
>> 2019-10-23T13:12:18.807+0800DEBUGetcd/cacher_kv.go:83[165.661µs]finish to
>> cache key /cse-pact/version/, 0 items, rev: 28
>> 2019-10-23T13:12:18.807+0800DEBUGetcd/cacher_kv.go:83[229.101µs]finish to
>> cache key /cse-sr/inst/files/, 1 items, rev: 28
>> 2019-10-23T13:12:18.808+0800DEBUGetcd/cacher_kv.go:83[129.673µs]finish to
>> cache key /cse-pact/latest/, 0 items, rev: 28
>> 2019-10-23T13:12:18.808+0800DEBUGetcd/cacher_kv.go:83[172.488µs]finish to
>> cache key /cse-sr/ms/indexes/, 3 items, rev: 28
>> 2019-10-23T13:12:18.810+0800DEBUGetcd/cacher_kv.go:83[1.082668ms]finish
>> to cache key /cse-sr/projects/, 1 items, rev: 28
>> 2019-10-23T13:12:18.810+0800DEBUGetcd/cacher_kv.go:83[838.669µs]finish to
>> cache key /cse-sr/ms/rule-indexes/, 0 items, rev: 28
>> 2019-10-23T13:12:18.811+0800DEBUGetcd/cacher_kv.go:83[2.386158ms]finish
>> to cache key /cse-sr/ms/dep-queue/, 0 items, rev: 28
>> 2019-10-23T13:12:18.810+0800DEBUGetcd/cacher_kv.go:83[484.118µs]finish to
>> cache key /cse-pact/participant/, 0 items, rev: 28
>> 2019-10-23T13:12:18.810+0800DEBUGetcd/cacher_kv.go:83[1.9711ms]finish to
>> cache key /cse-sr/ms/files/, 3 items, rev: 28
>> 2019-10-23T13:12:18.811+0800DEBUGetcd/cacher_kv.go:83[2.135947ms]finish
>> to cache key /cse-pact/pact-version/, 0 items, rev: 28
>> 2019-10-23T13:12:18.810+0800DEBUGetcd/cacher_kv.go:83[601.773µs]finish to
>> cache key /cse-pact/pact/, 0 items, rev: 28
>> 2019-10-23T13:12:18.810+0800DEBUGetcd/cacher_kv.go:83[1.593579ms]finish
>> to cache key /cse-pact/pact-tag/, 0 items, rev: 28
>> 2019-10-23T13:12:18.811+0800DEBUGetcd/cacher_kv.go:83[2.548803ms]finish
>> to cache key /cse-pact/verification/, 0 items, rev: 28
>> 2019-10-23T13:12:19.792+0800DEBUGalarm/service.go:85alarm[BackendConnectionRefuse]
>> CLEARED, map[]
>> 2019-10-23T13:12:48.817+0800INFOservice/instance.go:323heartbeat
>> successful, renew
>> instance[7062417bf9ebd4c646bb23059003cea42180894a/24e02f56f4d611e9a30f8c8590750471]
>> ttl to 120. operator
>> 2019-10-23T13:12:48.818+0800DEBUGbackend/registry.go:216update service
>> center
>> instance[7062417bf9ebd4c646bb23059003cea42180894a/24e02f56f4d611e9a30f8c8590750471]
>> heartbeat
>> 2019-10-23T13:12:49.797+0800DEBUGalarm/service.go:85alarm[BackendConnectionRefuse]
>> CLEARED, map[]
>> 2019-10-23T13:13:18.820+0800INFOservice/instance.go:323heartbeat
>> successful, renew
>> instance[7062417bf9ebd4c646bb23059003cea42180894a/24e02f56f4d611e9a30f8c8590750471]
>> ttl to 120. operator
>> 2019-10-23T13:13:18.820+0800DEBUGbackend/registry.go:216update service
>> center
>> instance[7062417bf9ebd4c646bb23059003cea42180894a/24e02f56f4d611e9a30f8c8590750471]
>> heartbeat
>> 2019-10-23T13:13:19.798+0800DEBUGalarm/service.go:85alarm[BackendConnectionRefuse]
>> CLEARED, map[]
>> 2019-10-23T13:13:48.823+0800INFOservice/instance.go:323heartbeat
>> successful, renew
>> instance[7062417bf9ebd4c646bb23059003cea42180894a/24e02f56f4d611e9a30f8c8590750471]
>> ttl to 120. operator
>> 2019-10-23T13:13:48.823+0800D

Re: [DISCUSSION/NOTICE]release java-chassis 1.3.0 and prepare for 2.0.0

[Bin Ma]

+1

Cool! Looking forward to 2.0.0 version: )


Best Wishes & Regards
---
Mabin



bismy  于2019年10月23日周三 上午9:48写道：

> Hi team,
>
>
> servicecomb-java-chassis now is ready for release 1.3.0, there are 6
> pennding PRs to be merged (they are all for bug fixes).
>
>
> We have prepared for weak-contract-type feature for a long time, and it is
> almost ready in branch weak-contract-type.
>
>
> As a result, we are going to release 1.3.0 based on master, and cut branch
> 1.x for future maintenance. And master becomes 2.0.0-SNAPSHOT, the
> weak-contract-type is going to merge to this branch.
>
>
> master 1.3.0-2.0.0-SNAPSHOT(weak-contract-type
> feature)-(swagger 3.0 support)(others)--
> 1.x 
> 1.3.0-1.3.1-SNAPSHOT(only bug fixes)-

Re: Swagger Codegen

[Bin Ma]

Hi William Cheng,

Thanks for your interest in the servicecomb-toolkit project, the
codegen of the servicecomb-toolkit project implements the microservices
code template[1] base on ServiceComb, and I learned that the
OpenAPITools/openapi-generator project [2] also provides a
collection of code templates, so I think maybe we can form some cooperation
 on this, I'd like to hear from you, looking forward to your reply.

Thanks: )

[1]
https://github.com/apache/servicecomb-toolkit/tree/master/codegen/src/main/resources/ServiceComb

[2]
https://github.com/OpenAPITools/openapi-generator/tree/master/modules/openapi-generator/src/main/resources

Wishes & Regards
---
Mabin



sen sun  于2019年10月23日周三 下午3:34写道：

> Hi William,
>
> I have read your email in detail. I have learned about the relationship
> between openapi-generator(
> https://github.com/OpenAPITools/openapi-generator)
>  and swagger-codegen(https://github.com/swagger-api/swagger-codegen) .
> When
> upgrading to openapi v3, we used openapi-generator in our project(
>
> https://github.com/apache/servicecomb-toolkit/blob/fa55b53ae66e5e6323dba88339b1eb0014003c15/toolkit-distribution/src/release/LICENSE#L347
> ).
> There are no hard-to-solve problems in the current use. If there is a
> problem, I will give feedback in time. Thanks
>
> Willem Jiang  于2019年10月21日周一 下午5:06写道：
>
> > Hi William，
> >
> > Thanks for your information. It's good to know there are some new
> > features of OpenAPI Generator.
> > Current we are leverage OpenAPI to do the contract first web service
> > development, and we just upgrade to use OpenAPI V3  in the toolkit.
> > I'm not the writer of toolkit, so I just forward the mail to the
> > dev@servicecomb, maybe Sun LiShen can answer your questions.
> >
> > Willem Jiang
> >
> > Twitter: willemjiang
> > Weibo: 姜宁willem
> >
> > On Mon, Oct 21, 2019 at 12:35 AM William Cheng 
> > wrote:
> > >
> > > Hi,
> > >
> > > Understood that you're busy. I've an important news to share with you:
> > >
> > > In May 2018, myself and other top contributors (40+) have decided to
> > fork Swagger Codegen to maintain a community-driven version called
> "OpenAPI
> > Generator" (https://openapi-generator.tech), which supports both
> > OpenAPI/Swagger spec v2 and v3.
> > >
> > > For the reasons behind the fork, please refer to the Q:
> >
> https://github.com/OpenAPITools/openapi-generator/blob/master/docs/qna.md.
> > For migration, please refer to
> >
> https://github.com/OpenAPITools/openapi-generator/blob/master/docs/migration-from-swagger-codegen.md
> > >
> > > 2 weeks ago we released OpenAPI Generator v4.1.3 with 4 new generators
> -
> > https://twitter.com/oas_generator/status/1180123829626003456. Please
> > check it out and let us know if you've any feedback or questions.
> > >
> > > Best regards,
> > > William
> > > https://github.com/wing328
> > >
> > > On Fri, 18 Oct 2019 at 02:14, William Cheng 
> wrote:
> > >>
> > >> Hi Willem,
> > >>
> > >> Sorry for reaching out to you directly. I saw you using Swagger
> > Codegen:
> >
> https://github.com/apache/servicecomb-toolkit/blob/fa55b53ae66e5e6323dba88339b1eb0014003c15/toolkit-distribution/src/release/LICENSE#L357
> > >>
> > >> I'm the top contributor to Swagger Codegen. May I know how's your
> > experience with Swagger Codegen so far? Did you find it easy to use and
> > customize?
> > >>
> > >> Best regards,
> > >> William
> > >> https://github.com/wing328
> >
>

Re: [VOTE] Release Apache ServiceComb Kie version 0.1.0

[Bin Ma]

2 issues[1] for Kie version 0.1.0 are not closed, I think we should updated
their status.

[1] https://issues.apache.org/jira/projects/SCB/versions/12345632


Best Wishes & Regards
---
Mabin




victor chan  于2019年10月23日周三 下午5:58写道：

> +1
>
> 1. go build success
> 2. RC dist PGP signature checked.
> 3. RC dist SHA signature checked.
> 4. ASF Headers checked
>
> sen sun  于2019年10月23日周三 下午3:40写道：
>
> > +1
> >
> > 1. go build success
> > 2. RC dist PGP signature checked.
> > 3. RC dist SHA signature checked.
> > 4. ASF Headers checked
> >
>

Re: [DISCUSSION] Optimize code implementations in ServiceComb-Java-Chassis

[Bin Ma]

It's cool! Thanks for your contribution : )


Best Wishes & Regards
---
Mabin



Ang Li  于2019年10月17日周四 下午3:25写道：

> Hi Team:
>
>
> I found some code implementations need to be optimized in
> servicecomb-java-chassis and created a jira issue to track:
> https://issues.apache.org/jira/projects/SCB/issues/SCB-1528
>
>
> All the optimizations are some small points about efficiency, readability,
> reliability and maintainability. Just to make code implementations more
> graceful.
> Comments are welcome to be added to the jira issue [SCB-1528] and I will
> do the optimization work.

Re: re-organize the docs in servicecomb portal

[Bin Ma]

It is recommended to split into multiple subtasks to trace this issue.



Best Wishes & Regards
---
Mabin



Xiaoliang Tian  于2019年10月12日周六 上午10:28写道：

> here u go  https://issues.apache.org/jira/browse/SCB-1521
>
> Willem Jiang  于2019年10月11日周五 下午6:10写道：
>
> > It make sense to do this change.
> > Do you mind create a JIRA for it?
> >
> > Willem Jiang
> >
> > Twitter: willemjiang
> > Weibo: 姜宁willem
> >
> > On Fri, Oct 11, 2019 at 11:11 AM Xiaoliang Tian
> >  wrote:
> > >
> > > now  https://servicecomb.apache.org/docs took so much
> responsabilities.
> > it
> > > holds not just docs for user and developers. but also meetup, news
> pages.
> > >
> > > it should only holds docs for user and developers.
> > >
> > > for other pages, put them into news/, blogs/ and community/
> > >
> > > for the old pages, do not migrate them into new folder but keep them in
> > > where they are.
> > >
> > >
> > > and we need add more pages
> > > docs/mesher
> > > docs/kie
> > > docs/service-center
> > > docs/getstarted: guide about how to install serivcecomb
> >
>

Re: [PROPOSAL] Mesher supports skywalking

[Bin Ma]

hi @陈硕
I think you can open a issue in Apache ServiceComb JIRA
to save your topology attachment , and feedback the link in the  mailing
list .

Best Wishes & Regards
---
Mabin



Sheng Wu  于2019年10月17日周四 下午2:46写道：

> Any update? This seems going to dark.
>
> Sheng.
>
> Sheng Wu 于2019年10月14日 周一下午12:38写道：
>
> > Interesting proposal.
> >
> > Could you explain a little more about the topology? And what do you
> expect
> > after the integration?
> >
> > Sheng
> >
> > Willem Jiang 于2019年10月14日 周一上午10:06写道：
> >
> >> I think we can get some feedback from the skywalking community, so I
> just
> >> forward the mail to dev@skywalking
> >> BTW, you find the topology map here[1]
> >> [1]
> >>
> >>
> https://issues.apache.org/jira/secure/attachment/12982640/12982640_image-2019-10-10-15-05-02-666.png
> >>
> >> Willem Jiang
> >>
> >> Twitter: willemjiang
> >> Weibo: 姜宁willem
> >>
> >>
> >> On Fri, Oct 11, 2019 at 10:45 AM 陈硕 <814464...@qq.com> wrote:
> >>
> >> > Hello, everyone
> >> >Skywalking is a very popular application performance management
> >> > software. We can enhance the performance management capability of
> >> mesher by
> >> > accessing skywalking.
> >> >Now I accessed skywalking using the manual-SDK go2sky(
> >> > https://github.com/tetratelabs/go2sky) recommended by the official
> >> > website . Unlike java-sdk , the SDK of golang need manually create and
> >> end
> >> > span to send messages to the skywalking server. Now I'm ready to
> adjust
> >> the
> >> > code. I want to put the code in the proxy/pkg directory. Create an APM
> >> > management directory and use go2sky as a client.
> >> >
> >> > Skywalking draws Mehser's topology as follows：
> >> >
> >> > Looking forward to your suggestions.
> >> >
> >> > --
> >> > 陈硕
> >> > 邮箱：814464...@qq.com
> >> >
> >> >
> >>
> > --
> > Sheng Wu
> > SkyWalking, Shardingsphere and Zipkin
> >
> --
> Sheng Wu
> SkyWalking, Shardingsphere and Zipkin
>

Re: [VOTE] Accept oas-validator to ServiceComb

[Bin Ma]

+1

Awsome! Thanks to the donation.

It's useful for enhancing the toolkit's API
specification validation capabilities.


Best Wishes & Regards
---
Mabin



sen sun  于2019年10月15日周二 下午6:47写道：

> +1
>
> This is a great project!
>
> yhs0092  于2019年10月15日周二 下午5:10写道：
>
> > +1
> > Great work!
> >
> >
> > Yours sincerely
> >
> >
> > Yao Haishi
> > yhs0...@163.com
> >
> >
> > On 10/15/2019 16:59，Ang Li wrote：
> > +1
> > Sounds Great!
> >
> >
> >
> >
> > --Original--
> > From:"Willem Jiang" > Date:Tue, Oct 15, 2019 11:07 AM
> > To:"dev" >
> > Subject:[VOTE] Accept oas-validator to ServiceComb
> >
> >
> >
> > Hi Team,
> >
> > This is a call for vote Accept oas-validator into
> > Apache Software Foundation (ASF) as a part of ServiceComb Toolkit.
> > There is the discussion thread[1] about the donation.
> >
> > Voting will start now ( Tuesday, 15th Oct, 2019) and will
> > remain open for at-least 72 hours, Request all PMC members to
> > give their vote.
> > [ ] +1 Accept
> > [ ] +0 No Opinion
> > [ ] -1 Reject because...
> >
> > [1]
> >
> https://lists.apache.org/thread.html/3fc8dae6faa2055dd59d600c9da8508360766ec361d81ec0ceefa8db@%3Cdev.servicecomb.apache.org%3E
> >
> > Willem Jiang
> >
> > Twitter: willemjiang
> > Weibo: 姜宁willem
>

Re: [VOTE] Release Apache ServiceComb Kie version 0.1.0

[Bin Ma]

+1


Best Wishes & Regards
---
Mabin



Shuo Chen  于2019年10月15日周二 下午5:21写道：

> +1
>
> Xiaoliang Tian  于2019年10月15日周二 下午3:56写道：
>
> > Hi All,
> >
> >   This is a call for Vote to release Apache ServiceComb Kie version 0.1.0
> >
> > Release Candidate :
> >
> >
> https://dist.apache.org/repos/dist/dev/servicecomb/servicecomb-kie/0.1.0/rc-02/
> >
> >
> >
> > Release Tag :
> > https://github.com/apache/servicecomb-kie/releases/tag/v0.1.0
> >
> > Release CommitID: 52d8ab78fd3c13c506eb135c5fdcf2b4aa55cda5
> >
> > Release Notes :
> >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12321626=12345632
> >
> >   Keys to verify the Release Candidate :
> > https://dist.apache.org/repos/dist/dev/servicecomb/KEYS
> >
> > Voting will start now ( Monday, 15nd October , 2019) and will remain open
> >  for at-least 72 hours, Request all PMC members to give their vote.
> >
> > [ ] +1 Release this package as 0.1.0
> > [ ] +0 No Opinion
> > [ ] -1 Do not release this package because
> >
> >  On the behalf of ServiceComb Team
> >
> >
> > Best Wishes & Regards
> >
>

Re: [VOTE] Release Apache ServiceComb Mesher version 1.6.3

[Bin Ma]

+1 non-binding

1. RC dist PGP signature checked
2. RC dist SHA signature  checked


Best Wishes & Regards
---
Mabin



陈硕  于2019年9月6日周五 下午2:56写道：

> +1
>
> Xiaoliang Tian  于2019年9月6日周五 下午2:46写道：
>
> > Hi All,
> >
> >   This is a call for Vote to release Apache ServiceComb Mesher version
> > 1.6.3
> >
> > Release Candidate :
> >
> >
> https://dist.apache.org/repos/dist/dev/servicecomb/servicecomb-mesher/1.6.3/rc-02/
> >
> >
> >
> > Release Tag :
> > https://github.com/apache/servicecomb-mesher/tree/v1.6.3
> >
> > Release CommitID:   c6a5e8af27470842a138da276c20223b31ab19bc
> >
> > Release Notes :
> >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12321626=12346107
> >
> >   Keys to verify the Release Candidate :
> > https://dist.apache.org/repos/dist/dev/servicecomb/KEYS
> >
> > Voting will start now ( Friday, 6nd September, 2019) and will remain open
> >  for at-least 72 hours, Request all PMC members to give their vote.
> >
> > [ ] +1 Release this package as 1.6.3
> > [ ] +0 No Opinion
> > [ ] -1 Do not release this package because
> >
> >  On the behalf of ServiceComb Team
> >
> >
> > Best Wishes & Regards
> > Xiaoliang Tian
> >
>

[ANNOUNCE] Apache ServiceComb Toolkit version 0.1.0 Released

[Bin Ma]

Hi All,

Apache ServiceComb Team is glad to announce the release of Apache
ServiceComb Toolkit 0.1.0

Apache ServiceComb Toolkit(https://github.com/apache/servicecomb-toolkit)
is a contract-based microservice development toolkit. It provides the
ability to convert and verify contracts, code, and documents, helping users
quickly build microservice projects based on popular microservices
frameworks and popular programming models, reducing the cost of
microservices entry, enabling users to focus on business development,
enhance refactoring and development efficiency.

Download Links : http://servicecomb.apache.org/release/toolkit-downloads

Release Notes : http://servicecomb.apache.org/release/toolkit-release-notes/

Know more about ServiceComb: http://servicecomb.apache.org/

ServiceComb Usefull Links :
- Mailing lists: dev@servicecomb.apache.org
- JIRA : https://issues.apache.org/jira/browse/SCB


Best Wishes & Regards
---
Mabin

Re: [VOTE] Release Apache ServiceComb Toolkit version 0.1.0

[Bin Ma]

Hi All,

We are glad to announce that ServiceComb community has approved the Apache
ServiceComb Toolkit version 0.1.0 release with the following results:

+1 binding: 5 (Mohammad Asif Siddiqui, Zen Lin, Willem Jiang, Xiaoliang
Tian, Liubao (A)  )
+1 non-binding: 3 (sen sun, victor chan, Bin Ma)

We will release the version soon.

Thanks All for your participation in this vote.


Best Wishes & Regards
---
Mabin



Bin Ma  于2019年8月30日周五 上午9:08写道：

> +1
>
>
> Best Wishes & Regards
> ---
> Mabin
>
>
>
> Liubao (A)  于2019年8月29日周四 上午10:42写道：
>
>> +1
>>
>>
>>
>> --
>> 刘宝 Liu Bao
>> Mobile: +86-18664569778
>> Email: bao@huawei.com<mailto:bao@huawei.com>
>> 发件人：Bin Ma 
>> 收件人：dev@servicecomb.apache.org 
>> 时间：2019-08-28 20:53:40
>> 主题Re: [VOTE] Release Apache ServiceComb Toolkit version 0.1.0
>>
>> Hi @Asif,
>>
>> ServiceComb Toolkit provides a maven plugin for the user, so it only
>> releases source code.
>>
>>
>> Best Wishes & Regards
>> ---
>> Mabin
>>
>>
>>
>> Willem Jiang  于2019年8月28日周三 下午7:36写道：
>>
>> > +1 binding.
>> > I checked:
>> > Staging repo looks good.
>> > The License and Notice file looks good.
>> > I can build the kit from the source.
>> >
>> > Willem Jiang
>> >
>> > Twitter: willemjiang
>> > Weibo: 姜宁willem
>> >
>> > On Tue, Aug 27, 2019 at 4:34 PM Bin Ma  wrote:
>> > >
>> > > Hi All,
>> > >
>> > > This is a call for Vote to release Apache ServiceComb Toolkit version
>> > 0.1.0
>> > >
>> > >
>> > > Release Candidate :
>> > >
>> >
>> https://dist.apache.org/repos/dist/dev/servicecomb/servicecomb-toolkit/0.1.0/rc-01/
>> > >
>> > >
>> > > Staging Repository :
>> > >
>> >
>> https://repository.apache.org/content/repositories/orgapacheservicecomb-1403
>> > >
>> > >
>> > > Release Tag :
>> > > https://github.com/apache/servicecomb-toolkit/releases/tag/0.1.0
>> > >
>> > > Release CommitID : 88fae512717b632a4f37f0fcce16b75d59143cea
>> > >
>> > > Release Notes :
>> > >
>> >
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12321626=12345703
>> > >
>> > >
>> > > Keys to verify the Release Candidate :
>> > > https://dist.apache.org/repos/dist/dev/servicecomb/KEYS
>> > >
>> > > Voting will start now ( Tuesday, 27nd August, 2019) and will remain
>> open
>> > > for at-least 72 hours, Request all PMC members to give their vote.
>> > >
>> > > [ ] +1 Release this package as 0.1.0
>> > > [ ] +0 No Opinion
>> > > [ ] -1 Do not release this package because
>> > >
>> > > On the behalf of ServiceComb Team
>> > >
>> > >
>> > > Best Wishes & Regards
>> > > ---
>> > > Mabin
>> >
>>
>

Re: [VOTE] Release Apache ServiceComb Toolkit version 0.1.0

[Bin Ma]

+1


Best Wishes & Regards
---
Mabin



Liubao (A)  于2019年8月29日周四 上午10:42写道：

> +1
>
>
>
> --
> 刘宝 Liu Bao
> Mobile: +86-18664569778
> Email: bao@huawei.com<mailto:bao@huawei.com>
> 发件人：Bin Ma 
> 收件人：dev@servicecomb.apache.org 
> 时间：2019-08-28 20:53:40
> 主题Re: [VOTE] Release Apache ServiceComb Toolkit version 0.1.0
>
> Hi @Asif,
>
> ServiceComb Toolkit provides a maven plugin for the user, so it only
> releases source code.
>
>
> Best Wishes & Regards
> ---
> Mabin
>
>
>
> Willem Jiang  于2019年8月28日周三 下午7:36写道：
>
> > +1 binding.
> > I checked:
> > Staging repo looks good.
> > The License and Notice file looks good.
> > I can build the kit from the source.
> >
> > Willem Jiang
> >
> > Twitter: willemjiang
> > Weibo: 姜宁willem
> >
> > On Tue, Aug 27, 2019 at 4:34 PM Bin Ma  wrote:
> > >
> > > Hi All,
> > >
> > > This is a call for Vote to release Apache ServiceComb Toolkit version
> > 0.1.0
> > >
> > >
> > > Release Candidate :
> > >
> >
> https://dist.apache.org/repos/dist/dev/servicecomb/servicecomb-toolkit/0.1.0/rc-01/
> > >
> > >
> > > Staging Repository :
> > >
> >
> https://repository.apache.org/content/repositories/orgapacheservicecomb-1403
> > >
> > >
> > > Release Tag :
> > > https://github.com/apache/servicecomb-toolkit/releases/tag/0.1.0
> > >
> > > Release CommitID : 88fae512717b632a4f37f0fcce16b75d59143cea
> > >
> > > Release Notes :
> > >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12321626=12345703
> > >
> > >
> > > Keys to verify the Release Candidate :
> > > https://dist.apache.org/repos/dist/dev/servicecomb/KEYS
> > >
> > > Voting will start now ( Tuesday, 27nd August, 2019) and will remain
> open
> > > for at-least 72 hours, Request all PMC members to give their vote.
> > >
> > > [ ] +1 Release this package as 0.1.0
> > > [ ] +0 No Opinion
> > > [ ] -1 Do not release this package because
> > >
> > > On the behalf of ServiceComb Team
> > >
> > >
> > > Best Wishes & Regards
> > > ---
> > > Mabin
> >
>

Re: [VOTE] Release Apache ServiceComb Toolkit version 0.1.0

[Bin Ma]

Hi @Asif,

ServiceComb Toolkit provides a maven plugin for the user, so it only
releases source code.


Best Wishes & Regards
---
Mabin



Willem Jiang  于2019年8月28日周三 下午7:36写道：

> +1 binding.
> I checked:
> Staging repo looks good.
> The License and Notice file looks good.
> I can build the kit from the source.
>
> Willem Jiang
>
> Twitter: willemjiang
> Weibo: 姜宁willem
>
> On Tue, Aug 27, 2019 at 4:34 PM Bin Ma  wrote:
> >
> > Hi All,
> >
> > This is a call for Vote to release Apache ServiceComb Toolkit version
> 0.1.0
> >
> >
> > Release Candidate :
> >
> https://dist.apache.org/repos/dist/dev/servicecomb/servicecomb-toolkit/0.1.0/rc-01/
> >
> >
> > Staging Repository :
> >
> https://repository.apache.org/content/repositories/orgapacheservicecomb-1403
> >
> >
> > Release Tag :
> > https://github.com/apache/servicecomb-toolkit/releases/tag/0.1.0
> >
> > Release CommitID : 88fae512717b632a4f37f0fcce16b75d59143cea
> >
> > Release Notes :
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12321626=12345703
> >
> >
> > Keys to verify the Release Candidate :
> > https://dist.apache.org/repos/dist/dev/servicecomb/KEYS
> >
> > Voting will start now ( Tuesday, 27nd August, 2019) and will remain open
> > for at-least 72 hours, Request all PMC members to give their vote.
> >
> > [ ] +1 Release this package as 0.1.0
> > [ ] +0 No Opinion
> > [ ] -1 Do not release this package because
> >
> > On the behalf of ServiceComb Team
> >
> >
> > Best Wishes & Regards
> > ---
> > Mabin
>

[VOTE] Release Apache ServiceComb Toolkit version 0.1.0

[Bin Ma]

Hi All,

This is a call for Vote to release Apache ServiceComb Toolkit version 0.1.0


Release Candidate :
https://dist.apache.org/repos/dist/dev/servicecomb/servicecomb-toolkit/0.1.0/rc-01/


Staging Repository :
https://repository.apache.org/content/repositories/orgapacheservicecomb-1403


Release Tag :
https://github.com/apache/servicecomb-toolkit/releases/tag/0.1.0

Release CommitID : 88fae512717b632a4f37f0fcce16b75d59143cea

Release Notes :
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12321626=12345703


Keys to verify the Release Candidate :
https://dist.apache.org/repos/dist/dev/servicecomb/KEYS

Voting will start now ( Tuesday, 27nd August, 2019) and will remain open
for at-least 72 hours, Request all PMC members to give their vote.

[ ] +1 Release this package as 0.1.0
[ ] +0 No Opinion
[ ] -1 Do not release this package because

On the behalf of ServiceComb Team


Best Wishes & Regards
---
Mabin

Re: Apache project meetup in ShangHai Sep 21st

[Bin Ma]

+1, It's a good news,looking forward to the meeting.


Best Wishes & Regards
---
Mabin



Willem Jiang  于2019年8月21日周三 下午2:52写道：

> Hi JB，
>
> Thanks for the support, you are in my top guest list, maybe next time
> I will send you my invitation.
>
> Regards,
>
> Willem Jiang
>
> Twitter: willemjiang
> Weibo: 姜宁willem
>
> On Wed, Aug 21, 2019 at 2:46 PM Jean-Baptiste Onofré 
> wrote:
> >
> > Hi !
> >
> > That's a good idea ! Unfortunately I can't be there this time, but
> > definitely a supporter of this meetup !
> >
> > Regards
> > JB
> >
> > On 21/08/2019 04:54, Willem Jiang wrote:
> > > Hi,
> > >
> > > We would like to hold a meetup in ShangHai Sep 21st by inviting some
> > > Apache members ( Craig Russell, Justin Mclean, Willem Jiang）and some
> > > apache projects committers in China like we did last year.
> > >
> > > We hold this meetup can help Apache projects to know each other in
> > > China. As there are lot of Apache project committers are based in east
> > > China,  we can leverage this opportunity to let Apache know better
> > > about the committers in China and give us some advice to build up
> > > health community.
> > >
> > > The discussion topic of meetup could be:
> > > How to be the TLP of ASF?
> > > How can we help ASF know better about China?
> > > How can we help more Chinese know better about ASF?
> > >
> > > If you are interested about this meetup, please drop an email to
> > > ningjiang AT apache.org with the information of your name, phone
> > > number and the project name before Sep 18th 12 PM. We will send you
> > > detail information of the meetup later.
> > >
> > > Please forward the mail to your friend who may be interested about
> this event.
> > >
> > > Willem
> > >
> >
> > --
> > Jean-Baptiste Onofré
> > jbono...@apache.org
> > http://blog.nanthrax.net
> > Talend - http://www.talend.com
>

Re: [ANN] New ServiceComb committer:Ma Bin(马彬)

[Bin Ma]

Thanks, very glad to be an Apache ServiceComb committer and grow with the
ServiceComb community together


Best Wishes & Regards
---
Mabin



victor chan  于2019年8月2日周五 下午4:01写道：

> Congratulations！ victor chan 邮箱：victorchan...@gmail.com 签名由 网易邮箱大师 定制
> 在2019年08月02日 15:54，Zen Lin 写道： Please join me and the rest of the
> ServiceComb PMC members in welcoming our new ServiceComb committer: Ma
> Bin(马彬). Ma Bin has been doing contribution in  the ServiceComb community
> for  more than two years, include three parts, a. Contributed ServiceComb
> code, include code in java-chassis, saga and website, Recently donate his
> servicecomb-toolkit[2] to servicecomb and commit on it frequently. b.
> Introduced ServiceComb to our first batch of users and support them to use
> it. c. Did Speeches to promote the ServiceComb more than 30 times in many
> different places. Congratulations to Tian Xiaoliang! Welcome! The Apache
> ServiceComb PMC.

Re: [PROPOSAL] create e-commerce project as a ServiceComb sample project for user guiding purpose.

[Bin Ma]

It sounds a good idea : )

Can you briefly show us the design how to use ServiceComb to build
an e-commerce? thks


Best Wishes & Regards
---
Mabin



郑志鹏  于2019年7月22日周一 上午10:26写道：

> Thanks for you suggestions. I will make sure the is licensed under Apache
> License and the libraries it uses is compatible. And I will make the
> document as detailed as possible.
>
> Liubao (A)  于2019年7月20日周六 下午10:55写道：
>
> > Any samples to use ServiceComb is preferred. I have some questions before
> > you contribute the code:
> >
> >* Make sure the project is licensed under Apache License and the
> > libraries it uses is compatible.
> >* Samples are intended to help users how to program. I'd prefer the
> > e-commerce project have some documents to describe the project and the
> > techniches and best proctics.
> >
> > -邮件原件-
> > 发件人: 郑志鹏 [mailto:aleczhen...@gmail.com]
> > 发送时间: 2019年7月19日 17:01
> > 收件人: dev@servicecomb.apache.org
> > 主题: [PROPOSAL] create e-commerce project as a ServiceComb sample project
> > for user guiding purpose.
> >
> > Hi, All
> >
> > Recently, I communicated with some ServiceComb new users, they want an
> > e-commerce system ServiceComb sample project with real business
> background.
> > They think with this demo they can learn ServiceComb’s abilities and
> > usages *more efficiently*.
> >
> > Then I found this project https://github.com/apache/servicecomb-samples.
> > So I want to develop an e-commerce system demo and *devote* it to this
> > project as this project’s sub-project.
> > --
> > The business background of my planing project:
> >
> > Traditionally, a real estate developer in china will show their nearing
> > completion buildings to the customers for a couple of days, then
> determine
> > an open sale time for all customers to make real deal offline. Those
> > customers have to get to sale place long before the open sale time and
> > queue up,because only in this way they get the chances to pick the
> > apartment which they like mostly. So recently, more and more real estate
> > developers begin to build an online apartments/houses open sale system.
> The
> > e-commerce system help their customer to pick the houses more easily and
> > more fairly. This is the system which I plan to build with ServiceComb.
> > Why I choose this project as a guiding sample of ServiceComb?
> >
> > Real estate developers use this system to make a deal with their customer
> > online. So, yes! This is a real e-commerce system with real commercial
> > value. But this is also a real simple e-commerce system which has no
> > payment and shipping module. So Its simplicity is good for the guiding
> > purpose. Meanwhile, because these trading subjects of this system are
> very
> > expensive，and there will be high QPS when the open sale time just
> arrives.
> > So There are high requirements for the system’s scalability, availability
> > and robustness.It’s an applicable project to show ServiceComb’s
> abilities.
> > Any questions and suggestions?
> >
> > --
> > Best Wishes & Regards
> > ———
> > Alec Zheng
> >
>
>
> --
> Best Wishes & Regards
> ———
> Alec Zheng
>

Re: [VOTE]Service mesh proposal

[Bin Ma]

+1


Best Wishes & Regards
---
Mabin



yhs0092  于2019年6月22日周六 上午11:33写道：

> +1
>
>
> Yours sincerely
>
>
> Yao Haishi
> yhs0...@163.com
>
>
> On 6/21/2019 21:54，Willem Jiang wrote：
> +1.
>
> Willem Jiang
>
> Twitter: willemjiang
> Weibo: 姜宁willem
>
> On Fri, Jun 21, 2019 at 4:41 PM Xiaoliang Tian 
> wrote:
>
> Hi All,
> this is a call for vote to bring service mesh called "mesher" into
> Apache Software Foundation (ASF) as ServiceComb's sub-project.
>
>
> Voting will start now ( Wednesday, 5th June, 2019) and will
> remain open for at-least 72 hours, Request all PMC members to
> give their vote.
> [ ] +1 Accept
> [ ] +0 No Opinion
> [ ] -1 Reject because...
>

Re: [VOTE]Have a booth and Holding an Apache ServiceComb Meetup as a Co-located Event, in KubeCon & CloudNativeCon Summit China 2019

[Bin Ma]

+1


Best Wishes & Regards
---
Mabin



Mohammad Asif Siddiqui  于2019年6月11日周二 上午9:54写道：

> +1 binding
> Best of Luck for meetup
>
> Regards
> Asif
>
> On 2019/06/11 01:52:22, Zen Lin  wrote:
> > Hi All,
> > This is a call for Vote to have a Apache ServiceComb booth and hold an
> > Apache ServiceComb  Meetup as a Co-located Event , in KubeCon &
> > CloudNativeCon Summit China 2019, as discussed in the proposal [1].
> >
> > Voting will start now (Tuesday, 11th June, 2019) and will remain open for
> > at-least 72 hours, Request PMC members and contributors to give their
> vote.
> >
> > [ ] +1 Accept
> > [ ] +0 No Opinion
> > [ ] -1 Reject because...
> >
> > [1]
> >
> http://mail-archives.apache.org/mod_mbox/servicecomb-dev/201906.mbox/%3CCAH9eK8QEtrgPF9jqwZO%2BKRk9gEMd_U2DYMe2wAgBC30gD-Sc%2Bg%40mail.gmail.com%3E
> >
> >
> > Best Regards,
> > ---
> > Zen Lin
> > zenlintechnofr...@gmail.com
> > Focused on Micro Service and Apache ServiceComb
> >
>

Re: [PROPOSAL]a new project mesher for servicecomb

[Bin Ma]

+1

I'm glad to hear this. I think that the Mesher can be used as a
multi-language sub-project or component, and provide a unified user
interface for service registration and discovery, governance, configuration
to users.So that ServiceComb can form a more diversified solution, bringing
multi-optional microservice solution to users with different scenarios and
requirement.


Best Wishes & Regards
---
Mabin



Mohammad Asif Siddiqui  于2019年6月11日周二 上午9:49写道：

> +1
>
> I strongly suggest to add Mesher as a part of ServiceComb as it will make
> ServiceComb a fully fledged microservice framework with support to all
> languages by either java-chassis or by mesher.
>
> Regards
> Asif
>
> On 2019/06/10 06:11:01, Xiaoliang Tian  wrote:
> > Hi All,
> >
> > Service mesh is a solution for microservice, mesher is a service mesh
> > implementation.
> >
> > if servicecomb introduce mesher, it will get some benifits.
> >
> > 1. user of servicecomb can choose any language and leverage same service
> > center and govenance policy.
> >
> > 2. user can gain better performance by using java chassis and mesher,
> than
> > user use service mesh solution only.
> >
> > the first one is most important reason why service mesh is important to
> > service comb
> >
> > The mesher feature has been finished [1]
> >
> > there is the list of features:
> > 1. service discovery, load balancing, circuit breaker, rate limiting,
> most
> > of features that java chassis has
> > 2. An admin API to expose runtime imformation of mesher
> > 3. support grpc and http1 and http2
> > 4. support transparent TLS communication
> > 5. run as a sidecar proxy for a service
> > 6. a sidecar injector to automattically inject mesher into k8s pod
> >
> > [1]  https://github.com/go-mesh/mesher
> >
> > Regards
> >
>

[RESULT][VOTE] Toolkit donation proposal

[Bin Ma]

Here is the result of voting the Toolkit donation[1]
There are 6 +1
Willem Jiang, Liubao, Zen Lin, wjm wjm, yhs0092, Zheng Feng, victor chan.
So the vote passed.

[1]
http://mail-archives.apache.org/mod_mbox/servicecomb-dev/201906.mbox/%3CCAFZODqO%3DqsZA%3DnAu8D7%2BpeR1gUYq-6GSV6aeyrkcz1xJjZDgeg%40mail.gmail.com%3E


Best Wishes & Regards
---
Mabin

Re: [VOTE] Toolkit donation proposal

[Bin Ma]

Hi All,

This vote is closed now, thanks all for participating in  the voting.

I will announce the results soon.


Best Wishes & Regards
---
Mabin




victor chan  于2019年6月10日周一 下午5:39写道：

> +1 victor chan 邮箱：victorchan...@gmail.com 签名由 网易邮箱大师 定制 On 06/10/2019
> 10:30, yhs0092 wrote: +1(binding) Good work! Yours sincerely Yao Haishi
> yhs0...@163.com On 6/10/2019 10:23，wjm wjm wrote： +1
> Zen Lin  于2019年6月10日周一 上午9:49写道： +1
> (binding) Best Regards, --- Zen Lin zenlintechnofr...@gmail.com Focused
> on Micro Service and Apache ServiceComb Liubao (A) 
> 于2019年6月10日周一 上午9:09写道： +1 -邮件原件- 发件人: Willem Jiang [mailto:
> willem.ji...@gmail.com] 发送时间: 2019年6月6日 19:03 收件人: dev <
> dev@servicecomb.apache.org> 主题: Re: [VOTE] Toolkit donation proposal My
> +1 (binding), it's great to see that we bring more tools to help user to
> build their applications. Willem Jiang Twitter: willemjiang Weibo: 姜宁willem
> On Thu, Jun 6, 2019 at 6:57 PM Bin Ma  wrote: Hi
> All, This is a call for a Vote to bring Toolkit[1] codebase into the Apache
> Software Foundation (ASF) as ServiceComb's sub-project. Reference: the mail
> thread link for the previous discussion[2]. Voting will start now (
> Wednesday, 5th June, 2019) and will remain open for at-least 72 hours,
> Request all PMC members to give their vote. [ ] +1 Accept [ ] +0 No Opinion
> [ ] -1 Reject because... [1] https://github.com/MabinGo/toolkit [2]
> https://lists.apache.org/thread.html/bba43e0116160dbdc7d1443c995a2b6fd
> c72f5e4e91f1e5208afc230@%3Cdev.servicecomb.apache.org%3E# Best Wishes &
> Regards --- Mabin

Re: Proposal for Holding an Apache ServiceComb Meetup as a Co-located Event in KubeCon & CloudNativeCon Summit China 2019

[Bin Ma]

+1


Best Wishes & Regards
---
Mabin



孙森  于2019年6月10日周一 下午5:50写道：

> +1
>
> victor chan  于2019年6月10日周一 下午5:41写道：
>
> > +1 victor chan 邮箱：victorchan...@gmail.com 签名由 网易邮箱大师 定制 On 06/10/2019
> > 16:32, yhs0092 wrote: +1 Yours sincerely Yao Haishi yhs0...@163.com On
> > 6/10/2019 16:02，Zheng Feng wrote： +1 for holding this
> > meetup ! Zen Lin  于2019年6月10日周一 上午10:08写道：
> > This is a Proposal for holding a Co-Located Event in KubeCon &
> > CloudNativeCon Summit China 2019 to help building ServiceComb's
> community.
> > My suggestion is to hold a Meetup named "Apache ServiceComb Meetup Hosted
> > by Huawei", to share technologies and user cases of ServiceComb. Because
> > the time is tight, I have already talked to Huawei to get free resources
> > and sposorship for the meetup. Details of the plan is listed below, -
> What
> > is the topic focus of the event? Topics are focused on  Apache Way
> related
> > topics, user-practices /technologies topics of Apache ServiceComb . - Who
> > is organising the event? PMCs of ServiceComb (incubating) are the
> organizer
> > - When is the event? June 24 - How many attendees are expected? 60~100 -
> > How much PMC involvement is there already? 3 - Which marks are requested?
> > Two marks are requested, 1. Name of "Apache ServiceComb Meetup " 2.
> > "Powered By" Apache logo of Apache ServiceComb - Is this for profit or
> > non-profit? (See "Event Profits And Donations")? non-profit. By the way,
> I
> > also suggest to have a booth about Apache ServiceComb in KubeCon &
> > CloudNativeCon Summit China 2019. Now, I would like to get suggestions
> from
> > you guys, If it is agreed , I am going to create a vote for it. Best
> > Regards, --- Zen Lin zenlintechnofr...@gmail.com Focused on Micro
> Service
> > and Apache ServiceComb
>

[VOTE] Toolkit donation proposal

[Bin Ma]

Hi All,

This is a call for a Vote to bring Toolkit[1] codebase into the
Apache Software Foundation (ASF) as ServiceComb's sub-project.

Reference: the mail thread link for the previous discussion[2].

Voting will start now ( Wednesday, 5th June, 2019) and will
remain open for at-least 72 hours, Request all PMC members to
give their vote.

[ ] +1 Accept
[ ] +0 No Opinion
[ ] -1 Reject because...

[1] https://github.com/MabinGo/toolkit
[2]
https://lists.apache.org/thread.html/bba43e0116160dbdc7d1443c995a2b6fdc72f5e4e91f1e5208afc230@%3Cdev.servicecomb.apache.org%3E#


Best Wishes & Regards
---
Mabin

Re: [PROPOSAL]create a new project for servicecomb toolkit

[Bin Ma]

OK, I will start a vote for Toolkit donation.


Best Wishes & Regards
---
Mabin



Willem Jiang  于2019年6月3日周一 下午5:59写道：

> @mabin1...@gmail.com
>
> Could you start a vote for it?
> Here is an vote template[1] ( it's for committer vote, you can change
> it to your proposal).
> Please ping me if you need any help from my side.
>
> [1]https://community.apache.org/newcommitter.html#committer-vote-template
>
> Willem Jiang
>
> Twitter: willemjiang
> Weibo: 姜宁willem
>
> On Mon, Jun 3, 2019 at 5:49 PM Willem Jiang 
> wrote:
> >
> > It's a good idea to provide tools to help user to generate the
> > application of ServiceComb java-chassis.
> > As there are some code already in the github[1], we need to go through
> > the IP Clearance Process[2].
> >
> > We can take the SkyWalking recent donation[3] as an example.
> >
> > [1] https://github.com/MabinGo/toolkit
> > [2] https://incubator.apache.org/ip-clearance/
> > [3]
> https://incubator.apache.org/ip-clearance/skywalking-rocketbot-ui.html
> >
> >
> > Willem Jiang
> >
> > Twitter: willemjiang
> > Weibo: 姜宁willem
> >
> > On Thu, May 30, 2019 at 4:37 PM Bin Ma  wrote:
> > >
> > > Currently, the toolkit project provides the function to develop
> > > microservices based on contracts.
> > >
> > > My opinion, the toolkit project is a collection of tools.
> > > For example, archetypes module of ServiceComb java-chassiswe can be
> > > migrated into toolkit project.
> > > In the future, remote debugging tools, automated test frameworks, etc.
> can
> > > be provided in the toolkit project
> > > to support connecting with popular microservice frameworks such as
> > > ServiceComb and SpringCloud.
> > >
> > > Any suggestions? @all
> > >
> > >
> > > Best Wishes & Regards
> > > ---
> > > Mabin
> > >
> > >
> > >
> > > Zen Lin  于2019年5月30日周四 上午10:27写道：
> > >
> > > > +1
> > > > It is quite important to provide a contract tool kit in microservice
> field.
> > > > I have one question that, this repo only contains the tools related
> to
> > > > contract, or it also contains other tools in future?
> > > > I mean, this will affact the naming of the repo.
> > > > Any thoughts?
> > > >
> > > > Best Regards,
> > > > ---
> > > > Zen Lin
> > > > zenlintechnofr...@gmail.com
> > > > Focused on Micro Service and Apache ServiceComb
> > > >
> > > >
> > > > wjm wjm  于2019年5月29日周三 下午9:15写道：
> > > >
> > > > > +1
> > > > >
> > > > > Bin Ma  于2019年5月28日周二 下午7:37写道：
> > > > >
> > > > > > Thanks for your suggestions, I will get the scenarios you
> provided and
> > > > > put
> > > > > > into the roadmap of the toolkit to consider how to implement.
> > > > > >
> > > > > >
> > > > > > Best Wishes & Regards
> > > > > > ---
> > > > > > Mabin
> > > > > >
> > > > > >
> > > > > >
> > > > > > Liubao (A)  于2019年5月28日周二 上午9:52写道：
> > > > > >
> > > > > > > Very glad to hear this proposal. I have a draft idea[1] of
> contract
> > > > > based
> > > > > > > software engineering based on tools.
> > > > > > > And a brief idea[2] of managing contract of all microservices
> by web.
> > > > > > >
> > > > > > >
> > > > > > > [1]
> > > > https://bbs.huaweicloud.com/blogs/c998f257673711e9bd5a7ca23e93a891
> > > > > > > [2] https://zhuanlan.zhihu.com/p/64064246
> > > > > > >
> > > > > > >
> > > > > > > -邮件原件-
> > > > > > > 发件人: Bin Ma [mailto:mabin1...@gmail.com]
> > > > > > > 发送时间: 2019年5月27日 11:00
> > > > > > > 收件人: dev@servicecomb.apache.org
> > > > > > > 主题: [PROPOSAL]create a new project for servicecomb toolkit
> > > > > > >
> > > > > > > Hi All,
> > > > > > >
> > > > > > > In the process of supporting users to do micro-service
> > > > transformation,

Re: [PROPOSAL]create a new project for servicecomb toolkit

[Bin Ma]

Currently, the toolkit project provides the function to develop
microservices based on contracts.

My opinion, the toolkit project is a collection of tools.
For example, archetypes module of ServiceComb java-chassiswe can be
migrated into toolkit project.
In the future, remote debugging tools, automated test frameworks, etc. can
be provided in the toolkit project
to support connecting with popular microservice frameworks such as
ServiceComb and SpringCloud.

Any suggestions? @all


Best Wishes & Regards
---
Mabin



Zen Lin  于2019年5月30日周四 上午10:27写道：

> +1
> It is quite important to provide a contract tool kit in microservice field.
> I have one question that, this repo only contains the tools related to
> contract, or it also contains other tools in future?
> I mean, this will affact the naming of the repo.
> Any thoughts?
>
> Best Regards,
> ---
> Zen Lin
> zenlintechnofr...@gmail.com
> Focused on Micro Service and Apache ServiceComb
>
>
> wjm wjm  于2019年5月29日周三 下午9:15写道：
>
> > +1
> >
> > Bin Ma  于2019年5月28日周二 下午7:37写道：
> >
> > > Thanks for your suggestions, I will get the scenarios you provided and
> > put
> > > into the roadmap of the toolkit to consider how to implement.
> > >
> > >
> > > Best Wishes & Regards
> > > ---
> > > Mabin
> > >
> > >
> > >
> > > Liubao (A)  于2019年5月28日周二 上午9:52写道：
> > >
> > > > Very glad to hear this proposal. I have a draft idea[1] of contract
> > based
> > > > software engineering based on tools.
> > > > And a brief idea[2] of managing contract of all microservices by web.
> > > >
> > > >
> > > > [1]
> https://bbs.huaweicloud.com/blogs/c998f257673711e9bd5a7ca23e93a891
> > > > [2] https://zhuanlan.zhihu.com/p/64064246
> > > >
> > > >
> > > > -邮件原件-
> > > > 发件人: Bin Ma [mailto:mabin1...@gmail.com]
> > > > 发送时间: 2019年5月27日 11:00
> > > > 收件人: dev@servicecomb.apache.org
> > > > 主题: [PROPOSAL]create a new project for servicecomb toolkit
> > > >
> > > > Hi All,
> > > >
> > > > In the process of supporting users to do micro-service
> transformation,
> > we
> > > > encountered the following problems:
> > > > 1. For users who integrate multi-vendor applications, because the
> > > > development languages, habits, and frameworks of different vendors
> are
> > > > different, the entire system data and service standards are
> > inconsistent,
> > > > users are difficult to integrate, and it is difficult to manage and
> > > control
> > > > the final delivery quality.
> > > > 2. For users who have evolved from legacy systems to microservices
> > > > architectures, additional learning and understanding of the
> > > > microservices-related framework details is required before the
> > > > microservices project can be designed, built, and developed according
> > to
> > > > the selected microservices framework. For users, Need to be
> distracted
> > to
> > > > focus on things outside the business.
> > > >
> > > > Based on the above reasons, combined with ServiceComb's service
> > contract
> > > > management capabilities, we have implemented a contract-based
> > > microservice
> > > > development toolkit[1] with the goal of rapidly building
> microservices
> > > > projects based on popular microservices frameworks and programming
> > > models,
> > > > and supporting the automatic generation of contracts,code and
> > > documentation
> > > > to help users reduce micro-service entry costs, focus on business
> > > > development, and improve legacy system reconfiguration and
> development
> > > > efficiency during the microservice transformation phase.
> > > >
> > > > The framework and basic function of toolkit has been finished [1]
> > > >
> > > > The function of the toolkit is as follows:
> > > > 1. Code extraction service contract
> > > > In applications developed based on the SpringMVC/POJO/JAX-RS model,
> > > > one-click generation of service contract files conforming to the
> > OpenAPI
> > > > specification.
> > > > 2. Service Contract Generation Micro Service Engineering Enter a
> > service
> > > > contract that conforms to the OpenAPI specification, one-click
> > generation
> > > > of a microservice project with ServiceComb/SpringCloud/Swagger as the
> > > base
> > > > microservice framework and SpringMVC/POJO/JAX-RS or SpringBoot as
> > > > programming model .
> > > > 3. Service contract and code consistency check Verify that the actual
> > > > implementation of the application (such as the data and service API)
> is
> > > > consistent with the agreed service contract description.
> > > > 4. Service contract / code generation document Enter a service
> contract
> > > > that conforms to the OpenAPI specification, one-click generation of a
> > > > document in html/word/pdf format.
> > > >
> > > > [1] https://github.com/MabinGo/toolkit
> > > >
> > > >
> > > > Best Wishes & Regards
> > > > ---
> > > > Mabin
> > > >
> > >
> >
>

Re: [PROPOSAL]create a new project for servicecomb toolkit

[Bin Ma]

Thanks for your suggestions, I will get the scenarios you provided and put
into the roadmap of the toolkit to consider how to implement.


Best Wishes & Regards
---
Mabin



Liubao (A)  于2019年5月28日周二 上午9:52写道：

> Very glad to hear this proposal. I have a draft idea[1] of contract based
> software engineering based on tools.
> And a brief idea[2] of managing contract of all microservices by web.
>
>
> [1] https://bbs.huaweicloud.com/blogs/c998f257673711e9bd5a7ca23e93a891
> [2] https://zhuanlan.zhihu.com/p/64064246
>
>
> -邮件原件-
> 发件人: Bin Ma [mailto:mabin1...@gmail.com]
> 发送时间: 2019年5月27日 11:00
> 收件人: dev@servicecomb.apache.org
> 主题: [PROPOSAL]create a new project for servicecomb toolkit
>
> Hi All,
>
> In the process of supporting users to do micro-service transformation, we
> encountered the following problems:
> 1. For users who integrate multi-vendor applications, because the
> development languages, habits, and frameworks of different vendors are
> different, the entire system data and service standards are inconsistent,
> users are difficult to integrate, and it is difficult to manage and control
> the final delivery quality.
> 2. For users who have evolved from legacy systems to microservices
> architectures, additional learning and understanding of the
> microservices-related framework details is required before the
> microservices project can be designed, built, and developed according to
> the selected microservices framework. For users, Need to be distracted to
> focus on things outside the business.
>
> Based on the above reasons, combined with ServiceComb's service contract
> management capabilities, we have implemented a contract-based microservice
> development toolkit[1] with the goal of rapidly building microservices
> projects based on popular microservices frameworks and programming models,
> and supporting the automatic generation of contracts,code and documentation
> to help users reduce micro-service entry costs, focus on business
> development, and improve legacy system reconfiguration and development
> efficiency during the microservice transformation phase.
>
> The framework and basic function of toolkit has been finished [1]
>
> The function of the toolkit is as follows:
> 1. Code extraction service contract
> In applications developed based on the SpringMVC/POJO/JAX-RS model,
> one-click generation of service contract files conforming to the OpenAPI
> specification.
> 2. Service Contract Generation Micro Service Engineering Enter a service
> contract that conforms to the OpenAPI specification, one-click generation
> of a microservice project with ServiceComb/SpringCloud/Swagger as the base
> microservice framework and SpringMVC/POJO/JAX-RS or SpringBoot as
> programming model .
> 3. Service contract and code consistency check Verify that the actual
> implementation of the application (such as the data and service API) is
> consistent with the agreed service contract description.
> 4. Service contract / code generation document Enter a service contract
> that conforms to the OpenAPI specification, one-click generation of a
> document in html/word/pdf format.
>
> [1] https://github.com/MabinGo/toolkit
>
>
> Best Wishes & Regards
> ---
> Mabin
>

[PROPOSAL]create a new project for servicecomb toolkit

[Bin Ma]

Hi All,

In the process of supporting users to do micro-service transformation, we
encountered the following problems:
1. For users who integrate multi-vendor applications, because the
development languages, habits, and frameworks of different vendors are
different, the entire system data and service standards are inconsistent,
users are difficult to integrate, and it is difficult to manage and control
the final delivery quality.
2. For users who have evolved from legacy systems to microservices
architectures, additional learning and understanding of the
microservices-related framework details is required before the
microservices project can be designed, built, and developed according to
the selected microservices framework. For users, Need to be distracted to
focus on things outside the business.

Based on the above reasons, combined with ServiceComb's service contract
management capabilities, we have implemented a contract-based microservice
development toolkit[1] with the goal of rapidly building microservices
projects based on popular microservices frameworks and programming models,
and supporting the automatic generation of contracts,code and documentation
to help users reduce micro-service entry costs, focus on business
development, and improve legacy system reconfiguration and development
efficiency during the microservice transformation phase.

The framework and basic function of toolkit has been finished [1]

The function of the toolkit is as follows:
1. Code extraction service contract
In applications developed based on the SpringMVC/POJO/JAX-RS model,
one-click generation of service contract files conforming to the OpenAPI
specification.
2. Service Contract Generation Micro Service Engineering
Enter a service contract that conforms to the OpenAPI specification,
one-click generation of a microservice project with
ServiceComb/SpringCloud/Swagger as the base microservice framework and
SpringMVC/POJO/JAX-RS or SpringBoot as programming model .
3. Service contract and code consistency check
Verify that the actual implementation of the application (such as the data
and service API) is consistent with the agreed service contract description.
4. Service contract / code generation document
Enter a service contract that conforms to the OpenAPI specification,
one-click generation of a document in html/word/pdf format.

[1] https://github.com/MabinGo/toolkit


Best Wishes & Regards
---
Mabin

Re: Board Report of ServiceComb

[Bin Ma]

OK, updated and added the reference link as below,

In community operations and promotional activities in December,
1. We participated in three[1] open source exchange conferences and
delivered five times keynote speeches to promote ServiceComb.
2. Apache ServiceComb won the first prize of China's outstanding open
source project organized by China Open Source Cloud Alliance. reference
news link[2]
3. Apache ServiceComb community joint Chuanzhiboke Education Technology
sub-brand Itheima, Boxuegu and Wisdom Gathering release Apache ServiceComb
tutorial. reference news link[3]

[1]
1.China Alliance of Industrial Internet Conference, reference link
http://www.sohu.com/a/278199186_774700
2.China Cloud Computing Standards and Applications Conference, reference
link http://www.zhiding.cn/special/8th_Cloud_Conference#Agenda
3.Chuanzhiboke Carnival and Apache ServiceComb Meetup, reference link
https://mp.weixin.qq.com/s/GzWuPHpyZut4H0cuSfTOYA
[2]https://blog.csdn.net/ServiceComb/article/details/84989759
[3]https://www.toutiao.com/i6639922959018361348/



Best Wishes & Regards
---
Mabin



Willem Jiang  于2019年1月8日周二 上午10:11写道：

> Hi Mabin,
>
> It could be more useful if we could include the news link or the reports.
>
> Willem Jiang
>
> Twitter: willemjiang
> Weibo: 姜宁willem
>
> On Tue, Jan 8, 2019 at 10:03 AM Bin Ma  wrote:
> >
> > Please help to review whether the following content needs to be presented
> > in the report,thks
> >
> > In community operations and promotional activities in December,
> > 1. We participated in three[1] open source exchange conferences and
> > delivered five times keynote speeches to promote ServiceComb.
> > 2. Apache ServiceComb won the first prize of China's outstanding open
> > source project organized by China Open Source Cloud Alliance.
> > 3. Apache ServiceComb community joint Chuanzhiboke Education Technology
> > sub-brand Itheima, Boxuegu and Wisdom Gathering release Apache
> ServiceComb
> > tutorial.
> >
> > [1]
> > 1.China Alliance of Industrial Internet Conference
> > 2.China Cloud Computing Standards and Applications Conference
> > 3.Chuanzhiboke Carnival and Apache ServiceComb Meetup
> >
> >
> > Best Wishes & Regards
> > ---
> > Mabin
> >
> >
> >
> > Jean-Baptiste Onofré  于2019年1月6日周日 下午1:39写道：
> >
> > > +1
> > >
> > > it sounds good to me.
> > >
> > > Regards
> > > JB
> > >
> > > On 04/01/2019 09:02, Willem Jiang wrote:
> > > > Here is the draft of the board report this month (We need to submit
> it
> > > > to the board before 9th Jan). Please let me know if any thing is
> > > > missing or you have any questions about it.
> > > >
> > > > ## Description:
> > > >  -  a microservice framework that provides a set of tools and
> > > > components to make development and deployment of cloud applications
> > > > easier.
> > > >
> > > > ## Issues:
> > > >  -  There are no issues requiring board attention at this time.
> > > >
> > > > ## Activity:
> > > >  - ServiceComb PMC did saga-actuator and pack release this month.
> > > >
> > > > ## Health report:
> > > >  - The mails and commits activity are as good as usual.
> > > >
> > > > ## PMC changes:
> > > >
> > > >  - Currently 16 PMC members.
> > > >  - No new PMC members added in the last 3 months
> > > >
> > > > ## Committer base changes:
> > > >
> > > >  - Currently 18 committers.
> > > >
> > > > ## Releases:
> > > >
> > > >  - ServiceComb Pack 0.3.0 was released on Wed Jan 02 2019
> > > >  - ServiceComb Saga Actuator 0.3.0 was released on Tue Dec 18 2018
> > > >
> > > > ## Mailing list activity:
> > > >
> > > > This month there are 1225 emails sent to servicecomb.apache.org by
> 38
> > > > people, divided into 796 topics
> > > >   Top 5 member:
> > > >   GitBox: 541 email(s)
> > > >   ASF GitHub Bot (JIRA): 208 email(s)
> > > >   ningji...@apache.org: 118 email(s)
> > > >   Willem Jiang (JIRA): 105 email(s)
> > > >   liu...@apache.org: 45 email(s)
> > > >
> > > >  - dev@servicecomb.apache.org:
> > > > - This month there are 56 emails sent by 18 people, divided into
> 12
> > > topics.
> > > > - 137 subscribers (up 17 in the last 3 months):
> > > > - 347 emails sent to list (634 in previous quarter)
> > > >
> > > >  - iss...@servicecomb.apache.org:
> > > > - 8 subscribers (up 0 in the last 3 months):
> > > > - 1674 emails sent to list (2708 in previous quarter)
> > > >
> > > > ## JIRA activity:
> > > >
> > > >  - 152 JIRA tickets created in the last 3 months
> > > >  - 153 JIRA tickets closed/resolved in the last 3 months
> > > >
> > > > Willem Jiang
> > > >
> > > > Twitter: willemjiang
> > > > Weibo: 姜宁willem
> > > >
> > >
> > > --
> > > Jean-Baptiste Onofré
> > > jbono...@apache.org
> > > http://blog.nanthrax.net
> > > Talend - http://www.talend.com
> > >
>

Re: Board Report of ServiceComb

[Bin Ma]

+1
Feedback from some users,the report is very useful for users and helps them
understand the ServiceComb community dynamics: )


Best Wishes & Regards
---
Mabin



Zen Lin  于2018年12月7日周五 下午5:42写道：

> +1
> Best Regards,
> ---
> Zen Lin
> zenlintechnofr...@gmail.com
> Focused on Micro Service and Apache ServiceComb
>
>
> wjm wjm  于2018年12月5日周三 下午11:07写道：
>
> > +1
> >
> > Willem Jiang  于2018年12月5日周三 下午6:06写道：
> >
> > > Hi Asif,
> > >
> > > Thanks for the suggestion. I will updated the board report with the
> > > new version of introduction.
> > >
> > > Willem Jiang
> > >
> > > Twitter: willemjiang
> > > Weibo: 姜宁willem
> > >
> > > On Tue, Dec 4, 2018 at 2:04 PM Mohammad Asif Siddiqui
> > >  wrote:
> > > >
> > > > +1
> > > >
> > > > Suggestion :  I guess we can re-visit and update the description of
> > > ServiceComb.( ServiceComb is a full stack microservice framework which
> > > provides a set of SDK's, Service Registry and Transaction Management
> > > Services for rapid development of Cloud native applications.)
> > > >
> > > > Regards
> > > > Asif
> > > >
> > > > On 2018/12/03 15:18:41, Jean-Baptiste Onofré 
> wrote:
> > > > > +1
> > > > >
> > > > > it looks good to me.
> > > > >
> > > > > Thanks,
> > > > > Regards
> > > > > JB
> > > > >
> > > > > On 03/12/2018 09:44, Willem Jiang wrote:
> > > > > > Hi Team,
> > > > > >
> > > > > > Here is the draft of the board report this month (We need to
> submit
> > > it
> > > > > > to the board before 12 Dec). Please let me know if any thing is
> > > > > > missing or you have any questions about it.
> > > > > >
> > > > > > ## Description:
> > > > > >  -  a microservice framework that provides a set of tools and
> > > > > > components to make development and deployment of cloud
> applications
> > > > > > easier.
> > > > > >
> > > > > > ## Issues:
> > > > > >  -  There are no issues requiring board attention at this time.
> > > > > >
> > > > > > ## Activity:
> > > > > >  - ServiceComb PMC did the first around graduate release this
> > month.
> > > > > >  - We began to hold the online community meeting[1] to discuss
> > about
> > > > > > the roadmap of the project.
> > > > > >  - ServiceComb saga will be rename to pack[2] to provide the TCC
> > and
> > > > > > Saga supports in the pack architecture
> > > > > >
> > > > > >  [1]
> > >
> >
> https://cwiki.apache.org/confluence/display/SERVICECOMB/Community+Meeting
> > > > > >  [2]
> > >
> >
> https://lists.apache.org/thread.html/b80d907cdc4585cea32c3b0258a1b6338bb3ab95118593a928bcfbd6@%3Cdev.servicecomb.apache.org%3E
> > > > > >
> > > > > > ## Health report:
> > > > > >  - The mails and commits activity are as good as usual.
> > > > > >
> > > > > > ## PMC changes:
> > > > > >
> > > > > >  - Currently 16 PMC members.
> > > > > >  - No new PMC members added in the last 3 months
> > > > > >
> > > > > > ## Committer base changes:
> > > > > >
> > > > > >  - Currently 18 committers.
> > > > > >  - New committers:
> > > > > > - Haishi Yao was added as a committer on Tue Nov 13 2018
> > > > > > - Jun Zhao was added as a committer on Tue Nov 13 2018
> > > > > >
> > > > > > ## Releases:
> > > > > >
> > > > > >  - ServiceComb Saga 0.2.1 on Nov 24, 2018
> > > > > >  - ServiceComb Java-Chassis 1.1.0 on Dec 1, 2018
> > > > > >  - ServiceComb Service-Center 1.1.0 on Dec 1, 2018
> > > > > >
> > > > > > ## Mailing list activity:
> > > > > >
> > > > > >  - dev@servicecomb.apache.org:
> > > > > > - This month, there were 197 emails sent by 25 people,
> divided
> > > > > > into 27 topics
> > > > > > - 130 subscribers (up 19 in the last 3 months):
> > > > > > - 485 emails sent to list (535 in previous quarter)
> > > > > >
> > > > > >  - iss...@servicecomb.apache.org:
> > > > > > - 8 subscribers (up 0 in the last 3 months):
> > > > > > - 2145 emails sent to list (2737 in previous quarter)
> > > > > >
> > > > > >
> > > > > > ## JIRA activity:
> > > > > >
> > > > > >  - 176 JIRA tickets created in the last 3 months
> > > > > >  - 179 JIRA tickets closed/resolved in the last 3 months
> > > > > >
> > > > > >
> > > > > >
> > > > > > Willem Jiang
> > > > > >
> > > > > > Twitter: willemjiang
> > > > > > Weibo: 姜宁willem
> > > > > >
> > > > >
> > > > > --
> > > > > Jean-Baptiste Onofré
> > > > > jbono...@apache.org
> > > > > http://blog.nanthrax.net
> > > > > Talend - http://www.talend.com
> > > > >
> > >
> >
>

Re: [VOTE] Rename of Saga repository

[Bin Ma]

May be some user docs should be updated synchronously,such as github
readme,website,user manuals and so on: )


Best Wishes & Regards
---
Mabin



Willem Jiang  于2018年12月4日周二 下午3:12写道：

> FYI， the github repo has been renamed, you can still use the old
> servicecomb-saga to access it.
>
> Willem Jiang
>
> Twitter: willemjiang
> Weibo: 姜宁willem
>
> On Mon, Dec 3, 2018 at 11:30 AM Willem Jiang 
> wrote:
> >
> > FYI， I just created a JIRA [1] for it.
> > [1] https://issues.apache.org/jira/browse/INFRA-17349
> >
> > Willem Jiang
> >
> > Twitter: willemjiang
> > Weibo: 姜宁willem
> > On Mon, Dec 3, 2018 at 9:15 AM Willem Jiang 
> wrote:
> > >
> > > The vote is passed. I will fill a JIRA to rename the git repo.
> > > Here are  6 +1 binding votes: yangbo, jbonofre, zhfeng, asifdxtreme,
> > > liubao, ningjiang.
> > > 2 +1 non-binding votes: ZhaoJun, YangYi.
> > >
> > > Willem Jiang
> > >
> > > Twitter: willemjiang
> > > Weibo: 姜宁willem
> > > On Wed, Nov 28, 2018 at 4:23 PM Willem Jiang 
> wrote:
> > > >
> > > > As we discussion before[1], I'd like call for a vote to rename
> > > > servicecomb-saga git repo to servicecomb-pack.
> > > >
> > > > servicecomb-pack is used to provide the TCC and Saga support in the
> > > > pack architecture, we also need to update the artifact group id  to
> > > > replace saga to pack at the meantime.
> > > >
> > > > Voting will start now ( Wednesday, 28th November, 2018) and will
> > > > remain open for at-least 72 hours, Request all PMC members to give
> > > > their vote.
> > > >
> > > > [ ] +1 Rename of servicecomb-service-saga repository to
> servicecomb-service-pack
> > > > [ ] +0 No Opinion
> > > > [ ] -1 Do not Rename the repository because
> > > >
> > > > [1]
> https://lists.apache.org/thread.html/e7468de26b5c956d615fc7c7dbbf03dbde5aef6ac92f5ef843db1dcb@%3Cdev.servicecomb.apache.org%3E
> > > >
> > > >
> > > > Willem Jiang
> > > >
> > > > Twitter: willemjiang
> > > > Weibo: 姜宁willem
>

Re: [ANN] New ServiceComb committer: Zhao Jun (赵俊)

[Bin Ma]

Congratulations : )


Best Wishes & Regards
---
Mabin



Zheng Feng  于2018年11月13日周二 下午5:53写道：

> welcome on board !
>
> Willem Jiang  于2018年11月13日周二 上午11:54写道：
>
> > Please join me and the rest of the ServiceComb PPMC members in welcoming
> > our
> > new ServiceComb committer: Zhao Jun (赵俊).
> >
> > Yao Haishi contribute the ServiceComb this summer, he is active
> > contributor on saga project and the mailing list, and we look
> > forward to many more contributions in the future.
> >
> > Congratulations to Zhao Jun ! Welcome!
> >
> > Willem Jiang
> >
> > Twitter: willemjiang
> > Weibo: 姜宁willem
> >
>

Re: Release of ServiceComb 1.1.0

[Bin Ma]

If java-chassis and Service Center are ready, it is recommended to publish
first.
Some  issues submitted by users have been resolved in the new release.


Best Wishes & Regards
---
Mabin



Willem Jiang  于2018年11月13日周二 下午5:32写道：

> We are thinking rename the saga project to pack, so it may take a
> little bit longer time for the release.
> I hope we can finished the transaction in this month.
>
> Willem Jiang
>
> Twitter: willemjiang
> Weibo: 姜宁willem
>
> On Tue, Nov 13, 2018 at 5:21 PM Sure  wrote:
> >
> > The Service-Center will also start a new release in 11.19~11.23
> >
> >
> >
> >
> > -- Original --
> > From: wjm wjm 
> > Date: Tue,Nov 13,2018 5:08 PM
> > To: dev 
> > Subject: Re: Release of ServiceComb 1.1.0
> >
> >
> >
> > we can start release process between 11.19~11.23 for java chassis
> >
> > Bin Ma  于2018年11月4日周日 上午12:13写道：
> >
> > > OK,I will try to check the ServiceComb website first
> > >
> > >
> > > Best Wishes & Regards
> > > ---
> > > Mabin
> > >
> > >
> > >
> > > Willem Jiang  于2018年11月2日周五 上午8:30写道：
> > >
> > > > I already submit a JIRA and wait for infra's response.
> > > > But the document it's OK for us do the modification, please send a PR
> > > > if you have time to work on it.
> > > >
> > > > Willem Jiang
> > > >
> > > > Twitter: willemjiang
> > > > Weibo: 姜宁willem
> > > >
> > > > On Thu, Nov 1, 2018 at 8:24 PM Bin Ma  wrote:
> > > > >
> > > > > Hi all,
> > > > >
> > > > > Some community users plan to make courses based on ServiceComb in
> the
> > > > near
> > > > > future, like Itcast,University and so on.
> > > > > So I think it may be speed up the process of renaming the git repo
> name
> > > > and
> > > > > updating the documentation.
> > > > >
> > > > >
> > > > > Best Wishes & Regards
> > > > > ---
> > > > > Mabin
> > > > >
> > > > >
> > > > >
> > > > > Willem Jiang  于2018年10月29日周一 下午12:54写道：
> > > > >
> > > > > > FYI， I fill a JIRA[1] for renaming the git repo.
> > > > > >
> > > > > > [1]https://issues.apache.org/jira/browse/INFRA-17185
> > > > > >
> > > > > > Willem Jiang
> > > > > >
> > > > > > Twitter: willemjiang
> > > > > > Weibo: 姜宁willem
> > > > > > On Sat, Oct 27, 2018 at 10:09 PM Willem Jiang <
> > > willem.ji...@gmail.com>
> > > > > > wrote:
> > > > > > >
> > > > > > > Oh,  I just forgot the github name issue which we faced when
> moving
> > > > > > > the servicecomb to apache incubator.
> > > > > > > I will fill a JIRA this weekend, it may take few days to do the
> > > > > > > transfer. Once we changed the github name, we could consider
> the
> > > > > > > release of ServiceCenter.
> > > > > > >
> > > > > > > Willem Jiang
> > > > > > >
> > > > > > > Twitter: willemjiang
> > > > > > > Weibo: 姜宁willem
> > > > > > >
> > > > > > > On Sat, Oct 27, 2018 at 2:25 PM Mohammad Asif Siddiqui
> > > > > > >  wrote:
> > > > > > > >
> > > > > > > > Hi Willem,
> > > > > > > >
> > > > > > > > In my opinion since ServiceComb has already graduated so we
> can
> > > > change
> > > > > > the repository names first and migrate the SVN for the releases
> and
> > > > then
> > > > > > plan for the ServiceComb 1.1.0 release. In Service-Center after
> the
> > > > change
> > > > > > in the repository name we need to change the import statements of
> > > each
> > > > file
> > > > > > and also we need to update the Travis settings for each project
> and
> > > > make
> > > > > > new encryption keys for automatic snapshot deployment, for all
> these
> > > > > > activities it might take 2-3 days so we can plan this first in
> coming
> > > > week
> > > > > > and then we can go ahead with the Service-Center 1.1.0 release.
> > > > > > > >
> > > > > > > > Just my 2 cents..
> > > > > > > >
> > > > > > > > Regards
> > > > > > > > Asif
> > > > > > > >
> > > > > > > > On 2018/10/22 03:39:02, Willem Jiang  >
> > > > wrote:
> > > > > > > > > Hi,
> > > > > > > > >
> > > > > > > > > The last ServiceComb java-chassis，service-center 1.0.0
> release
> > > is
> > > > > > > > > three month ago. It's time to discuss the release of
> > > ServiceComb
> > > > > > > > > 1.1.0.
> > > > > > > > >
> > > > > > > > > As we add the TCC implementation in the Saga 0.3.0, we may
> need
> > > > to
> > > > > > > > > create a separate git repo to support the Saga and TCC at
> the
> > > > same
> > > > > > > > > time.  It may take sometime to do these change. We may do
> the
> > > > Saga
> > > > > > > > > release after the release of java-chassis and
> service-center.
> > > > > > > > >
> > > > > > > > > Regards,
> > > > > > > > >
> > > > > > > > > Willem Jiang
> > > > > > > > >
> > > > > > > > > Twitter: willemjiang
> > > > > > > > > Weibo: 姜宁willem
> > > > > > > > >
> > > > > >
> > > >
> > >
>

Re: [ANN] New ServiceComb committer: Yao Haishi (姚海石)

[Bin Ma]

Congratulations!


Best Wishes & Regards
---
Mabin



Zheng Feng  于2018年11月13日周二 下午5:53写道：

> welcome on board !
>
> Willem Jiang  于2018年11月13日周二 上午10:47写道：
>
> > Please join me and the rest of the ServiceComb PPMC members in welcoming
> > our
> > new ServiceComb committer: Yao Haishi (姚海石).
> >
> > Yao Haishi contribute the ServiceComb more than a year, he is active
> > contributor on java-chassis, doc and the mailing list, and we look
> > forward to many more
> > contributions in the future.
> >
> > Congratulations to Yao Haishi ! Welcome!
> >
> >
> > Willem Jiang
> >
> > Twitter: willemjiang
> > Weibo: 姜宁willem
> >
>

Re: [Heads Up ]Git repository names are changed

[Bin Ma]

of course.
These two days are busy with supporting ServiceComb community activities...
Currently, I have already completed the modification and submitted it.
If there is a problem with the follow-up, I will submit the PR and fix it
in time.


Best Wishes & Regards
---
Mabin



Willem Jiang  于2018年11月13日周二 上午10:48写道：

> Hi Bin
>
> Do you mind to send a PR to help us clean up the
> {incubating|incubator} words in the website?
>
> Willem Jiang
>
> Twitter: willemjiang
> Weibo: 姜宁willem
>
> On Mon, Nov 12, 2018 at 7:24 PM Bin Ma  wrote:
> >
> > OK, my local env problem, the redirect is fine after clearing the browser
> > cookie.
> >
> >
> > Best Wishes & Regards
> > ---
> > Mabin
> >
> >
> >
> > Willem Jiang  于2018年11月12日周一 下午1:54写道：
> >
> > > We already use the servicecomb.apache.org and the old domain name
> > > servicecomb.io just redirect the request to servicecomb.apache.org.
> > >
> > > Willem Jiang
> > >
> > > Twitter: willemjiang
> > > Weibo: 姜宁willem
> > > On Mon, Nov 12, 2018 at 10:32 AM Bin Ma  wrote:
> > > >
> > > > Hi @Willem,
> > > >
> > > > Does the domain name of the ServiceComb Website also need to be
> updated?
> > > > such as,
> > > >   http://servicecomb.incubator.apache.org/
> > > > change to
> > > >   http://servicecomb.apache.org/
> > > >
> > > >
> > > >
> > > > Best Wishes & Regards
> > > > ---
> > > > Mabin
> > > >
> > > >
> > > >
> > > > Bin Ma  于2018年11月12日周一 上午9:29写道：
> > > >
> > > > > Great, I will update my document that guide to use ServiceComb.
> > > > >
> > > > >
> > > > > Best Wishes & Regards
> > > > > ---
> > > > > Mabin
> > > > >
> > > > >
> > > > >
> > > > > Sure  于2018年11月11日周日 下午9:22写道：
> > > > >
> > > > >> Hi guys, the ServiceCenter docs and codes are fixed!
> > > > >>
> > > > >>
> > > > >>
> > > > >>
> > > > >>
> > > > >> 发件人: "zzzwjm";
> > > > >> 发送时间: 2018年11月9日(星期五) 上午10:55
> > > > >> 收件人: "dev";
> > > > >>
> > > > >> 主题: Re: [Heads Up ]Git repository names are changed
> > > > >>
> > > > >>
> > > > >>
> > > > >> Great, thanks~
> > > > >>
> > > > >> Zheng Feng  于2018年11月9日周五 上午10:43写道：
> > > > >>
> > > > >> > Nice work ! I just open the PR to fix in the saga [1]
> > > > >> >
> > > > >> > [1] https://github.com/apache/servicecomb-saga/pull/332
> > > > >> >
> > > > >> > Willem Jiang  于2018年11月9日周五 上午10:02写道：
> > > > >> >
> > > > >> > > I did some clean up on java-chassis, saga, service-center
> README
> > > file
> > > > >> > > and removed the DISCLAIM file.
> > > > >> > > I also updated some documents of saga reference in the doc
> site.
> > > > >> > > There may still have some place need to updated.
> > > > >> > > Please check out the documents and feel free to submit fix for
> > > that.
> > > > >> > >
> > > > >> > > Willem Jiang
> > > > >> > >
> > > > >> > > Twitter: willemjiang
> > > > >> > > Weibo: 姜宁willem
> > > > >> > >
> > > > >> > > On Fri, Nov 9, 2018 at 8:59 AM Willem Jiang <
> > > willem.ji...@gmail.com>
> > > > >> > > wrote:
> > > > >> > > >
> > > > >> > > > Hi Team,
> > > > >> > > >
> > > > >> > > > As part of way to the Apache TLP, we need to rename the
> github
> > > repo
> > > > >> > name.
> > > > >> > > > Now it's done.  Please let me know if something is broken.
> > > > >> > > > I just checked travis CI, it's OK. I'll update the status
> bage
> > > link
> > > > >> > > shortly.
> > > > >> > > >
> > > > >> > > >
> > > > >> > > > Willem Jiang
> > > > >> > > >
> > > > >> > > > Twitter: willemjiang
> > > > >> > > > Weibo: 姜宁willem
> > > > >> > >
> > > > >> >
> > > > >
> > > > >
> > >
>

Re: [Heads Up ]Git repository names are changed

[Bin Ma]

OK, my local env problem, the redirect is fine after clearing the browser
cookie.


Best Wishes & Regards
---
Mabin



Willem Jiang  于2018年11月12日周一 下午1:54写道：

> We already use the servicecomb.apache.org and the old domain name
> servicecomb.io just redirect the request to servicecomb.apache.org.
>
> Willem Jiang
>
> Twitter: willemjiang
> Weibo: 姜宁willem
> On Mon, Nov 12, 2018 at 10:32 AM Bin Ma  wrote:
> >
> > Hi @Willem,
> >
> > Does the domain name of the ServiceComb Website also need to be updated?
> > such as,
> >   http://servicecomb.incubator.apache.org/
> > change to
> >   http://servicecomb.apache.org/
> >
> >
> >
> > Best Wishes & Regards
> > ---
> > Mabin
> >
> >
> >
> > Bin Ma  于2018年11月12日周一 上午9:29写道：
> >
> > > Great, I will update my document that guide to use ServiceComb.
> > >
> > >
> > > Best Wishes & Regards
> > > ---
> > > Mabin
> > >
> > >
> > >
> > > Sure  于2018年11月11日周日 下午9:22写道：
> > >
> > >> Hi guys, the ServiceCenter docs and codes are fixed!
> > >>
> > >>
> > >>
> > >>
> > >>
> > >> 发件人: "zzzwjm";
> > >> 发送时间: 2018年11月9日(星期五) 上午10:55
> > >> 收件人: "dev";
> > >>
> > >> 主题: Re: [Heads Up ]Git repository names are changed
> > >>
> > >>
> > >>
> > >> Great, thanks~
> > >>
> > >> Zheng Feng  于2018年11月9日周五 上午10:43写道：
> > >>
> > >> > Nice work ! I just open the PR to fix in the saga [1]
> > >> >
> > >> > [1] https://github.com/apache/servicecomb-saga/pull/332
> > >> >
> > >> > Willem Jiang  于2018年11月9日周五 上午10:02写道：
> > >> >
> > >> > > I did some clean up on java-chassis, saga, service-center README
> file
> > >> > > and removed the DISCLAIM file.
> > >> > > I also updated some documents of saga reference in the doc site.
> > >> > > There may still have some place need to updated.
> > >> > > Please check out the documents and feel free to submit fix for
> that.
> > >> > >
> > >> > > Willem Jiang
> > >> > >
> > >> > > Twitter: willemjiang
> > >> > > Weibo: 姜宁willem
> > >> > >
> > >> > > On Fri, Nov 9, 2018 at 8:59 AM Willem Jiang <
> willem.ji...@gmail.com>
> > >> > > wrote:
> > >> > > >
> > >> > > > Hi Team,
> > >> > > >
> > >> > > > As part of way to the Apache TLP, we need to rename the github
> repo
> > >> > name.
> > >> > > > Now it's done.  Please let me know if something is broken.
> > >> > > > I just checked travis CI, it's OK. I'll update the status bage
> link
> > >> > > shortly.
> > >> > > >
> > >> > > >
> > >> > > > Willem Jiang
> > >> > > >
> > >> > > > Twitter: willemjiang
> > >> > > > Weibo: 姜宁willem
> > >> > >
> > >> >
> > >
> > >
>

Re: [Heads Up ]Git repository names are changed

[Bin Ma]

Hi @Willem,

Does the domain name of the ServiceComb Website also need to be updated?
such as,
  http://servicecomb.incubator.apache.org/
change to
  http://servicecomb.apache.org/



Best Wishes & Regards
---
Mabin



Bin Ma  于2018年11月12日周一 上午9:29写道：

> Great, I will update my document that guide to use ServiceComb.
>
>
> Best Wishes & Regards
> ---
> Mabin
>
>
>
> Sure  于2018年11月11日周日 下午9:22写道：
>
>> Hi guys, the ServiceCenter docs and codes are fixed!
>>
>>
>>
>>
>>
>> 发件人: "zzzwjm";
>> 发送时间: 2018年11月9日(星期五) 上午10:55
>> 收件人: "dev";
>>
>> 主题: Re: [Heads Up ]Git repository names are changed
>>
>>
>>
>> Great, thanks~
>>
>> Zheng Feng  于2018年11月9日周五 上午10:43写道：
>>
>> > Nice work ! I just open the PR to fix in the saga [1]
>> >
>> > [1] https://github.com/apache/servicecomb-saga/pull/332
>> >
>> > Willem Jiang  于2018年11月9日周五 上午10:02写道：
>> >
>> > > I did some clean up on java-chassis, saga, service-center README file
>> > > and removed the DISCLAIM file.
>> > > I also updated some documents of saga reference in the doc site.
>> > > There may still have some place need to updated.
>> > > Please check out the documents and feel free to submit fix for that.
>> > >
>> > > Willem Jiang
>> > >
>> > > Twitter: willemjiang
>> > > Weibo: 姜宁willem
>> > >
>> > > On Fri, Nov 9, 2018 at 8:59 AM Willem Jiang 
>> > > wrote:
>> > > >
>> > > > Hi Team,
>> > > >
>> > > > As part of way to the Apache TLP, we need to rename the github repo
>> > name.
>> > > > Now it's done.  Please let me know if something is broken.
>> > > > I just checked travis CI, it's OK. I'll update the status bage link
>> > > shortly.
>> > > >
>> > > >
>> > > > Willem Jiang
>> > > >
>> > > > Twitter: willemjiang
>> > > > Weibo: 姜宁willem
>> > >
>> >
>
>

Re: [Heads Up ]Git repository names are changed

[Bin Ma]

Great, I will update my document that guide to use ServiceComb.


Best Wishes & Regards
---
Mabin



Sure  于2018年11月11日周日 下午9:22写道：

> Hi guys, the ServiceCenter docs and codes are fixed!
>
>
>
>
>
> 发件人: "zzzwjm";
> 发送时间: 2018年11月9日(星期五) 上午10:55
> 收件人: "dev";
>
> 主题: Re: [Heads Up ]Git repository names are changed
>
>
>
> Great, thanks~
>
> Zheng Feng  于2018年11月9日周五 上午10:43写道：
>
> > Nice work ! I just open the PR to fix in the saga [1]
> >
> > [1] https://github.com/apache/servicecomb-saga/pull/332
> >
> > Willem Jiang  于2018年11月9日周五 上午10:02写道：
> >
> > > I did some clean up on java-chassis, saga, service-center README file
> > > and removed the DISCLAIM file.
> > > I also updated some documents of saga reference in the doc site.
> > > There may still have some place need to updated.
> > > Please check out the documents and feel free to submit fix for that.
> > >
> > > Willem Jiang
> > >
> > > Twitter: willemjiang
> > > Weibo: 姜宁willem
> > >
> > > On Fri, Nov 9, 2018 at 8:59 AM Willem Jiang 
> > > wrote:
> > > >
> > > > Hi Team,
> > > >
> > > > As part of way to the Apache TLP, we need to rename the github repo
> > name.
> > > > Now it's done.  Please let me know if something is broken.
> > > > I just checked travis CI, it's OK. I'll update the status bage link
> > > shortly.
> > > >
> > > >
> > > > Willem Jiang
> > > >
> > > > Twitter: willemjiang
> > > > Weibo: 姜宁willem
> > >
> >

Re: Release of ServiceComb 1.1.0

[Bin Ma]

OK,I will try to check the ServiceComb website first


Best Wishes & Regards
---
Mabin



Willem Jiang  于2018年11月2日周五 上午8:30写道：

> I already submit a JIRA and wait for infra's response.
> But the document it's OK for us do the modification, please send a PR
> if you have time to work on it.
>
> Willem Jiang
>
> Twitter: willemjiang
> Weibo: 姜宁willem
>
> On Thu, Nov 1, 2018 at 8:24 PM Bin Ma  wrote:
> >
> > Hi all,
> >
> > Some community users plan to make courses based on ServiceComb in the
> near
> > future, like Itcast,University and so on.
> > So I think it may be speed up the process of renaming the git repo name
> and
> > updating the documentation.
> >
> >
> > Best Wishes & Regards
> > ---
> > Mabin
> >
> >
> >
> > Willem Jiang  于2018年10月29日周一 下午12:54写道：
> >
> > > FYI， I fill a JIRA[1] for renaming the git repo.
> > >
> > > [1]https://issues.apache.org/jira/browse/INFRA-17185
> > >
> > > Willem Jiang
> > >
> > > Twitter: willemjiang
> > > Weibo: 姜宁willem
> > > On Sat, Oct 27, 2018 at 10:09 PM Willem Jiang 
> > > wrote:
> > > >
> > > > Oh,  I just forgot the github name issue which we faced when moving
> > > > the servicecomb to apache incubator.
> > > > I will fill a JIRA this weekend, it may take few days to do the
> > > > transfer. Once we changed the github name, we could consider the
> > > > release of ServiceCenter.
> > > >
> > > > Willem Jiang
> > > >
> > > > Twitter: willemjiang
> > > > Weibo: 姜宁willem
> > > >
> > > > On Sat, Oct 27, 2018 at 2:25 PM Mohammad Asif Siddiqui
> > > >  wrote:
> > > > >
> > > > > Hi Willem,
> > > > >
> > > > > In my opinion since ServiceComb has already graduated so we can
> change
> > > the repository names first and migrate the SVN for the releases and
> then
> > > plan for the ServiceComb 1.1.0 release. In Service-Center after the
> change
> > > in the repository name we need to change the import statements of each
> file
> > > and also we need to update the Travis settings for each project and
> make
> > > new encryption keys for automatic snapshot deployment, for all these
> > > activities it might take 2-3 days so we can plan this first in coming
> week
> > > and then we can go ahead with the Service-Center 1.1.0 release.
> > > > >
> > > > > Just my 2 cents..
> > > > >
> > > > > Regards
> > > > > Asif
> > > > >
> > > > > On 2018/10/22 03:39:02, Willem Jiang 
> wrote:
> > > > > > Hi,
> > > > > >
> > > > > > The last ServiceComb java-chassis，service-center 1.0.0 release is
> > > > > > three month ago. It's time to discuss the release of ServiceComb
> > > > > > 1.1.0.
> > > > > >
> > > > > > As we add the TCC implementation in the Saga 0.3.0, we may need
> to
> > > > > > create a separate git repo to support the Saga and TCC at the
> same
> > > > > > time.  It may take sometime to do these change. We may do the
> Saga
> > > > > > release after the release of java-chassis and service-center.
> > > > > >
> > > > > > Regards,
> > > > > >
> > > > > > Willem Jiang
> > > > > >
> > > > > > Twitter: willemjiang
> > > > > > Weibo: 姜宁willem
> > > > > >
> > >
>

Re: Release of ServiceComb 1.1.0

[Bin Ma]

Hi all,

Some community users plan to make courses based on ServiceComb in the near
future, like Itcast,University and so on.
So I think it may be speed up the process of renaming the git repo name and
updating the documentation.


Best Wishes & Regards
---
Mabin



Willem Jiang  于2018年10月29日周一 下午12:54写道：

> FYI， I fill a JIRA[1] for renaming the git repo.
>
> [1]https://issues.apache.org/jira/browse/INFRA-17185
>
> Willem Jiang
>
> Twitter: willemjiang
> Weibo: 姜宁willem
> On Sat, Oct 27, 2018 at 10:09 PM Willem Jiang 
> wrote:
> >
> > Oh,  I just forgot the github name issue which we faced when moving
> > the servicecomb to apache incubator.
> > I will fill a JIRA this weekend, it may take few days to do the
> > transfer. Once we changed the github name, we could consider the
> > release of ServiceCenter.
> >
> > Willem Jiang
> >
> > Twitter: willemjiang
> > Weibo: 姜宁willem
> >
> > On Sat, Oct 27, 2018 at 2:25 PM Mohammad Asif Siddiqui
> >  wrote:
> > >
> > > Hi Willem,
> > >
> > > In my opinion since ServiceComb has already graduated so we can change
> the repository names first and migrate the SVN for the releases and then
> plan for the ServiceComb 1.1.0 release. In Service-Center after the change
> in the repository name we need to change the import statements of each file
> and also we need to update the Travis settings for each project and make
> new encryption keys for automatic snapshot deployment, for all these
> activities it might take 2-3 days so we can plan this first in coming week
> and then we can go ahead with the Service-Center 1.1.0 release.
> > >
> > > Just my 2 cents..
> > >
> > > Regards
> > > Asif
> > >
> > > On 2018/10/22 03:39:02, Willem Jiang  wrote:
> > > > Hi,
> > > >
> > > > The last ServiceComb java-chassis，service-center 1.0.0 release is
> > > > three month ago. It's time to discuss the release of ServiceComb
> > > > 1.1.0.
> > > >
> > > > As we add the TCC implementation in the Saga 0.3.0, we may need to
> > > > create a separate git repo to support the Saga and TCC at the same
> > > > time.  It may take sometime to do these change. We may do the Saga
> > > > release after the release of java-chassis and service-center.
> > > >
> > > > Regards,
> > > >
> > > > Willem Jiang
> > > >
> > > > Twitter: willemjiang
> > > > Weibo: 姜宁willem
> > > >
>

Re: [DRAFT] Graduation resolution proposal

[Bin Ma]

+1, awesome!


Best Wishes & Regards
---
Mabin



yhs0092  于2018年9月13日周四 上午11:16写道：

> +1 Great job!
>
>
> Yours sincerely
>
>
> Yao Haishi
> yhs0...@163.com
>
>
> On 9/13/2018 11:08，Lance Ju wrote：
> +1
> Great job!
>
> DeanLee <82529...@qq.com> 于2018年9月13日周四 上午10:57写道：
>
> +1
>
>
>
> ---Original---
> From: "Willem Jiang"
> Date: Wed, Sep 12, 2018 21:52 PM
> To: "dev";
> Subject: [DRAFT] Graduation resolution proposal
>
>
> As ServiceComb community discussed for the graduation for a while[1]
> and all the committer are OK to be the member of PMC[2].
>
> Now we have the developer team[3] from Huawei, Talend, Stealth,
> Hyperpilot, RedHat, JingDong,Tencent, Syswin, PICC, Changhong,
> Cainiao.
>
> 3300+ commits on development of three subproject.
> 1350+ PRs on the Github
> 171 contributors
> 800+ issues created
> 700+ issues resolved
>
> dev has 113 subscribers
> 208 emails sent by 28 people, divided into 30 topics in last month
>
> Please check out  Apache Maturity Model Assessment for ServiceComb[4]
> for more information.
>
> I just draft our graduation resolution proposal here. Please comment it.
>
> NOTE
> * I'm proposing myself as initial PMC chair -- Please comment if community
> is onboard with this or propose other persons as well
>
> [1]
>
> https://lists.apache.org/thread.html/8e59fef1a9eae9ee90808114b3abbdfdf8c6f24442d7575ee04f5100@%3Cdev.servicecomb.apache.org%3E
> [2]
>
> https://lists.apache.org/thread.html/2d1e7f17f15fc8ec0d4d293798991e93127534be9cc13334336d228f@%3Cdev.servicecomb.apache.org%3E
> [3]https://servicecomb.incubator.apache.org/developers/team/
> [4]
>
> https://cwiki.apache.org/confluence/display/SERVICECOMB/Apache+Maturity+Model+Assessment+for+ServiceComb
>
> 
>
> Establish the Apache ServiceComb Project
>
> WHEREAS, the Board of Directors deems it to be in the best interests of
> the Foundation and consistent with the Foundation's purpose to establish
> a Project Management Committee charged with the creation and maintenance
> of open-source software, for distribution at no charge to the public,
> related to a microservice framework that provides a set of tools and
> components to make development and deployment of cloud applications
> easier.
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> (PMC), to be known as the "Apache ServiceComb Project", be and hereby is
> established pursuant to Bylaws of the Foundation; and be it further
>
> RESOLVED, that the Apache ServiceComb Project be and hereby is
> responsible for the creation and maintenance of software related to a
> microservice framework that provides a set of tools and components to
> make development and deployment of cloud applications easier; and be it
> further
>
> RESOLVED, that the office of "Vice President, Apache ServiceComb" be and
> hereby is created, the person holding such office to serve at the
> direction of the Board of Directors as the chair of the Apache
> ServiceComb Project, and to have primary responsibility for management
> of the projects within the scope of responsibility of the Apache
> ServiceComb Project; and be it further
>
> RESOLVED, that the persons listed immediately below be and hereby are
> appointed to serve as the initial members of the Apache ServiceComb
> Project:
>
> * Aray Chenchu Sukesh
> * Bao Liu
> * Eric Lee   
> * Jean-Baptiste Onofré   
> * Jimin Wu   
> * Linzhinan  
> * Mohammad Asif Siddiqui 
> * Qi Zhang   
> * Roman Shaposhnik   
> * Timothy Chen   
> * Willem Ning Jiang  
> * Yang Bo
> * Yihua Cui  
> * Yin Xiang  
> * Zheng Feng 
> * zhengyangyong  
>
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Willem Ning Jiang be
> appointed to the office of Vice President, Apache ServiceComb, to serve
> in accordance with and subject to the direction of the Board of
> Directors and the Bylaws of the Foundation until death, resignation,
> retirement, removal or disqualification, or until a successor is
> appointed; and be it further
>
> RESOLVED, that the Apache ServiceComb Project be and hereby is tasked
> with the migration and rationalization of the Apache Incubator
> ServiceComb podling; and be it further
>
> RESOLVED, that all responsibilities pertaining to the Apache Incubator
> ServiceComb podling encumbered upon the Apache Incubator PMC are
> hereafter discharged.
>
>
>
> Willem Jiang
>
> Twitter: willemjiang
> Weibo: 姜宁willem
>

Re: [ANN] New ServiceComb PPMC: Feng Zheng (冯征）

[Bin Ma]

Congratulations!


Best Wishes & Regards
---
Mabin



Mohammad Asif Siddiqui  于2018年9月4日周二 下午3:11写道：

> Congratulations  Feng Zheng
>
> Regards
> Asif
>
> On Tue, Sep 4, 2018 at 12:03 PM Zen Lin 
> wrote:
>
> > Congratulations.
> >
> > Best Regards,
> > ---
> > Zen Lin
> > zenlintechnofr...@gmail.com
> > Focused on Micro Service and Apache ServiceComb
> >
> >
> > Lance Ju  于2018年9月4日周二 下午2:26写道：
> >
> > > Congratulations!
> > >
> > > 郑扬勇 <342906...@qq.com> 于2018年9月4日周二 上午10:53写道：
> > >
> > > > Congratulations!
> > > >
> > > >
> > > >
> > > >
> > > >  -- 原始邮件 --
> > > >   发件人: "willem.jiang";
> > > >  发送时间: 2018年8月31日(星期五) 晚上10:53
> > > >  收件人: "dev";
> > > >
> > > >  主题: [ANN] New ServiceComb PPMC: Feng Zheng (冯征）
> > > >
> > > >
> > > >
> > > > Please join me and the rest of the ServiceComb PPMC members in
> > welcoming
> > > > our
> > > > new ServiceComb PPMC member Feng Zheng.
> > > >
> > > > Feng Zheng does lots of contributions to the Saga since earlier this
> > year
> > > > and he did a good bridge work between ServiceComb and RedHat
> > transaction
> > > > related projects.
> > > >
> > > > Congratulations to Feng Zheng! Welcome!
> > > >
> > > > Willem Jiang
> > > >
> > > > Twitter: willemjiang
> > > > Weibo: 姜宁willem
> > >
> >
>

Re: [ANN] New ServiceComb PPMC: Zheng Yangyong (郑扬勇）

[Bin Ma]

Congratulations! Learn from  Zheng Yangyong: )


Best Wishes & Regards
---
Mabin



Mohammad Asif Siddiqui  于2018年9月4日周二 下午3:12写道：

> Congratulations Zheng Yangyong
>
> Regards
> Asif
>
> On Tue, Sep 4, 2018 at 12:03 PM Zen Lin 
> wrote:
>
> > Congratulations.
> >
> > Best Regards,
> > ---
> > Zen Lin
> > zenlintechnofr...@gmail.com
> > Focused on Micro Service and Apache ServiceComb
> >
> >
> > 郑扬勇 <342906...@qq.com> 于2018年9月4日周二 上午10:51写道：
> >
> > > Thanks :)
> > >
> > >   -- 原始邮件 --
> > >   发件人: "willem.jiang";
> > >  发送时间: 2018年8月31日(星期五) 晚上10:58
> > >  收件人: "dev";
> > >
> > >  主题: [ANN] New ServiceComb PPMC: Zheng Yangyong (郑扬勇）
> > >
> > >
> > >
> > > Please join me and the rest of the ServiceComb PPMC members in
> welcoming
> > > our
> > > new ServiceComb PPMC member Zheng Yangyong.
> > >
> > > Zheng Yangyong does lots of contributions to the Java Chassis, Saga
> since
> > > last August and helps users to solve their daily problems with
> > > ServiceComb.
> > >
> > > Congratulations to Zheng Yangyong! Welcome!
> > >
> > > Willem Jiang
> > >
> > > Twitter: willemjiang
> > > Weibo: 姜宁willem
> >
>

Re: [ANN] New ServiceComb PPMC: Lin Zhinan (林志南）

[Bin Ma]

Congratulations! Learn from guys and actively contribute to the community
: )


Best Wishes & Regards
---
Mabin



DeanLee <82529...@qq.com> 于2018年9月4日周二 下午3:50写道：

> Congratulations Lin Zhinan, Zheng Yangyong and  Feng Zheng
>
>
>
>
> -- 原始邮件 --
> 发件人: "Mohammad Asif Siddiqui";
> 发送时间: 2018年9月4日(星期二) 下午3:42
> 收件人: "dev";
>
> 主题: Re: [ANN] New ServiceComb PPMC: Lin Zhinan (林志南）
>
>
>
> Congratulations Lin Zhinan
>
> Regards
> Asif
>
> On Tue, Sep 4, 2018 at 12:03 PM Zen Lin 
> wrote:
>
> > My pleasure, thanks for trust.
> >
> > Best Regards,
> > ---
> > Zen Lin
> > zenlintechnofr...@gmail.com
> > Focused on Micro Service and Apache ServiceComb
> >
> >
> > 郑扬勇 <342906...@qq.com> 于2018年9月4日周二 上午10:52写道：
> >
> > > Congratulations!
> > >
> > >
> > >  -- 原始邮件 --
> > >   发件人: "willem.jiang";
> > >  发送时间: 2018年8月31日(星期五) 晚上11:01
> > >  收件人: "dev";
> > >
> > >  主题: [ANN] New ServiceComb PPMC: Lin Zhinan (林志南）
> > >
> > >
> > >
> > > Please join me and the rest of the ServiceComb PPMC members in
> welcoming
> > > our
> > > new ServiceComb PPMC member Lin Zhinan.
> > >
> > > Lin Zhinan does lots of contributions to the ServiceComb later last
> year
> > > and he already did lot of PPMC work such as helping us to hold the
> meetup
> > > events.
> > >
> > > Congratulations to Lin Zhinan! Welcome!
> > >
> > >
> > > Willem Jiang
> > >
> > > Twitter: willemjiang
> > > Weibo: 姜宁willem
> >

Re: [DISCUSS] Heading to graduation

[Bin Ma]

+1, ServiceComb is healthily and rapidly growing: )


Best Wishes & Regards
---
Mabin



Jean-Baptiste Onofré  于2018年9月4日周二 下午7:55写道：

> Hi,
>
> Basically, we should ask to the current PPMC if they agree to become PMC.
>
> Regarding the PMC Chair, I'm proposing Willem as Chair. He's driving the
> graduation, active on the project since the beginning, and a great asset
> for the foundation generally speaking.
>
> Thanks Willem !
>
> Regards
> JB
>
> On 03/09/2018 10:10, Willem Jiang wrote:
> > Hi Team,
> >
> > For the resolution proposal[1], we need to figure out  PMC and PMC Chair
> of
> > the ServiceComb for the board.
> > Normally we just move our PPMC member to the PMC, and we need to figure
> out
> > the PMC Chair.
> >
> > [1]
> https://incubator.apache.org/guides/graduation.html#preparing_a_charter
> >
> >
> >
> > Willem Jiang
> >
> > Twitter: willemjiang
> > Weibo: 姜宁willem
> >
> > On Thu, Aug 16, 2018 at 12:32 PM, Jean-Baptiste Onofré 
> > wrote:
> >
> >> Hi Willem,
> >>
> >> thanks for the update.
> >>
> >> The maturity model assessment draft looks overall good to me.
> >>
> >> I will add the resolution proposal draft on the wiki as well.
> >>
> >> Regards
> >> JB
> >>
> >> On 15/08/2018 11:09, Willem Jiang wrote:
> >>> With the ServiceComb java-chassis 1.0.0-incubating and service-center
> >>> 1.0.0-incubating release officially out.
> >>> We believe it is time to discuss what requirements remains to consider
> >>> graduation to the TLP.
> >>>
> >>> I just updated the ServiceComb Project Status for it:
> >>>
> >>> http://servicecomb.incubator.apache.org/
> >>>
> >>> Apache ServiceComb entered incubation in November of 2017, ServiceComb
> >>> community learned a lot about how to do things in Apache ways.
> >>> Now we are a very helpful and engaged community, ready to help on all
> >>> questions from the ServiceComb Community.
> >>> We are making consensus decisions through the discussion in the mailing
> >>> list and voted 3 new committers.
> >>> We managed delivered three round released include 5 different binary
> >>> release, now we can do self-driving releases in good cadence.
> >>>
> >>> Please check out the maturity assessment doc[1] for more information.
> >>>
> >>> [1]
> >>
> https://cwiki.apache.org/confluence/display/SERVICECOMB/Apache+Maturity+
> >>> Model+Assessment+for+ServiceComb
> >>>
> >>> Any thoughts? And welcome advice from ServiceComb Mentors?
> >>>
> >>> Regards,
> >>>
> >>>
> >>>
> >>> Willem Jiang
> >>>
> >>> Twitter: willemjiang
> >>> Weibo: 姜宁willem
> >>>
> >>> On Fri, Jul 13, 2018 at 4:16 PM, Jean-Baptiste Onofré  >
> >>> wrote:
> >>>
>  It sounds good !
> 
>  In the mean time, I'm moving forward on the assessment document and
>  preparing the resolution.
> 
>  I will send an update during the weekend.
> 
>  Regards
>  JB
> 
>  On 13/07/2018 09:44, Willem Jiang wrote:
> > Yeah, we are heading to TLP.
> >
> > Current we are planing release ServiceComb Service-Center 1.0.0,
> > SerivceComb Java-Chassis 1.0.0 this month.
> > The ServiceComb trademark transfer process looks good.
> > And we make consensus decisions through the discussion - vote
> process.
> >
> >
> > Willem Jiang
> >
> > Twitter: willemjiang
> > Weibo: 姜宁willem
> >
> > On Sun, Jul 8, 2018 at 1:59 PM, Jean-Baptiste Onofré <
> j...@nanthrax.net>
> > wrote:
> >
> >> Hi all,
> >>
> >> Last week, Willem and I had a long discussion about the status of
> the
> >> ServiceComb podling.
> >>
> >> IMHO, we are almost ready for graduation.
> >>
> >> We worked on the maturity assessment doc:
> >>
> >> https://cwiki.apache.org/confluence/display/
>  SERVICECOMB/Apache+Maturity+
> >> Model+Assessment+for+ServiceComb
> >>
> >> So, it looks good to me, I'm doing a new pass on the assessment
> model
> >> providing some details on some topics, but overall good.
> >>
> >> I wanted to have your inputs about that (heading to TLP).
> >>
> >> Thoughts ?
> >>
> >> Regards
> >> JB
> >> --
> >> Jean-Baptiste Onofré
> >> jbono...@apache.org
> >> http://blog.nanthrax.net
> >> Talend - http://www.talend.com
> >>
> >
> 
>  --
>  Jean-Baptiste Onofré
>  jbono...@apache.org
>  http://blog.nanthrax.net
>  Talend - http://www.talend.com
> 
> >>>
> >>
> >> --
> >> Jean-Baptiste Onofré
> >> jbono...@apache.org
> >> http://blog.nanthrax.net
> >> Talend - http://www.talend.com
> >>
> >
>
> --
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>

Re: [VOTE] Release Apache ServiceComb Service-Center (incubating) version 1.0.0 (RC-03)

[Bin Ma]

 +1 non binding


Best Wishes & Regards
---
Mabin



wjm wjm  于2018年7月27日周五 上午8:54写道：

>  +1 binding
>
> 1. check release notes and binaries. [OK]
> 2. run test case using windows version. [OK]
>
> 2018-07-26 22:32 GMT+08:00 Willem Jiang :
>
> > +1 binding
> >
> > I checked：
> > - hashes and signatures looks good
> > - DISCLAIMER/NOTICE/LICENSE looks good
> > - can make build the kit from source
> > - checked for archive matching git tag
> > - Source file have ASF headers
> >
> >
> >
> > Willem Jiang
> >
> > Twitter: willemjiang
> > Weibo: 姜宁willem
> >
> > On Thu, Jul 26, 2018 at 8:55 PM, bismy  wrote:
> >
> > > +1 binding
> > > Check done:
> > > 1. check release notes and binaries. [OK]
> > > 2. run test case using windows version. [OK]
> > >
> > >
> > >
> > >
> > > -- 原始邮件 --
> > > 发件人: "Mohammad Asif Siddiqui";
> > > 发送时间: 2018年7月26日(星期四) 下午3:45
> > > 收件人: "dev";
> > >
> > > 主题: Re: [VOTE] Release Apache ServiceComb Service-Center (incubating)
> > > version 1.0.0 (RC-03)
> > >
> > >
> > >
> > > +1 binding
> > >
> > > Checks I did:
> > > - hashes and signatures is good
> > > - DISCLAIMER/NOTICE/LICENSE exists
> > > - ran RAT tool
> > > - can make release kit from source
> > > - checked for archive matching git tag
> > > - Source file have ASF headers
> > > - Ran the java-chassis and go-chassis demo's.
> > > - Ran Integration test on linux, windows and mac
> > >
> > > Regards
> > > Asif
> > >
> > > On 2018/07/25 09:00:29, Mohammad Asif Siddiqui  >
> > > wrote:
> > > > Hi All,
> > > >
> > > > This is a call for a Vote to release Apache ServiceComb
> Service-Center
> > > (Incubating) version 1.0.0 (RC-03)
> > > >
> > > > Release Notes : https://github.com/apache/
> > incubator-servicecomb-service-
> > > center/blob/master/docs/release/releaseNotes-1.0.0.md
> > > >
> > > > Release Candidate :
> https://dist.apache.org/repos/dist/dev/incubator/
> > > servicecomb/incubator-servicecomb-service-center/1.0.0/rc-03/
> > > >
> > > > Release Tag :
> https://github.com/apache/incubator-servicecomb-service-
> > > center/releases/tag/1.0.0
> > > >
> > > > Release CommitID : fc38b272a288cf322fa309402a98a89dc6b591f4
> > > >
> > > > Keys to verify the Release Candidate :
> https://dist.apache.org/repos/
> > > dist/dev/incubator/servicecomb/KEYS
> > > >
> > > > Guide to build the release from source : https://github.com/apache/
> > > incubator-servicecomb-service-center/tree/master/scripts/release
> > > >
> > > > Voting will start now ( Wednesday, 25th July, 2018) and will remain
> > open
> > > for atleast 72 hours, Request all PPMC members to give their vote
> > > >
> > > > [ ] +1 Release this package as 1.0.0
> > > > [ ] +0 No Opinion
> > > > [ ] -1 Do not release this package because
> > > >
> > > > On the behalf of ServiceComb Team
> > > > Mohammad Asif Siddiqui
> > > >
> > > >
> > >
> >
>

Re: [VOTE] Release Apache ServiceComb Java-Chassis (Incubating) version 1.0.0

[Bin Ma]

 +1 non binding,  my show cases are working fine.

Best Wishes & Regards
---
Mabin



wjm wjm  于2018年7月27日周五 上午9:00写道：

> SCB-575 still in OPEN status
>
> 2018-07-27 8:55 GMT+08:00 wjm wjm :
>
> > SCB-592 also have won't fix problem
> >
> > it's better everybody check their own issues
> >
>

Re: 【Proposal】Close ServiceComb group on github

[Bin Ma]

Currently, ​​Scaffold_CRM  Demo [1],Company Demo [2] and Seckill [3]  are
popular with users.
It is useful to create a sub project to host these demos before closing
ServiceComb organization.

​[1] https://github.com/zhengyangyong/scaffold
[2] https://github.com/ServiceComb/ServiceComb-Company-WorkShop
[3] https://github.com/ServiceComb/seckill


Best Wishes & Regards
---
Mabin



Willem Jiang  于2018年7月26日周四 上午8:06写道：

> ServiceComb-Company-WorkShop has some stuff relates to Huawei cloud, so we
> don't put it as a sub project as the Apache ServiceComb.
> If we have more demo project come out, we may consider to create sub
> project in Apache.
> For those demo or personal projects, we need to go through the donation
> process before we move them into Apache.
>
>
> Willem Jiang
>
> Twitter: willemjiang
> Weibo: 姜宁willem
>
> On Wed, Jul 25, 2018 at 10:20 PM, Zen Lin 
> wrote:
>
> > Summarize:
> > Scaffold_CRM  Demo [1], which shows how to use servicecomb scaffold to
> > develop a CRM application.
> > Company Demo [2], which shows how to use servicecomb to develop a
> ordinary
> > microservices application.
> > start.servicecomb.io,  which is the cold generator website of
> servicecomb.
> >
> > [1] https://github.com/zhengyangyong/scaffold
> > 
> > [2] https://github.com/ServiceComb/ServiceComb-Company-WorkShop
> > [3] https://github.com/wangkirin/initializr
> >
> > Anymore?
> >
> > Hi Willem, JB,
> > We do not know how to keep these official demos and tools  in a Apache
> > project usually.
> > A centralized repository for Demos or tools? something like
> > https://github.com/apache/servicecomb-demos?
> >
> > Best Regards,
> > ---
> > Zen Lin
> > zenlintechnofr...@gmail.com
> > Focused on Micro Service and Apache ServiceComb
> >
> >
> > Jean-Baptiste Onofré  于2018年7月25日周三 下午8:54写道：
> >
> > > Should not be on Apache gitbox ?
> > >
> > > Regards
> > > JB
> > >
> > > Le 25 juil. 2018 à 11:13, à 11:13, Willem Jiang <
> willem.ji...@gmail.com>
> > > a écrit:
> > > >Yeah, we can just transfer the repo to another group.
> > > >If the user use the older URL to access the repo, github can redirect
> > > >the
> > > >request to the new transfer URL.
> > > >
> > > >
> > > >Willem Jiang
> > > >
> > > >Twitter: willemjiang
> > > >Weibo: 姜宁willem
> > > >
> > > >On Wed, Jul 25, 2018 at 4:47 PM, Yang Bo  wrote:
> > > >
> > > >> +1 for removing the ServiceComb organization.
> > > >>
> > > >> Some issues:
> > > >> The go-chassiss and related forked third parties are still hosted on
> > > >this
> > > >> group. We should migrate those first before closing.
> > > >>
> > > >>
> > > >> On Wed, Jul 25, 2018 at 4:45 PM Willem Jiang <
> willem.ji...@gmail.com>
> > > >> wrote:
> > > >>
> > > >> > I think we just need to find a home for
> > > >> > https://github.com/ServiceComb/ServiceComb-Company-WorkShop
> > > >> >
> > > >> > huaweicse could be a way to go.
> > > >> >
> > > >> >
> > > >> > Willem Jiang
> > > >> >
> > > >> > Twitter: willemjiang
> > > >> > Weibo: 姜宁willem
> > > >> >
> > > >> > On Wed, Jul 25, 2018 at 4:25 PM, bismy  wrote:
> > > >> >
> > > >> > > +1.
> > > >> > > Does huawei has an organization to hosting these contents? Maybe
> > > >we can
> > > >> > > move them all there. And I have an organization to host
> temporary
> > > >> > contents.
> > > >> > > https://github.com/huaweicse
> > > >> > >
> > > >> > >
> > > >> > > -- 原始邮件 --
> > > >> > > 发件人: "Zen Lin";
> > > >> > > 发送时间: 2018年7月25日(星期三) 下午4:13
> > > >> > > 收件人: "dev";
> > > >> > > 抄送: "Xiaoliang Tian";
> > > >> > > 主题: 【Proposal】Close ServiceComb group on github
> > > >> > >
> > > >> > >
> > > >> > >
> > > >> > > Hi Guys,
> > > >> > >
> > > >> > > As we known, Apache ServiceComb (incubating) is in the "Near
> > > >> Graduation"
> > > >> > > status.
> > > >> > > There still a ServiceComb group on the github [1], projects
> under
> > > >this
> > > >> > > group is not in the incubator scope of ServiceComb now, my
> > > >suggestion
> > > >> is
> > > >> > to
> > > >> > > close this group.
> > > >> > >
> > > >> > > I  have gone though the projects and find out the corresponding
> > > >> > maintainers
> > > >> > > , please transfer the project to other place but not
> ServiceComb,
> > > > as
> > > >> > > follows,
> > > >> > >
> > > >> > > Maintainer: Shawn
> > > >> > > https://github.com/ServiceComb/go-chassis
> > > >> > > 
> > > >> > > https://github.com/ServiceComb/cse-collector
> > > >> > > 
> > > >> > > https://github.com/ServiceComb/go-cc-client
> > > >> > > 
> > > >> > > https://github.com/ServiceComb/go-archaius
> > > >> > > 
> > > >> > > https://github.com/ServiceComb/go-sc-client
> > > >> > > 
> > > >> > > https://github.com/ServiceComb/paas-lager
> > > >> > > 
> > > >> > > https://github.com/ServiceComb/http-client
> > > >> > > 
> > > >> > > https://github.com/ServiceComb/auth
> > > >> > >
> > > >> > > Maintainer: Willem
> > > >> > > 

Re: [DISCUSS] Service-Center Docker images version numbering

[Bin Ma]

+1 for Yang Bo' suggestion.
Service Center backend and frontend is better to integrated in one docker
image, so that easy for users get and run complete function anywhere, such
as in Mac OS.


Best Wishes & Regards
---
Mabin



bismy  于2018年7月20日周五 上午11:16写道：

> +1 For daily build, we only test against released server center for
> java-chassis, e.g. 1.0.0.m2. We can test lastest version or other to check
> compatibility before release new version or weeks a day.
>
>
>
>
> -- 原始邮件 --
> 发件人: "willem.jiang";
> 发送时间: 2018年7月19日(星期四) 下午4:34
> 收件人: "dev";
>
> 主题: Re: [DISCUSS] Service-Center Docker images version numbering
>
>
>
> For the system test and integration test, it could be good the
> ServiceCenter is stable.
> So we may not use the latest version in the Java-Chassis system tests.
> If we want to check the service-center compatible, we can start a CI with
> some basic test per day.
>
>
> Willem Jiang
>
> Twitter: willemjiang
> Weibo: 姜宁willem
>
> On Tue, Jul 17, 2018 at 9:24 PM, Mohammad Asif Siddiqui <
> asifdxtr...@apache.org> wrote:
>
> > Hi All,
> >
> > There was an issue raised in github[1] of service-center regarding the
> > images of SC in docker hub for which we need your feedback.
> >
> > Problem : Currently there are no docker images of service-center which
> > reflects the current state of the service-center. We only make docker
> > images when we cut new version and also update the "latest" tag at that
> > time. If someone(like Java-Chassis and Saga CI) wants to test their
> changes
> > with the latest Service-Center then they have to either wait for a new
> > version to be released or make there own docker image which might be
> > sometimes difficult.
> >
> > Solution : For every successful merge to Service-Center the CI will make
> a
> > new docker image and push it to Dockerhub with the "latest" tag.
> Whenever a
> > new version is cut then we will make a new tag with the version number.
> So
> > the Service-Center tags will look like:
> > "latest" : Always represents the latest state of the Service-Center in
> > github repo.
> > "VersionNumer"(like 1.0.0) : This will be created whenever a new version
> is
> > released.
> >
> > CI's which are using the SC docker hub images can always use the latest
> tag
> > for their test as well as recent versions of the service-center to check
> > backward compatibility.
> >
> > Since Java-Chassis and Saga CI's uses these SC docker images very
> > frequently in their test so we want to know the opinion on this from
> > maintainers of Java-Chassis and Saga.
> >
> > [1]
> >
> https://github.com/apache/incubator-servicecomb-service-center/issues/277
> >
> > Regards
> > Asif
> >

Re: Re: [DISCUSS]Shall we upgrade Java-chassis to support Spring Boot2

[Bin Ma]

+1 to @Kirin Wang's suggestion.
start.servicecomb.io should be support Spring Boot 2 too, Chuanzhi
Boke also use start.servicecomb.io to develop coursewares now. It should be
created a sub-task to tracing.


Best Wishes & Regards
---
Mabin



Kirin Wang  于2018年7月23日周一 上午9:23写道：

> I think we also have a sub-task of support Spring Boot 2 ,  which  is  add
> Spring Boot 2.X option in start.servicecomb.io .
>
> Zen Lin  于2018年7月23日周一 上午9:15写道：
>
> > +1 to Willem's suggestion.
> > Could someone ask yaohaishi to create a issue track for this, upgrade to
> > support Spring Boot2.
> > And when he find an actual issue on testing it, can create a  sub issue
> > under the issue of "upgrade to support Spring Boot2".
> >
> > Thus,  Mabin and the users can know the detail progress or report what
> > issue they meet through the issue.
> >
> > Best Regards,
> > ---
> > Zen Lin
> > zenlintechnofr...@gmail.com
> > Focused on Micro Service and Apache ServiceComb
> >
> >
> > Willem Jiang  于2018年7月20日周五 下午4:40写道：
> >
> > > SCB-758 is a big task.  I don't think we need to wait for it done to
> > > support Spring Boot 2.x.
> > > Yaohaishi already did some test on it,  we just need to keep fix the
> > actual
> > > issue we find
> > >
> > > my suggestion is we support Spring Boot 1.x by default, and add a
> Spring
> > > Boot 2.x profile to the user who want to use Spring Boot 2.x.
> > >
> > >
> > >
> > > Willem Jiang
> > >
> > > Twitter: willemjiang
> > > Weibo: 姜宁willem
> > >
> > > On Fri, Jul 20, 2018 at 4:25 PM, Bin Ma  wrote:
> > >
> > > > Currently I have recommended user like Chuanzhi Boke to develop based
> > on
> > > > the spring boot1.x version to ensure that user development is not
> > > blocked.
> > > >
> > > > I agree with bimsy's idea,users' demands and scenes are clear,an task
> > > > should be created to trace.
> > > >
> > > > As I know, SCB-758(https://issues.apache.org/jira/browse/SCB-758)
> is a
> > > > task
> > > > to remove the dependency of java-chassis on spring, I'm not sure if
> > this
> > > > task is completed first, and it is more helpful to support the
> > > springboot2
> > > > ?
> > > >
> > > > 2018-07-20 11:24 GMT+08:00 Willem Jiang :
> > > >
> > > > > From the Spring Boot2 migration guide[1], the class package and
> name
> > > was
> > > > > changed.
> > > > >
> > > > > We may need to create different module to handle the class package
> > > change
> > > > > issue.
> > > > >
> > > > > [1]
> > > > > https://github.com/spring-projects/spring-boot/wiki/
> > > > >
> Spring-Boot-2.0-Migration-Guide#embedded-containers-package-structure
> > > > >
> > > > >
> > > > >
> > > > > Willem Jiang
> > > > >
> > > > > Twitter: willemjiang
> > > > > Weibo: 姜宁willem
> > > > >
> > > > > On Fri, Jul 20, 2018 at 10:29 AM, yhs0092  wrote:
> > > > >
> > > > > > I tried to upgrade Java-Chassis to support SpringBoot2 before,
> but
> > > > > failed.
> > > > > >
> > > > > >
> > > > > > There are two problems. The first one is in our bean.xml file，
> the
> > > xsd
> > > > > > file is imported like below:
> > > > > > ```
> > > > > >
> > classpath:org/springframework/beans/factory/xml/spring-beans-3.0.xsd
> > > > > > ```
> > > > > > but 3.0 version xsd file does not exist anymore.
> > > > > >
> > > > > > This is still resolvable, but for the second problem, I still
> > haven't
> > > > > > found a way to resolve it.
> > > > > >
> > > > > >
> > > > > > When my service demo is started, an error occurs:
> > > > > > ```
> > > > > > 2018-03-13 22:57:18.396  WARN 6 --- [   main]
> > > > > > ConfigServletWebServerApplicationContext : Exception encountered
> > > > during
> > > > > > context initialization - cancelling refresh attempt:
> > > > > > org.springframework.beans.factory.BeanDefinitionStore

Re: [VOTE] Release Apache ServiceComb Service-Center (incubating) version 1.0.0

[Bin Ma]

I did some tests with 1.0.0 version, base functions is OK and the features
are forward compatible, but the link of user guide in Service Center
Dashboard seems be wrong.

Best Wishes & Regards
---
Mabin



Jean-Baptiste Onofré  于2018年7月23日周一 下午1:17写道：

> I guess you mean NOTICE file, right ?
>
> Regards
> JB
>
> Le 23 juil. 2018 à 03:53, à 03:53, Yang Bo  a écrit:
> >-1
> >
> >Several third-party libraries were added but not included in LICENSE
> >file.
> >
> >github.com/karlseguin/ccache
> >github.com/gorilla/websocket
> >css-percentage-circle
> >vis
> >
> >
> >On Sat, Jul 21, 2018 at 10:16 AM bismy  wrote:
> >
> >> +1
> >> Check the release notes and run some test to binaries.
> >>
> >>
> >> One small improvement, for API Changes in release notes, can you give
> >> detail description about the changes?
> >>
> >>
> >>
> >>
> >> -- 原始邮件 --
> >> 发件人: "Mohammad Asif Siddiqui";
> >> 发送时间: 2018年7月21日(星期六) 凌晨4:29
> >> 收件人: "dev";
> >>
> >> 主题: [VOTE] Release Apache ServiceComb Service-Center (incubating)
> >version
> >> 1.0.0
> >>
> >>
> >>
> >> Hi All,
> >>
> >> This is a call for a Vote to release Apache ServiceComb
> >Service-Center
> >> (Incubating) version 1.0.0
> >>
> >> Release Notes :
> >>
> >
> https://github.com/apache/incubator-servicecomb-service-center/blob/master/docs/release/releaseNotes-1.0.0.md
> >>
> >>
> >> Release Candidate :
> >>
> >
> https://dist.apache.org/repos/dist/dev/incubator/servicecomb/incubator-servicecomb-service-center/1.0.0/rc-01/
> >>
> >>
> >> Release Tag :
> >>
> >
> https://github.com/apache/incubator-servicecomb-service-center/releases/tag/1.0.0
> >>
> >>
> >> Release CommitID : 7590fec4e4447fdd3b2977970d544e88ae3762cf
> >>
> >> Keys to verify the Release Candidate :
> >> https://dist.apache.org/repos/dist/dev/incubator/servicecomb/KEYS
> >>
> >> Guide to build the release from source :
> >>
> >
> https://github.com/apache/incubator-servicecomb-service-center/tree/master/scripts/release
> >>
> >>
> >> Voting will start now ( Saturday, 21st July, 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
> >> [ ] +0 No Opinion
> >> [ ] -1 Do not release this package because
> >>
> >> On the behalf of ServiceComb Team
> >> Mohammad Asif Siddiqui
> >
> >
> >
> >--
> >Best Regards,
> >Yang.
>

Re: [DISCUSS] Proposal for Re-Design of Service-Center Frontend

[Bin Ma]

About the new Service-Center UI, some ideas from the user's point of view,
1. The function of the old UI is stable at 1.0.0-m2, including featrures
and configuration files. The new UI should provide stable and usable
features, and do not displayed test phase featrures in the UI interface to
avoid misleading users, such as SCHEMA Test in 1.0.0-m1.
2. If there is no user appeal in the old UI, it is recommended to maintain
compatibility, including the original usage methods, functions, and
back-end interfaces,it is not excluded that the user may develop the UI by
himself. If there are changes, it is recommended to provide detailed
instructions.
3. I have seen some new features are added in the new UI. It is recommended
that each function provide detailed instructions for users to understand
and use quickly.
4. Need to provide Chinese version UI and manual  : )

Best Wishes & Regards
---
Mabin



Zen Lin  于2018年7月17日周二 下午3:36写道：

> +1
>
> Best Regards,
> ---
> Zen Lin
> zenlintechnofr...@gmail.com
> Focused on Micro Service and Apache ServiceComb
>
>
> Willem Jiang  于2018年7月17日周二 下午3:33写道：
>
> > I cannot agree with you more about it.
> > We need to avoid this kind of situation in our further development.
> > Before we start writing the code, it's quite important that we need to
> send
> > a heads up or proposal to let others know about it.
> >
> >
> > Willem Jiang
> >
> > Twitter: willemjiang
> > Weibo: 姜宁willem
> >
> > On Tue, Jul 17, 2018 at 3:22 PM, wjm wjm  wrote:
> >
> > > ok
> > >
> > > but i think it's better raise proposal before start work on it.
> > >
> > > 2018-07-17 15:04 GMT+08:00 Willem Jiang :
> > >
> > > > It‘s no harm if the development is down.  We just need to get more
> feed
> > > > back from the community and consider to merge the UI to the new UI.
> > > > For the UI, there are some License stuff of java script library we
> need
> > > to
> > > > care about. We may need to address this issue before CSE UI is open
> > > > sourced.
> > > >
> > > >
> > > > Willem Jiang
> > > >
> > > > Twitter: willemjiang
> > > > Weibo: 姜宁willem
> > > >
> > > > On Tue, Jul 17, 2018 at 1:36 PM, Mohammad Asif Siddiqui <
> > > > asifdxtr...@apache.org> wrote:
> > > >
> > > > > Hi Guyz,
> > > > >
> > > > > The development of these design was already done before and that's
> > the
> > > > > reason we were able to show the snapshots of the new UI. The code
> is
> > > > ready
> > > > > to be merged but before merging we decided to come here and discuss
> > > about
> > > > > this UI for people opinion. Since most of the people are concerned
> > > about
> > > > > the effort needed to re-design this UI, so I would like to tell
> that
> > > > > development is already done.
> > > > >
> > > > > So in my opinion we can merge this change to make the UI better and
> > > > > whenever ServiceComb-UI gets opensourced then we can plan to merge
> > some
> > > > of
> > > > > these designs to the ServiceComb-UI.
> > > > >
> > > > > Any thoughts?
> > > > >
> > > > > Regrds
> > > > > Asif
> > > > >
> > > > > On 2018/07/16 10:57:00, Zen Lin 
> wrote:
> > > > > > Hi all,
> > > > > > As we known,  CSE is a initial commercial product of servicecomb
> > and
> > > we
> > > > > > have tried our best to ask CSE to open source ServiceComb-UI to
> > > > stronger
> > > > > > servicecomb and let servicecomb service users better.
> > > > > > But I think the discuss should focused on what's  difference
> > between
> > > > > > servicecenter UI positioning and servicecomb UI positioning.
> > > > > >
> > > > > > If we sure the functionality of servicecenter UI is a subset of
> of
> > > > > > servicecomb UI which will be opensourceed future, and Asif have
> > > willing
> > > > > to
> > > > > > keep on developing and maintaining a servicenter UI, will will
> have
> > > two
> > > > > UI
> > > > > > in future, I think that is allowed with a opensource project
> also.
> > > > > >
> > > > > > Therefore, to my opinion, I think we can focused on discussing
> > > > > > servicecenter-UI's position, something like, what functionality
> for
> > > > > > service-center UI is reasonable?
> > > > > >
> > > > > >
> > > > > > Best Regards,
> > > > > > ---
> > > > > > Zen Lin
> > > > > > zenlintechnofr...@gmail.com
> > > > > > Focused on Micro Service and Apache ServiceComb
> > > > > >
> > > > > >
> > > > > > wjm wjm  于2018年7月16日周一 下午12:43写道：
> > > > > >
> > > > > > > maybe we can change our mind to: make sure new feathers all in
> > > > > > > ServiceComb-UI, not design a new one.
> > > > > > >
> > > > > > > 2018-07-16 12:41 GMT+08:00 wjm wjm :
> > > > > > >
> > > > > > > > as i said that, Proposal of new SC frontend seems to be a
> > subset
> > > of
> > > > > > > > ServiceComb-UI
> > > > > > > > if that's true, i think we no need to spend time to do one
> > thing
> > > > > with two
> > > > > > > > way.
> > > > > > > >
> > > > > > > > 2018-07-16 11:58 GMT+08:00 Mohammad Asif Siddiqui <
> > > > > > > asifdxtr...@apache.org>
> > > > > > > > :

Re: Re: [DISCUSS]Shall we upgrade Java-chassis to support Spring Boot2

[Bin Ma]

Currently I have recommended user like Chuanzhi Boke to develop based on
the spring boot1.x version to ensure that user development is not blocked.

I agree with bimsy's idea,users' demands and scenes are clear,an task
should be created to trace.

As I know, SCB-758(https://issues.apache.org/jira/browse/SCB-758) is a task
to remove the dependency of java-chassis on spring, I'm not sure if this
task is completed first, and it is more helpful to support the springboot2 ?

2018-07-20 11:24 GMT+08:00 Willem Jiang :

> From the Spring Boot2 migration guide[1], the class package and name was
> changed.
>
> We may need to create different module to handle the class package change
> issue.
>
> [1]
> https://github.com/spring-projects/spring-boot/wiki/
> Spring-Boot-2.0-Migration-Guide#embedded-containers-package-structure
>
>
>
> Willem Jiang
>
> Twitter: willemjiang
> Weibo: 姜宁willem
>
> On Fri, Jul 20, 2018 at 10:29 AM, yhs0092  wrote:
>
> > I tried to upgrade Java-Chassis to support SpringBoot2 before, but
> failed.
> >
> >
> > There are two problems. The first one is in our bean.xml file， the xsd
> > file is imported like below:
> > ```
> > classpath:org/springframework/beans/factory/xml/spring-beans-3.0.xsd
> > ```
> > but 3.0 version xsd file does not exist anymore.
> >
> > This is still resolvable, but for the second problem, I still haven't
> > found a way to resolve it.
> >
> >
> > When my service demo is started, an error occurs:
> > ```
> > 2018-03-13 22:57:18.396  WARN 6 --- [   main]
> > ConfigServletWebServerApplicationContext : Exception encountered during
> > context initialization - cancelling refresh attempt:
> > org.springframework.beans.factory.BeanDefinitionStoreException: Failed
> to
> > parse configuration class [org.apache.servicecomb.
> > springboot.starter.transport.RestServletInitializer]; nested exception
> is
> > java.io.FileNotFoundException: class path resource
> > [org/springframework/boot/context/embedded/
> AbstractConfigurableEmbeddedServletContainer.class]
> > cannot be opened because it does not exist
> > ```
> > Because AbstractConfigurableEmbeddedServletContainer is removed in
> > SpringBoot2, and our RestServletInitializer is extended from this class,
> > maybe we cannot upgrade to SpringBoot2 by simply change the maven
> > dependency.
> > And once we refactor our RestServletInitializer, the java-chassis may not
> > be compatible with SpringBoot1.
> >
> >
> >
> > 在 2018-07-20 08:57:05，"wjm wjm"  写道：
> > >not enough, must exclude old spring also
> > >
> > >2018-07-20 6:44 GMT+08:00 Willem Jiang :
> > >
> > >> How about let user override the version of Spring Boot in their
> > application
> > >> and give it a try.
> > >> Just like what we do with JDK9 here[1]
> > >> If there is any issue comes out, we can keep digging it.
> > >>
> > >> [1]https://github.com/apache/incubator-servicecomb-saga/issues/76
> > >>
> > >>
> > >> Willem Jiang
> > >>
> > >> Twitter: willemjiang
> > >> Weibo: 姜宁willem
> > >>
> > >> On Thu, Jul 19, 2018 at 8:26 PM, Bin Ma  wrote:
> > >>
> > >> > Hi,
> > >> >   Java-chassis currently supports Spirng Boot 1.5.12 version.
> > >> >
> > >> >   In fact, some enterprise users develop their coursewares based on
> > >> Spring
> > >> > Boot2, so hopefully Java-chassis can support Spring Boot2, such as
> > >> Chuanzhi
> > >> > Boke.
> > >> >
> > >> >   I think it's neccessary to discuss the plan about  upgrading
> > >> > Java-Chasssis to support  Spring Boot2 to satisfy users' scenario.
> > >> >
> > >> >   Any thoughts and any troubles to upgrading, please feel free to
> > discuss
> > >> > here.
> > >> >
> > >>
> >
>



-- 
Best Wishes & Regards
---
Mabin

[DISCUSS]Shall we upgrade Java-chassis to support Spring Boot2

[Bin Ma]

Hi,
  Java-chassis currently supports Spirng Boot 1.5.12 version.

  In fact, some enterprise users develop their coursewares based on Spring
Boot2, so hopefully Java-chassis can support Spring Boot2, such as Chuanzhi
Boke.

  I think it's neccessary to discuss the plan about  upgrading
Java-Chasssis to support  Spring Boot2 to satisfy users' scenario.

  Any thoughts and any troubles to upgrading, please feel free to discuss
here.

Re: [DISCUSS] Detail design for linking servicecomb-java-chassis-doc tousers of website.

[Bin Ma]

+1
This needs to be handled asap, if the official website
and servicecomb-java-chassis-doc are not synchronized, it will mislead
users and affect the user experience.

2018-07-11 10:20 GMT+08:00 bismy :

> Agree with your idea
>
>
>
>
> -- 原始邮件 --
> 发件人: "Zen Lin";
> 发送时间: 2018年7月9日(星期一) 下午4:05
> 收件人: "dev";
>
> 主题: [DISCUSS] Detail design for linking servicecomb-java-chassis-doc
> tousers of website.
>
>
>
> As Liubao have renew a user docs in
> https://huaweicse.github.io/servicecomb-java-chassis-doc/.
>
> My suggestion is  to replace the user part of website to this docs, details
> are:
>
>1. Create several items in http://servicecomb.incubator.
> apache.org/users/ ,
>each item corresponds to a project, such as java-chassis, saga,
>servicecenter
>2.  Change https://huaweicse.github.io/servicecomb-java-chassis-doc/ to
>https://servicecomb.incubator.apache,org/servicecomb-java-chassis-doc/
>
>3. link
>https://servicecomb.incubator.apache,org/servicecomb-java-chassis-doc/
> to the
>Java-chassis item under http://servicecomb.incubator.apache.org/users/
>
> If we do it like this way , we also should change user docs of the saga and
> servicecenter to gitbook to keep the user experience consistent.
>
> By the way, I also create a JIRA issue [1] to track this.
>
> Any thoughts  please feel free to discuss here.
>
>
> [1] https://issues.apache.org/jira/browse/SCB-721
>
> Best Regards,
> ---
> Zen Lin
> zenlintechnofr...@gmail.com
> Focused on Micro Service and Apache ServiceComb
>

Re: [DISCUSS] Add Users and Customers information in github pages of ServiceComb Projects.

[Bin Ma]

In my opinion, users' confidence in the project comes from the project
maturity assessment report, so I think it is better to reflect users' use
in the report rather than the github page.

Now,there are about 5 Huawei departments and other 10 companies are using
ServiceComb,they are Huawei Cloud Core Network,Huawei Cloud EI,Huawei Cloud
Security,Huawei Consumer Business Cloud,Huawei Device
Cloud,ChangHong,Isofstone,Pactera,Greentown,Gaomai
Zhiyuan,Ceewa,MedSci,Hangling, Yunlu since ServiceComb has been incubating.

2018-07-12 22:16 GMT+08:00 Mohammad Asif Siddiqui :

> Hi All,
>
> As most of the credibility of the project comes from the people who uses it
> and trusts it.
>
> As per my understanding we have already have some customers who are using
> ServiceComb in the development and productions env, so is it possible to
> put their names in the github pages of ServiceComb Projects with their
> logos.
>
> It will really help for the promotion of ServiceComb and build a confidence
> and trust for new Users who want to adopt ServiceComb.
>
> Any thoughts on this?
>
> Regards
> Asif
>

Re: Podling Report Reminder - July 2018

[Bin Ma]

 Add some commentary, more and more companies and users have used or
participated in contributing to the Servicecomb community. They are Huawei
Cloud Core Network,Huawei Cloud EI,Huawei Cloud Security,Huawei Consumer
Business Cloud,Huawei Device
Cloud,ChangHong,Isofstone,Pactera,Greentown,Gaomai
Zhiyuan,Ceewa,MedSci,Hangling and so on since ServiceComb has been
incubating.

2018-07-02 16:15 GMT+08:00 Jean-Baptiste Onofré :

> Hi
>
> Thanks for the update. I think we can update the status to "near
> graduation".
>
> I'm planning to work today and tomorrow on a plan and resolution to move
> forward on graduation.
>
> Regards
> JB
>
> Le 2 juil. 2018 à 10:10, à 10:10, Willem Jiang  a
> écrit:
> >Hi Team
> >
> >I just update the project report like this , please review it and feel
> >free
> >to add what I'm missing.
> >We may need to add a report link for the workshop which we hold last
> >week.
> >
> >BTW,  we get more and more contributors to the projects, which is good
> >sign
> >to see.  Please keep up this good work.
> >
> >
> >ServiceComb has been incubating since 2017-11-22.
> >
> >Three most important issues to address in the move towards graduation:
> >
> >  1. Community building
> >  2. Project visibility
> >  3. Trademark transfer
> >
> >Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
> >aware of?
> >
> >  NO
> >
> >How has the community developed since the last report?(2018-04)
> >  * The community get the second release out, service-center 1.0.0-m2,
> >java-chassis 1.0.0-m2 and saga 0.2.0
> >  * The community hold a day workshop in Beijing at Jun 27.
> >
> >How has the project developed since the last report? (2018-04)
> >  * Java Chassis merged with 102 PRs by 16 contributors.
> >  * Service Center merged with 58 PRs by 6 contributors .
> >  * Saga merged with 48 PRs by 14 contributors.
> >  * 70 mails send by 19 people on the dev@ list (2018-04)
> >  * 156 mails sent by 17 people on the dev@ list （2018-05）
> >  * 97 mails send by  23 people on the dev@ list  (2018-06)
> >
> >How would you assess the podling's maturity?
> >Please feel free to add your own commentary.
> >
> >  [ ] Initial setup
> >  [ ] Working towards first release
> >  [*] Community building
> >  [ ] Nearing graduation
> >  [ ] Other:
> >
> >Date of last release:
> >
> >  2018-06-22 Java Chassis 1.0.0-m2
> >  2018-06-22 Service Center 1.0.0-m2
> >  2018-06-22 Saga 0.2.0
> >
> >When were the last committers or PPMC members elected?
> >  2018-06-08 Zheng yangyong  was elected as committer.
> >  2018-06-11 Li Dagang(Eric) was elected as committer.
> >
> >
> >Willem Jiang
> >
> >Twitter: willemjiang
> >Weibo: 姜宁willem
> >
> >On Thu, Jun 28, 2018 at 5:41 AM,  wrote:
> >
> >> Dear podling,
> >>
> >> This email was sent by an automated system on behalf of the Apache
> >> Incubator PMC. It is an initial reminder to give you plenty of time
> >to
> >> prepare your quarterly board report.
> >>
> >> The board meeting is scheduled for Wed, 18 July 2018, 10:30 am PDT.
> >> The report for your podling will form a part of the Incubator PMC
> >> report. The Incubator PMC requires your report to be submitted 2
> >weeks
> >> before the board meeting, to allow sufficient time for review and
> >> submission (Wed, July 04).
> >>
> >> Please submit your report with sufficient time to allow the Incubator
> >> PMC, and subsequently board members to review and digest. Again, the
> >> very latest you should submit your report is 2 weeks prior to the
> >board
> >> meeting.
> >>
> >> Candidate names should not be made public before people are actually
> >> elected, so please do not include the names of potential committers
> >or
> >> PPMC members in your report.
> >>
> >> Thanks,
> >>
> >> The Apache Incubator PMC
> >>
> >> Submitting your Report
> >>
> >> --
> >>
> >> Your report should contain the following:
> >>
> >> *   Your project name
> >> *   A brief description of your project, which assumes no knowledge
> >of
> >> the project or necessarily of its field
> >> *   A list of the three most important issues to address in the move
> >> towards graduation.
> >> *   Any issues that the Incubator PMC or ASF Board might wish/need to
> >be
> >> aware of
> >> *   How has the community developed since the last report
> >> *   How has the project developed since the last report.
> >> *   How does the podling rate their own maturity.
> >>
> >> This should be appended to the Incubator Wiki page at:
> >>
> >> https://wiki.apache.org/incubator/July2018
> >>
> >> Note: This is manually populated. You may need to wait a little
> >before
> >> this page is created from a template.
> >>
> >> Mentors
> >> ---
> >>
> >> Mentors should review reports for their project(s) and sign them off
> >on
> >> the Incubator wiki page. Signing off reports shows that you are
> >> following the project - projects that are not signed may raise alarms
> >> for the Incubator PMC.
> >>
> >> Incubator PMC
> >>
>

Re: [Discussion] Improve documents of serviceComb

[Bin Ma]

Personally, if I was a user of the first contact with ServiceComb, I would
like to get some information from the official website,
1.list of all the ServiceComb features, including descriptions of all
features, specifications, usage guide, demo links, and so on.
2.quick start guide, including the simplest "hello world" case, an
entry-level composite microservice case (just like bmi now), a microservice
case based on business scenarios, and so on.
3.FAQ, including the common problems and solutions, and each FAQ requires a
clear context.
4.Summary architecture design graph, including architecture and surrounding
open source ecological construction.
5.Module dependency graph of ServiceComb, the roles and dependencies of
each package in the ServiceComb source code.
6.roadmap.

2018-05-11 11:52 GMT+08:00 Zen Lin :

> Yeah,
>
> But I think maybe we have some misunderstanding between API-reference and
> user-guide, let us make it more clearly.
>
> To user-guide,  it is a list of quckstart samples to each functionality of
> ServiecComb, such as,
> https://cloud.spring.io/spring-cloud-gateway/#quick-start shows users how
> to quickly start with a gateway.
> These user guide samples can help users to quickly start from a simple
> sample to use functionality in there first step, thus can give users
> confidence and interesting to use ServiceComb.
>
> I think what Liubao is doing is just a API-reference, which is used for
> deep leaning users to use and develop ServiceComb, it is also important and
> strong required.
>
> @Willem, Liubao,
> Do you agree with the relationship between userguide and api-reference,
> if it is agreed, I think maybe Kirin can create two issues on JIRA, one is
> improvement quickstart of ServiceComb, the other is improvement of
> userguide.
>
> Best Regards,
> ---
> Zen Lin
> zenlintechnofr...@gmail.com
> Focused on Micro Service and Apache ServiceComb
>
> 2018-05-11 11:07 GMT+08:00 Willem Jiang :
>
> > We could create some JIRAs to track the document relate issues.
> > @Liubao,  Do you mind create some sub tasks for it?
> >
> > I think we already have some docs for the quick start and user guide,
> but
> > we need to publish the API documents as well.
> > So I just fill a JIRA[1] for java-chassis and Saga about it.
> >
> > [1]https://issues.apache.org/jira/browse/SCB-575
> >
> >
> > Willem Jiang
> >
> > Blog: http://willemjiang.blogspot.com (English)
> >   http://jnn.iteye.com  (Chinese)
> > Twitter: willemjiang
> > Weibo: 姜宁willem
> >
> > On Fri, May 11, 2018 at 10:37 AM, Zen Lin 
> > wrote:
> >
> > > Yeah,  Nice.
> > > Hi Liubao, Kirin,
> > >
> > > I think it is better to have some detail discussion between both of you
> > to
> > > ensure a new set of document can give users a friendly and
> > > three-dimensional experience, includes quick start, user guide, API
> > > reference.
> > >
> > > Best Regards,
> > > ---
> > > Zen Lin
> > > zenlintechnofr...@gmail.com
> > > Focused on Micro Service and Apache ServiceComb
> > >
> > > 2018-05-11 9:31 GMT+08:00 bismy :
> > >
> > > > We are keeping in thinking a way to better guide the first start
> users.
> > > > Maybe a working project is very good start point.
> > > > However, quick start to tell the basics is also very important.
> > > > Inspired by working project, I write a quick start to let users
> > download
> > > > examples or using archetypes recently provided.
> > > > Please check https://huaweicse.github.io/
> servicecomb-java-chassis-doc/
> > > > zh_CN/start/first-sample.html
> > > >
> > > >
> > > > We are now working on better ServiceComb-java-chassis documents now,
> > and
> > > > this link is the preview version.
> > > >
> > > >
> > > > -- 原始邮件 --
> > > > 发件人: "Zen Lin";
> > > > 发送时间: 2018年5月10日(星期四) 晚上7:39
> > > > 收件人: "dev";
> > > >
> > > > 主题: Re: [Discussion] Improve documents of serviceComb
> > > >
> > > >
> > > >
> > > > Hi kirin,
> > > >
> > > > Thanks.
> > > > I think we should figure out what the users want when they want to
> > > reading
> > > > the quickstart and userguide.
> > > >
> > > > What liubao doing is to output a comprehensive user guide like
> > > > Api-reference book, and the  community lacks of documentation focused
> > > > solely on helping users get started.
> > > >
> > > > I think it is quite important to supplement this deficiency, so is
> our
> > > goal
> > > > should be focused on the following 3 key points?
> > > > 1. One simplest sample to show easily Using ServiceComb by one-click.
> > > > 2. One small sample to show users can make there apps easily have
> basic
> > > > service governance capabilities with ServiceComb.
> > > > 3. A simple sample corresponding to a functionality of ServiceComb,
> > like
> > > > what you mentioned like Spring.
> > > >
> > > > Anyway, you can also finding some place on the website 

Re: [VOTE] Move github notifications to maillist "comm...@servicecomb.apache.org"

[Bin Ma]

+1 non binding

2018-05-11 21:12 GMT+08:00 wjm wjm :

> +1
>
> 2018-05-11 17:52 GMT+08:00 Willem Jiang :
>
> > +1 , it could make the dev discuss more focused.
> >
> >
> > Willem Jiang
> >
> > Blog: http://willemjiang.blogspot.com (English)
> >   http://jnn.iteye.com  (Chinese)
> > Twitter: willemjiang
> > Weibo: 姜宁willem
> >
> > On Fri, May 11, 2018 at 4:51 PM, kirin wang 
> > wrote:
> >
> > > Hi  Community:
> > >
> > >   As we already discussed  in [1], this is a call for vote to move
> > > github notifications of Apache ServiceComb to maillist  "
> > > comm...@servicecomb.apache.org" .
> > >
> > > Voting will start now ( Friday, 11th May, 2018) and will remain open
> for
> > > next 72 hours.
> > >
> > > [ ] +1 Move Github notifications to maillist
> "commits@servicecomb.apache.
> > > org
> > > "
> > > [ ] +0 No Opinion
> > > [ ] -1 Do not move Github notifications to maillist "
> > > comm...@servicecomb.apache.org"
> > >
> > >
> > >
> > > [1]
> > > https://lists.apache.org/thread.html/95f538f676326bd2cb1a06cf278c40
> > > 76352b987bfbabad6c6ae247bc@%3Cdev.servicecomb.apache.org%3E
> > >
> >
>

Re: [VOTE] Release Apache ServiceComb Java-Chassis (incubating) version 1.0.0-m1 - Second Attempt

[Bin Ma]

 +1 Non Binding

Build the source successfully,and unit tests and integration tests are
passed

2018-03-19 13:06 GMT+08:00 Mahesh Raju Somalaraju :

> +1 Non Binding
>
> - Ran java-chassis demos using service-center release binary.
> - Run the rat to verify the License header issue.
>
> Thanks & Regards
> -Mahesh Raju S
>
>
> On Sat, Mar 17, 2018 at 12:22 AM, Mohammad Asif Siddiqui <
> asifdxtr...@apache.org> wrote:
>
> > 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-1181/
> >
> > Release Tag : https://github.com/apache/incubator-servicecomb-java-
> > chassis/releases/tag/1.0.0-m1
> >
> > Release CommitID : 3dbfb87eb6249f3ad41ea7514d1a73ec6e193bfe
> >
> > Keys to verify the Release Candidate : https://dist.apache.org/repos/
> > dist/dev/incubator/servicecomb/KEYS
> >
> > Voting will start now ( Saturday, 17th 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
> >
> >
>

Re: [VOTE] Release Apache ServiceComb Service-Center (incubating) version 1.0.0-m1 - Fourth Attempt

[Bin Ma]

+1 non binding

Ran the service-center release binary successfully

2018-03-19 13:05 GMT+08:00 Mahesh Raju Somalaraju :

> +1 Non Binding
>
> - Ran java-chassis demos using service-center release binary.
> - Run the rat to verify the License header issue.
>
> Thanks & Regards
> -Mahesh Raju S
>
> On Sat, Mar 17, 2018 at 12:08 AM, Mohammad Asif Siddiqui <
> asifdxtr...@apache.org> wrote:
>
> > Hi All,
> >
> > This is a call for Vote to release Apache ServiceComb Service-Center
> > (Incubating) version 1.0.0-m1 (fourth release candidate).
> >
> > Release Notes : https://github.com/apache/incubator-servicecomb-service-
> > center/blob/master/docs/release/releaseNotes.md
> >
> > Release Candidate : https://dist.apache.org/repos/dist/dev/incubator/
> > servicecomb/incubator-servicecomb-service-center/1.0.0-m1/
> >
> > Release Tag : https://github.com/apache/incubator-servicecomb-service-
> > center/releases/tag/1.0.0-m1
> >
> > Release CommitID : 94cea25ba55e763dbe23d0cd4a8da73e37a50539
> >
> > Keys to verify the Release Candidate : https://dist.apache.org/repos/
> > dist/dev/incubator/servicecomb/KEYS
> >
> > Guide to build the release from source : https://github.com/apache/
> > incubator-servicecomb-service-center/tree/master/scripts/release
> >
> > Voting will start now ( Saturday, 17th 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
> >
> >
> >
>