Re: [DISCUSS] Change default branch to 3.0 branch

[Xin Wang]

Hi, Albumen，Yunkun

I think the usual way is:
1. Create a 2.7.x branch from the master branch as the maintenance branch

2. Merge the 3.0 branch into the master branch,

3 And then delete branch 3.0



Albumen Kevin  于2021年6月18日周五 下午5:20写道：

> Hi YunKun,
>
> Existing PRs will work fine due to GitHub changing it automatically.
> The problem is users who tracked master in local will break.
>
> I think it is necessary to rename the master branch to the 2.7.x branch.
> However, we should consider whether to rename the 3.0 branch to the master
> branch or not.
>
> On Fri, Jun 18, 2021 at 5:04 PM YunKun Huang  wrote:
>
> > or maybe we should rename 3.0 branch to master branch?
> >  not sure if it will broke existing PR
> >
> > On Thu, Jun 17, 2021 at 2:11 PM Xin Wang 
> wrote:
> > >
> > > +1 to agree
> > >
> > > Horizon <1060026...@qq.com> 于2021年6月16日周三 上午11:27写道：
> > >
> > > > +1
> > > >
> > > >
> > > > > 2021年6月16日 10:38，Jun Liu  写道：
> > > > >
> > > > > +1
> > > > >
> > > > > 3.0 represents the next generation Dubbo and should be placed at a
> > > > prominent position.
> > > > >
> > > > > Jun
> > > > >
> > > > >> On Jun 13, 2021, at 3:59 PM, Albumen Kevin 
> > wrote:
> > > > >>
> > > > >> Hello Community,
> > > > >>
> > > > >> With everyone's strong support, Apache Dubbo 3.0 is about to be
> > > > released.
> > > > >>
> > > > >> Shall we change the default branch in GitHub repo[1] to 3.0
> > branch[2],
> > > > >> which can guide
> > > > >> new contributors to contribute to Dubbo 3 easily, and rename the
> > master
> > > > >> branch to `2.7` branch?
> > > > >>
> > > > >> [1] https://github.com/apache/dubbo/branches
> > > > >> [2] https://github.com/apache/dubbo/tree/3.0
> > > > >>
> > > > >> Thanks,
> > > > >> Albumen Kevin
> > > > >
> > > >
> > > >
> >
>

Re: [DISCUSS] Change default branch to 3.0 branch

[Xin Wang]

+1 to agree

Horizon <1060026...@qq.com> 于2021年6月16日周三 上午11:27写道：

> +1
>
>
> > 2021年6月16日 10:38，Jun Liu  写道：
> >
> > +1
> >
> > 3.0 represents the next generation Dubbo and should be placed at a
> prominent position.
> >
> > Jun
> >
> >> On Jun 13, 2021, at 3:59 PM, Albumen Kevin  wrote:
> >>
> >> Hello Community,
> >>
> >> With everyone's strong support, Apache Dubbo 3.0 is about to be
> released.
> >>
> >> Shall we change the default branch in GitHub repo[1] to 3.0 branch[2],
> >> which can guide
> >> new contributors to contribute to Dubbo 3 easily, and rename the master
> >> branch to `2.7` branch?
> >>
> >> [1] https://github.com/apache/dubbo/branches
> >> [2] https://github.com/apache/dubbo/tree/3.0
> >>
> >> Thanks,
> >> Albumen Kevin
> >
>
>

Re: [VOTE] Accept the donation of dubbo-go-pixiu

[Xin Wang]

+1 Accept

joezou  于2021年3月14日周日 下午10:44写道：

> +1 Accept
>
> stocks alex  于2021年3月13日周六 下午9:20写道：
>
> > +1 Accept
> >
> > wongoo  于2021年3月13日周六 下午7:24写道：
> >
> > > Hi All,
> > >
> > > This is a formal vote to donate dubbogo/dubbo-go-pixiu[1] to apache.
> > >
> > > dubbo-go-pixiu is a gateway based on dubbo-go. It provides a general
> > > solution that supports calling dubbo services through other protocols.
> At
> > > present, it supports HTTP and gRPC[developing].
> > >
> > > All contributors[3] agree to donate it to the Dubbo community, and have
> > > already signed the ICLA. In the discussion[2], the community also
> > supports
> > > the donation.
> > >
> > >
> > > Please vote:
> > > [ ] +1 Accept
> > > [ ] +0 No Opinion
> > > [ ] -1 Reject because...
> > >
> > >
> > > [1] https://github.com/dubbogo/dubbo-go-pixiu/
> > > [2]
> > >
> > >
> >
> https://lists.apache.org/thread.html/r765a243e534ff36f524227776a8ab7c067678d1952141a4cf461200c%40%3Cdev.dubbo.apache.org%3E
> > > [3] pixiu contributors:
> > > - williamfeng323, ICLA signed
> > > - mark4z, ICLA signed
> > > - xiaoliu10, ICLA signed
> > > - oaoit, ICLA signed
> > > - xianlezheng, ICLA signed
> > > - ztelur, ICLA signed
> > > - zhangshen023, ICLA signed
> > > - cityiron/IronCity, dubbo commiter
> > > - zouyx, dubbo PMC
> > > - pantianying, dubbo commiter
> > > - AlexStocks, dubbo PMC
> > >
> > > --
> > > Regards,
> > > Wongoo
> > >
> >
>

Re: [DISCUSSION] donate dubbo-go-pixiu to Dubbo community

[Xin Wang]

+1

ranke <213...@qq.com> 于2021年3月11日周四 上午11:16写道：

> +1
>
>
>
>
> --Original--
> From: "wongoo" Date: 2021年3月10日(星期三) 上午10:33
> To: "dev" Subject: [DISCUSSION] donate dubbo-go-pixiu to Dubbo community
>
>
>
> Hello Dubbo community,
>
> I would like to initiate a discussion about donating dubbo-go-pixiu to the
> Dubbo community.
>
> We are developing the dubbo-go-pixiu, a gateway based on dubbo-go, which
> provides a general solution that supports calling dubbo services through
> other protocols. At present, it supports HTTP and gRPC[developing].
>
> The development of dubbo-go-pixiu is driven by the dubbo-go community, all
> contributors agree to donate it to Dubbo community, and we have signed the
> ICLA. The source code is available here:
> https://github.com/dubbogo/dubbo-go-pixiu.
>
> --
> Regards,
> Wongoo

Re: [VOTE] Accept dubbogo/dubbo-go-pixiu donation

[Xin Wang]

+1 to Accept

stocks alex  于2021年3月9日周二 下午8:11写道：

> +1 Accept
>
> wongoo  于2021年3月9日周二 下午2:48写道：
>
> > all contributors are agree to donate and preparing the sign for ICLA. I
> > will provide a list for that when all finished.
> >
> > On Tue, Mar 9, 2021 at 12:25 PM Ming Wen  wrote:
> >
> > > Hi，
> > > Do you have signed ICLA’s for all contribitors?
> > >
> > > Thanks,
> > > Ming Wen, Apache APISIX PMC Chair
> > > Twitter: _WenMing
> > >
> > >
> > > wongoo  于2021年3月9日周二 下午12:00写道：
> > >
> > > > Hi All,
> > > >
> > > > This is a formal vote to donate dubbogo/dubbo-go-pixiu[1] to apache.
> > > >
> > > > *dubbo-go-pixiu* is a gateway based on dubbo-go. It provides a
> general
> > > > solution that supports calling dubbo services through other
> protocols.
> > At
> > > > present, it supports HTTP and gRPC[developing].
> > > >
> > > >
> > > > Please vote:
> > > > [ ] +1 Accept
> > > > [ ] +0 No Opinion
> > > > [ ] -1 Reject because...
> > > >
> > > >
> > > > [1] https://github.com/dubbogo/dubbo-go-pixiu
> > > >
> > > > --
> > > > Regards,
> > > > Wongoo
> > > >
> > >
> >
> >
> > --
> > Regards,
> > Wongoo
> >
>

Re: [Discuss] Disable Travis CI for apache/dubbo

[Xin Wang]

Agree, since Github Actions have become more and more powerful

Albumen Kevin  于2021年3月5日周五 下午2:59写道：

> Hi community,
>
>
> So far, we have enable two kinds of CI/CD platform , Travis CI and
>
> GitHub Actions, for Dubbo. GitHub actions works fine for Dubbo
>
> in 2.6.x[1], 2.7.x[2] and 3.x[3] versions.
>
> In 2.7.x and 3.x versions, both unit test and integration test[4], based
>
> on apache/dubbo-samples, are introduced to guarantee the stability
>
> of the snapshot version.
>
>
> There are some benefits can be provided by GitHub Actions now:
>
>
> - More powerful ecosystem
>
> - Easy integration with more GitHub activity
>
> - Can be launched at any time because it is no need
>
>for us to share the concurrency limit with all projects.
>
>Also the concurrency limit for each project looks enough for us.
>
>
> I am wondering if we could disable Travis CI for now which function
>
> can be completely replaced with GitHub Actions?
>
>
> [1] https://github.com/apache/dubbo/actions/runs/623019397
>
> [2] https://github.com/apache/dubbo/actions/runs/620506574
>
> [3] https://github.com/apache/dubbo/actions/runs/620213136
>
> [4] https://github.com/apache/dubbo/runs/2029991040
>

Re: [ANN] Welcome a new committer He Qun(Watermelo)

[Xin Wang]

Congratulations !

xinming he  于2020年9月4日周五 下午3:19写道：

> Hi, Community,
>
> On behalf of the Dubbo PMC, I am pleased to announce that He Qun[1] has
> been
> voted in as a new Dubbo committer.
>
> Please join me to say congratulations to him!
>
> He Qun, would you please briefly introduce yourself to the community?
>
> 1. https://github.com/watermelo
> Yours,
> Xinming.
>

Re: [VOTE] Release Apache Dubbo-Hessian-Lite 3.2.7 RC1

[Xin Wang]

>   What we could change in the future is
we should gracefully retire hessian-lite library and encourage Dubbo users
to depend on the official Hessian 4 release




I think dealing with this component is a hassle, I'll tell you what I know :


1. History of using Hessian in Dubbo

Hessian[1] is a serialization component specially developed by caucho
company and provided to resin.
The official has been disclosing the code on their company's SVN until
2017 Feb.

Probably from the beginning of Dubbo's creation of repo in GitHub in
2012, he copied a 2009 code named
Hessian-lite from the official of Hessian until now.

2. In a sense, after the 2017 Feb, the official Hessian is no longer a
standard open source project

  Although the official Hessian has been releasing binary packages
recently, the source code has not been opened to the public since 2017, see
[2]

  I set up a Hessian Group [3], which collects the clients of each language
of Hessian [4].

I also wrote an email to the caucho official, expecting them to open source
to GitHub and let everyone
participate in the development. The official answer is:

>  Generally, Hessian needs to be super stable both in terms of API and
reliability for the sake of Resin.  If there's a bug or feature request,
》》>  feel free to file it at bugs.caucho.com.  With that said, we
whole-heartedly support people to fork Hessian.


So my suggestions are as follows:
  1. Hessian-lite needs to continue to be published in the Apache community
  2. In view of the dependence of Dubbo project on hessian, many users use
Hessian in production, so we still have to try to contact more with the
official maintainers of Hessian

[1] http://hessian.caucho.com/
[2] https://github.com/ebourg/hessian
[3] https://github.com/hessian-group
[4] https://github.com/hessian-group/awesome-hessian

Ian Luo  于2020年3月23日周一 上午11:55写道：

> >
> > The hessian-lite module has already exist long before Dubbo joined ASF,
> I
> > am not sure if the original developers who did this still active in the
> > mailing list, so it’s hard to tell the whole story. But I think at least
> > something is sure about why we need to maintain a separate copy:
> > 1. The Caucho Hessian community[1], we’ve seen its activity in a very low
> > level for a really long time. To meet requirements we do have to
> maintain a
> > copy inside our community.
> > 2. Hessian works as a serialization protocol in Dubbo and has been widely
> > used by users. It’s the core part of an RPC framework, most users will
> stay
> > on Hessian and won’t change.
>
>
> Justin, I totally agree with the reasons Jun gave above. We are not the
> original developers who made the decision to tailor Hessian library instead
> of contribute back, but after I take a brief at the release history of
> Hessian 4 [1], I guess I would make the similar decision.
>
> If it is legally fine (I think it is perfectly allowed), I suggest we have
> to live with the current situation. What we could change in the future is
> we should gracefully retire hessian-lite library and encourage Dubbo users
> to depend on the official Hessian 4 release.
>
> My conclusion is, this particular issue should not block the current
> release and the future potential releases.
>
> Thanks,
> -Ian.
>
>
> 1. https://mvnrepository.com/artifact/com.caucho/hessian
>
>
> On Mon, Mar 23, 2020 at 10:25 AM Jun Liu  wrote:
>
> > Hi
> >
> > > - NOTICE is missing
> >
> >
> > From what I can see now, we need an NOTICE file, inside which we should
> > mention the codes copy of of the Caucho Hessian Project. Do you think
> would
> > that change be enough for the next round of release?
> >
> > > It would be good to know more the history here and why this was done,
> > where there talks with the Caucho and they gave permission to do this? Or
> > are some of those developers involved here?
> >
> > The hessian-lite module has already exist long before Dubbo joined ASF,
> I
> > am not sure if the original developers who did this still active in the
> > mailing list, so it’s hard to tell the whole story. But I think at least
> > something is sure about why we need to maintain a separate copy:
> > 1. The Caucho Hessian community[1], we’ve seen its activity in a very low
> > level for a really long time. To meet requirements we do have to
> maintain a
> > copy inside our community.
> > 2. Hessian works as a serialization protocol in Dubbo and has been widely
> > used by users. It’s the core part of an RPC framework, most users will
> stay
> > on Hessian and won’t change.
> >
> > >  are some of those developers involved here?
> >
> > I remember Xin Wang in ou

Re: [Announce] Dubbo Spring Boot 2.7.5 released

[Xin Wang]

Mercy, thank you for your hard work .


Has the code of 2.7.5-release branch been merged into the master branch  ？

Mercy Ma  于2020年1月3日周五 下午2:59写道：

> Hello Dubbo Community,
>
> I am glad to announce that Dubbo Spring Boot 2.7.5 was released.
>
> You can check detailed release notes here:
> https://github.com/apache/dubbo-spring-boot-project/releases/tag/2.7.5
>
> If you have any questions using this version, please send mail to here or
> report the issue on Github
> .
>
> Best regards,
> Mercy Ma
>

Re: [VOTE] Accept RitterHou/python-dubbo donation

[Xin Wang]

+1 accept


Minxuan Zhuang  于2019年9月24日周二 上午10:57写道：

> +1 accept
>
> On Tue, Sep 24, 2019 at 10:55 AM yuhang xiu  wrote:
>
> > +1 accept
> > Dubbo's ecology continues to expand. :)
> >
> > Ian Luo  于2019年9月24日周二 上午10:53写道：
> >
> > > Hi All,
> > >
> > > This is a formal vote to bring RitterHou/python-dubbo[1], which is
> > donated
> > > by Qianmi, to Apache Dubbo project.
> > >
> > > Please vote:
> > >
> > > [ ] +1 Accept
> > > [ ] +0 No Opinion
> > > [ ] -1 Reject because...
> > >
> > >
> > > [1] https://github.com/RitterHou/python-dubbo
> > >
> >
>

Re: [ANN] Welcome new committer: Xinming He

[Xin Wang]

Congratulations！

Furkan KAMACI  于2019年7月30日周二 下午9:13写道：

> Hi,
>
> Congrats Xinming!
>
> Kind Regards,
> Furkan KAMACI
>
> On Tue, Jul 30, 2019 at 1:58 PM Jerrick Zhu  wrote:
>
> > Congrats.
> >
> >
> >
> >  于2019年7月26日周五 下午11:38写道：
> >
> > > Congratulations！
> > >
> > >
> > >
> > > | |
> > > 曹杰乐
> > > 邮箱：caojiele1...@126.com
> > > |
> > >
> > > 签名由 网易邮箱大师 定制
> > >
> > > On 07/26/2019 18:06, Huxing Zhang wrote:
> > > Hi Community,
> > >
> > > On behalf of the Dubbo PMC, I am pleased to announce that Xinming
> > > He[1], has been voted in as a new Dubbo committer.
> > >
> > > Please join me to say congratulations to him!
> > >
> > > Xinming, would you please briefly introduce yourself to the community?
> > >
> > > [1] https://github.com/hxmhlt
> > >
> > > --
> > > Best Regards！
> > > Huxing
> > >
> >
>

Re: [VOTE] Accept dubbogo/hessian2 donation

[Xin Wang]

+1 Accept

Huxing Zhang  于2019年7月4日周四 上午10:00写道：

> Hi All,
>
> This is a formal vote to bring dubbogo/hessian2[1], which is depended
> by dubbo-go, to Apache Dubbo project.
>
> Please vote:
>
> [ ] +1 Accept
> [ ] +0 No Opinion
> [ ] -1 Reject because...
>
> [1] https://github.com/dubbogo/hessian2
>
> --
> Best Regards！
> Huxing
>

Re: [ANN] Welcome new committer, Yuneng Xie

[Xin Wang]

Congratulations!

ShengXiao Xie  于2019年6月13日周四 下午8:56写道：

> Congratulations!
>
>
> > 在 2019年6月12日，10:18，Jun Liu  写道：
> >
> > Hi Community,
> >
> > On behalf of the Dubbo PMC, I am pleased to announce that
> > Yuneng Xie[1], a.k.a uglycow, has been voted in as a new Dubbo committer.
> >
> > Please join me to say congratulations to him!
> >
> > Yuneng, would you please briefly introduce yourself to the community?
> >
> > [1] https://github.com/uglycow
> >
> > Jun
> >
>
>
>

Re: [Proposal]Write A Book(Apache Dubbo: The Definitive Guide)

[Xin Wang]

+1 ， will take part in


彭辛航  于2019年6月10日周一 下午4:10写道：

> 希望直接基于最新的2.7.3进行讲解
>
> -邮件原件-
> 发件人: Huxing Zhang 
> 发送时间: 2019年6月10日 15:48
> 收件人: dev 
> 主题: Re: [Proposal]Write A Book(Apache Dubbo: The Definitive Guide)
>
> Hi,
>
> +1. Exciting news!
>
> On Thu, Jun 6, 2019 at 7:30 PM KimmKing  wrote:
> >
> > Hi, Community，
> > 随着微服务架构越来越流行，Apache
> Dubbo项目越来越火，最近我们的各种技术会议、沙龙，Dubbo的曝光和传播也越来越多。配合Dubbo社区生态的发展建设，目前我们非常适合推出一系列不同层次和侧重的Dubbo书籍了。就我了解，yiji和jingzhu将要出版一本
> 深入Apache Dubbo与实战，kirito也计划推出一本 Dubbo实战。越多Dubbo的书涌现，就意味着Dubbo的生态越发达。
> > 像其他各类开源技术一样，我们可以组织一下社区，直接整理修订官方文档，成为一本Dubbo的入门基础工具书（Apache
> Dubbo权威指南，Apache Dubbo: The Definitive
> Guide），作为前面两本书的补充。目前的官方文档比较全面，后续也可以基于英文文档推出英文版。
> >
> 这本书可以按照Dubbo社区的名义来出版，并将未来的版税作为Dubbo技术的发展经费来使用，比如第一笔版税全部用来购买初次印刷的本书籍，然后分发给各个Committer和Contributor作为后续一段时间内技术分享和技术沙龙时，跟现场参与者交互的赠品。
> >
> 此外，我私下问了几个contributor也都愿意参与这件有益于Dubbo发展的好事，我本人可以尝试组织人员启动这个项目，在1-2月左右完成初稿，在Q3结束前完成出版的各项准备工作。
> >大家有什么想法和建议， 非常期待大家的回复。
> >
> >
> > Hi, Community,
> > As the micro-service architecture becomes more and more popular, the
> Apache Dubbo project is so hot. Recently, we have various technical
> conferences, salons, and Dubbo have more and more exposures and spreads.
> With the development of the Dubbo community ecology, we are now very
> suitable to launch a series of Dubbo books of different levels and focuses.
> As far as I know, yiji and jingzhu will publish a book deep into Apache
> Dubbo quickly, kirito also plans to launch a Dubbo in Action. The more
> Dubbo's books emerge, the more developed Dubbo's ecology.
> >
> > Like other open source project, we can organize the community, directly
> polish and revise the official documentation, and become a Dubbo beginners'
> reference book (Apache Dubbo: The Definitive Guide), supplemented by the
> previous two books.  The current official documentation is more
> comprehensive, and the follow-up can also be a English Version book based
> on English documents.
> > The book can be published in the name of the Dubbo Community, and future
> royalties are used as development funds for Dubbo technology. For example,
> the first royalties are all used to purchase the first printed book, and
> then distributed to each Committer and Contributor as a follow-up
> paragraph. Giveaways to interact with live participants during technical
> sharing and technical salons.
> >
> > In addition, I privately asked a few contributors who are also willing
> to participate in this task that is good for Dubbo development. I can try
> to organize several contributors to start the project, complete the first
> draft around 1-2 months, and be ready of publication at the end of Q3.
> > Everyone has any ideas and suggestions?  I look forward to your reply.
> >
> >
> > -
> > kimmking
> > 2019-06-06
>
>
>
> --
> Best Regards！
> Huxing
>

Re: [ANN] Apache Dubbo as a Top-level project

[Xin Wang]

Congratulations!


ding peng  于2019年5月21日周二 下午1:06写道：

> Congratulations!
>
> BRs
> moriadry
>
>
> > On May 21, 2019, at 10:57 AM, YunKun Huang  wrote:
> >
> > Congratulations !
> > : )
> >
> > Huxing Zhang  于2019年5月21日周二 上午10:53写道：
> >
> >> Hi,
> >>
> >> Today ASF officially announced Apache Dubbo as a Top-level project[1].
> >> Congratulations to Dubbo!
> >>
> >> [1]
> >>
> https://blogs.apache.org/foundation/entry/the-apache-software-foundation-announces52
> >>
> >> --
> >> Best Regards！
> >> Huxing
> >>
>
>

Re: [DISCUSS] Migrating projects under dubbo group

[Xin Wang]

>   rpc-native-thrift-for-apache-dubbo

This is going to be merged into incubator-dubbo:
ETA is May 15.

Eric Zhao  于2019年4月25日周四 下午7:43写道：

> Hi,
>
> > How soon will to finish signing SGA? Could you please give an ETA?
>
> I've finished signing both the ICLA and SGA. Please check.
>
> > I can help to request the INFRA to transfer, I am thinking to group
> them together.
>
> Thanks!
>
>
> --
> Best Regards,
> Eric
>
> Huxing Zhang  于2019年4月25日周四 下午5:37写道：
>
> > Hi,
> >
> > On Thu, Apr 25, 2019 at 5:28 PM Eric Zhao  wrote:
> > >
> > > Hi there,
> > >
> > > I'm the author of dubbo-sentinel-support. I'd like to transfer the
> > project
> > > to ASF.
> > >
> > > 1) are you willing to transferred to ASF or not.
> > >
> > > Yes
> >
> > Nice.
> >
> > >
> > > > 2) if so, please give an estimated time when will you can finish
> > transfer.
> > > > What you will need to do includes:
> > > > - Find the all the contributors and ask them to sign the Apache
> > > > ICLA[2], if the contribution is trivial, this can be ignore
> > >
> > > I'll sign the ICLA today.
> >
> > >
> > > > - If the code belongs to your company, you need to sign the SGA[3]
> > > > - request ASF infra to transfer the project
> >
> > How soon will to finish signing SGA? Could you please give an ETA?
> >
> > >
> > > Seems that I don't have the permission to transfer the project. Could
> you
> > > please help me to transfer the project?
> >
> > I can help to request the INFRA to transfer, I am thinking to group
> > them together.
> >
> > >
> > > ---
> > > Best Regards,
> > > Eric
> > >
> > > Huxing Zhang  于2019年4月25日周四 下午4:25写道：
> > >
> > > > Hi,
> > > >
> > > >
> > > > On Thu, Apr 25, 2019 at 4:02 PM Huxing Zhang 
> > wrote:
> > > > >
> > > > > Hi All,
> > > > >
> > > > > As is discussed in the graduation proposal in general@ mailing
> list,
> > > > > the github.com/dubbo group has some potential branding issue. To
> > avoid
> > > > > it completely, we need to decide the short-term plan and long-term
> > > > > plan.
> > > > >
> > > > > For the short-term plan, there are two way proposed:
> > > > >
> > > > > 1. Rename dubbo group to another one, let's say A.
> > > > > 2. Create a new group A, and migrate all the project to under A,
> and
> > > > > keep the dubbo group empty. The purpose is to avoid someone to
> abuse
> > > > > it in the future.
> > > > >
> > > > > I am leaning towards option 2. But I'd like to hear what other may
> > think.
> > > > >
> > > > > The next step is to decide what A is.  Actually naming a thing is
> one
> > > > > of the most difficult thing to do... I am trying to find something
> > > > > related. I checked the wikipedia page for Dubbo[1], in the history
> > > > > section, it says  Dubbo is now thought to be a mispronunciation of
> > the
> > > > > local Wiradjuri word "Thubbo" or "Tubbo".
> > > > >
> > > > > I think thubbo and tubbo both are good. thubbo is more different to
> > > > > dubbo than tubbo. So I prefer thubbo. How do you think?
> > > > >
> > > > >
> > > > > For the long-term plan:
> > > > >
> > > > > 1. Like discussed before, all projects under group A are expected
> to
> > > > > be transferred to Apache (if the owner) agree with an ETA. I talked
> > to
> > > > > most of the owners and they basically agree, the multi-language
> > > > > project are TODOs. I am trying to pull them onto list.
> > > > >
> > > > > This projects that still listed under dubbo group includes:
> > > > >
> > > > > * js-for-apache-dubbo
> > > > > * py-client-for-apache-dubbo
> > > > > * rpc-xmlrpc-for-apache-dubbo
> > > > > * jmeter-plugins-for-apache-dubbo
> > > > > * go-for-apache-dubbo
> > > > > * php-framework-for-apache-dubbo
> > > > > * dotnet-for-apache-dubbo
> > > > > * serialization-native-hessian-for-apache-dubbo
> > > > > * jms-for-apache-dubbo
> > > > > * dubbo.github.io
> > > >
> > > > I suggest to redirect dubbo.io directly to dubbo.apache.org from DNS
> > > > and remote this project. I think it can be done before May 31.
> > > >
> > > > > * metrics
> > > >
> > > > This project has no strong relation to Dubbo, I suggest to move it to
> > > > alibaba group, I think it can be done before May 10.
> > > >
> > > > > * hessian-lite
> > > >
> > > > This project has no strong relation to Dubbo, I suggest to move it to
> > > > alibaba group, I think it can be done before May 10.
> > > >
> > > > > * dubbo-sentinel-support
> > > > > * awesome-dubbo
> > > >
> > > > I suggest to transfer to ASF, most of the contributors are Dubbo
> PPMC.
> > > > I think it can be done before May 31.
> > > >
> > > > > * dubbo-remoting-js
> > > > > * egg-dubbo-rpc
> > > > > * rpc-native-thrift-for-apache-dubbo
> > > > > * intellij-idea-plugin
> > > > > * initializr
> > > >
> > > > I suggest to go to ASF if license is OK, otherwise go to alibaba.
> > > > Depending on the case, I think it can be done before May 31.
> > > >
> > > > >
> > > > >
> > > > > If you are the project owner, could you please confirm that:
> > > > >
> > > > > 1) are you willing to 

Re: [VOTE] Apache Dubbo graduation to Top Level Project

[Xin Wang]

+1 to  recommend graduation of Apache Dubbo as a TLP

Huxing Zhang  于2019年4月18日周四 下午8:24写道：

> Hi All,
>
> After a discussion in the Apache Dubbo community on the dev mailing
> list[1], choosing PMC chair[2], forming the PMC members[3], completing
> the maturity model[4], and discussing the resolution proposal[5], I
> would like to call a vote for Apache Dubbo graduating to a top level
> project.
>
> Please vote on the proposal to graduate Dubbo as TLP to submit to the
> Incubator PMC.
>
> Vote:
> [ ] +1 - Recommend graduation of Apache Dubbo as a TLP
> [ ] -1 - Do not recommend graduation of Apache Dubbo because ….
>
> The VOTE is open for a minimum of 72 hours.
>
> [1]
> https://lists.apache.org/thread.html/767da61f249789f09665a52a241e3b352d168fec051ee7dd1dd7c20b@%3Cdev.dubbo.apache.org%3E
> [2]
> https://lists.apache.org/thread.html/537a7a88ab19ffee31c0b642ff6239372aa063985846febe2ad11d91@%3Cdev.dubbo.apache.org%3E
> [3]
> https://lists.apache.org/thread.html/b7218b3b441f7a96e1d339e1eeea60e8bba9b06295e73b56659524c0@%3Cdev.dubbo.apache.org%3E
> [4]
> https://github.com/apache/incubator-dubbo/wiki/Apache-Maturity-Model-Assessment-for-Dubbo
> [5]
> https://lists.apache.org/thread.html/2b9fb2c565656308dcce5281c5352da41d5aabc56020af084c6888d3@%3Cdev.dubbo.apache.org%3E
>
> -
> Establish the Apache Dubbo 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 high-performance, lightweight, java based RPC framework.
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> (PMC), to be known as the "Apache Dubbo Project", be and hereby is
> established pursuant to Bylaws of the Foundation; and be it further
>
> RESOLVED, that the Apache Dubbo Project be and hereby is responsible for
> the creation and maintenance of software related to a high-performance,
> lightweight, java based RPC framework; and be it further
>
> RESOLVED, that the office of "Vice President, Apache Dubbo" 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 Dubbo
> Project, and to have primary responsibility for management of the
> projects within the scope of responsibility of the Apache Dubbo 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 Dubbo Project:
>
>  * Huxing Zhang   
>  * Ian Luo
>  * Jun Liu
>  * Justin Mclean  
>  * Kimm King  
>  * Liang Zhang
>  * Liujie Qin 
>  * Mercy Ma   
>  * Minxuan Zhuang 
>  * Shang Zonghai  
>  * Von Gosling
>  * Xin Wang   
>  * Yong Zhu   
>  * Yuhang Xiu 
>  * YunKun Huang   
>
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Ian Luo be appointed to the
> office of Vice President, Apache Dubbo, 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 Dubbo Project be and hereby is tasked with the
> migration and rationalization of the Apache Incubator Dubbo podling; and
> be it further
>
> RESOLVED, that all responsibilities pertaining to the Apache Incubator
> Dubbo podling encumbered upon the Apache Incubator PMC are hereafter
> discharged.
>
> --
> Best Regards！
> Huxing
>

Re: [IMPORTANT][PPMC] Invitation to be Dubbo PMC member

[Xin Wang]

YES

Jun Liu  于2019年4月9日周二 上午10:16写道：

> YES
>
> Jun
>
> > On Apr 9, 2019, at 10:12 AM, Huxing Zhang  wrote:
> >
> > Dear Dubbo PPMC members,
> >
> > (bcc to all PPMC members)
> >
> > The Dubbo community is discussing the graduation of Dubbo to be a Top
> > Level project of Apache Software Foundation in the dev mailing list.
> > As one of the steps towards graduation, the community needs to set up
> > list of Project Management Committees (PMC) members after graduation,
> > which will be included in the graduation resolution.
> >
> > The role of the PMC is included as follows[1]:
> >
> > The role of the PMC from a Foundation perspective is oversight. The
> > main role of the PMC is not code and not coding - but to ensure that
> > all legal issues are addressed, that procedure is followed, and that
> > each and every release is the product of the community as a whole.
> > That is key to our litigation protection mechanisms.
> >
> > Secondly the role of the PMC is to further the long term development
> > and health of the community as a whole, and to ensure that balanced
> > and wide scale peer review and collaboration does happen. Within the
> > ASF we worry about any community which centers around a few
> > individuals who are working virtually uncontested. We believe that
> > this is detrimental to quality, stability, and robustness of both code
> > and long term social structures.
> >
> > If you are willing to be a PMC member after graduation, please respond
> > YES to this thread by replying to dev@dubbo.apache.org no later than
> > 2019-04-12 (Friday).
> > If you are not subscribing the private list, please remember to
> > subscribe to the private@ list.
> >
> >
> > [1] http://www.apache.org/foundation/how-it-works.html#pmc
> > --
> > Best Regards！
> > Huxing
>
>

Re: [DISCUSS] PMC Chair of Dubbo

[Xin Wang]

+ 1 to support Ian Luo  to become the PMC chair


Jun Liu  于2019年4月4日周四 上午10:59写道：

> He is also the right person for PMC chair in my mind.
>
> Jun
>
> > On Apr 4, 2019, at 10:26 AM, Huxing Zhang  wrote:
> >
> > Hi All,
> >
> > According to [1], in the "Preparing a Charter" section, we need to
> > decide PMC chair.
> > This is previously discussed on the "[DISCUSS] Graduate Apache
> > Dubbo(incubating) as a Top Level Project" thread, but it looks like it
> > is easily ignored. Therefore I am starting a dedicated thread to
> > discuss this.
> >
> > I personally am suggesting Ian Luo as PMC chair. Ian is leading the
> > Dubbo project, and has rich experience in RPC/service framework. I
> > think he is the best candidate.
> >
> > How do others think?
> >
> > [1] https://incubator.apache.org/guides/graduation.html
> > --
> > Best Regards！
> > Huxing
>
>

Re: Re: [ANN] New PPMC member: Kimm King

[Xin Wang]

Congraduations

YunKun Huang  于2019年4月1日周一 下午7:02写道：

> Congraduations :)
>
>
> On 2019/04/01 09:03:14, KimmKing   wrote:
> > Thanks all of you.
> >
> >
> >
> > : )
> >
> > 在 2019-04-01 10:52:26，"华 钟明"  写道：
> > >Congraduations ! __
> > >
> > >Best Regards！
> > >Zhongming Hua
> > >
> > >
> > >在 2019/4/1 上午10:50，“Jun Alpha” 写入:
> > >
> > >Congraduations
> > >
> > >徐靖峰  于2019年4月1日周一 上午10:24写道：
> > >
> > >> 666 Congraduations!
> > >>
> > >> > 在 2019年4月1日，上午10:13，Taosheng, Wei  写道：
> > >> >
> > >> > Congraduations :)
> > >> >
> > >> >
> > >> >
> > >> >
> > >> > -- Original --
> > >> > From: Huxing Zhang 
> > >> > Date: Mon,Apr 1,2019 10:12 AM
> > >> > To: dev 
> > >> > Subject: Re: [ANN] New PPMC member: Kimm King
> > >> >
> > >> >
> > >> >
> > >> > Hi Community,
> > >> >
> > >> > On behalf of the Dubbo PPMC, I am pleased to announce that Kimm
> King[1]
> > >> > has been voted in as a new Dubbo PPMC member.
> > >> >
> > >> > Please join me to say congratulations to him!
> > >> >
> > >> > [1] https://github.com/kimmking
> > >> >
> > >> > --
> > >> > Best Regards！
> > >> > Huxing
> > >>
> > >>
> > >>
> > >>
> > >
> >
>

Re: [apache/incubator-dubbo] Merge incubator-dubbo-rpc-jsonrpc into incubator-dubbo

[Xin Wang]

+1

Huxing Zhang  于2019年3月31日周日 下午4:58写道：

> Hi,
>
> +1, I also filed an issue to merge xmlprc to incubator-dubbo.
>
> On Fri, Mar 29, 2019 at 10:16 AM 徐靖峰  wrote:
> >
> > Hi
> >
> > I want to Merge incubator-dubbo-rpc-jsonrpc(
> https://github.com/apache/incubator-dubbo-rpc-jsonrpc <
> https://github.com/apache/incubator-dubbo-rpc-jsonrpc>) into
> incubator-dubbo. Package name and author information will be refactored.
> >
>
>
> --
> Best Regards！
> Huxing
>

Re: commit to master branch by mistake

[Xin Wang]

I  think you can rollback  to the latest -1 commit  by command:

git reset –hard commit-id



Xianjun Ke  于2019年3月16日周六 下午9:52写道：

> Hi community,
> I'm sorry,When I'm trying to fix 3678[1], I commited to the master branch
> by mistake.What should I
> do to revert this commit[2] ?
>
>
> [1] https://github.com/apache/incubator-dubbo/issues/3678
> [2]
>
> https://github.com/apache/incubator-dubbo/commit/affc976120356c93a44f98f612184c06e8ddf09f
>

Re: Add a test-dubbo project in the dubbo group

[Xin Wang]

>   PelicanDT is an integrated test solution for distributed applications.
It helps developers to test distributed applications easily and
efficiently. It can easily implement automatic integration testing of Dubbo.
hi，junyang
There is an issue [1] that plans for integration testing and performance
testing. Can you briefly explain how to realize the  test?

1. How to organize integration test cases?
2. How to display the test results online ?


[1] https://github.com/apache/incubator-dubbo/issues/2508

jun liu  于2019年3月7日周四 下午8:48写道：

> Hi, junyang
>
> > The goal of the test-dubbo project is to bring together more tools for
> verifying Dubbo, such as integration testing, performance testing, high
> availability testing, etc., making Dubbo's testing easier and more
> efficient.
>
> We have been thinking of implementing "automatic integration test" on the
> basis of incubator-dubbo-samples[1], can you help to see what steps should
> be done to realize that?
>
> Jun
>
> > On Mar 7, 2019, at 6:52 PM, junyang.zjy 
> wrote:
> >
> > Hi,
> >
> > The goal of the test-dubbo project is to bring together more tools for
> verifying Dubbo, such as integration testing, performance testing, high
> availability testing, etc., making Dubbo's testing easier and more
> efficient.
> >
> > PelicanDT is an integrated test solution for distributed applications.
> It helps developers to test distributed applications easily and
> efficiently. It can easily implement automatic integration testing of Dubbo.
> >
> >
> >> 在 2019年3月6日，下午9:51，Huxing Zhang  写道：
> >>
> >> Hi,
> >>
> >> Can you elaborate more on what you would like to achieve in this
> project?
> >> Do you mean by something like integration test for Dubbo?
> >> I think it is good to have some automatic integration test for Dubbo.
> >> A framework that runs the samples under incubator-dubbo-samples, and
> >> to test against every release candidate, or even nightly build.
> >> I could be placed under dubbo group at first, once it get mature
> >> enough, it can be brought to Apache.
> >>
> >> On Wed, Mar 6, 2019 at 4:03 PM junyang.zjy 
> wrote:
> >>>
> >>> Dubbo is now a very good open source product, whether to consider
> adding a test-dubbo project in the dubbo group,
> similar to test-infra under kubernates, gathering a collection of tools to
> testing dubbo and displaying dubbo tests results.
> >>
> >>
> >>
> >> --
> >> Best Regards！
> >> Huxing
> >
>
>

Re: [ANN] Welcome new committer: Zhen Li

[Xin Wang]

Congratulations!


jun liu  于2019年3月7日周四 下午8:43写道：

> Congratulations!
>
> Jun
>
> > On Mar 6, 2019, at 6:19 PM, Yuhao Bi  wrote:
> >
> > Welcome and Congratulations!
> >
> > kezhenx...@163.com  于2019年3月6日周三 下午5:45写道：
> >
> >>
>
>

Re: [ANN] Welcome new committer: Zhenxu Ke

[Xin Wang]

Congratulations!


jun liu  于2019年3月7日周四 下午8:43写道：

> Congratulations!
>
> Jun
>
> > On Mar 5, 2019, at 9:37 PM, Huxing Zhang  wrote:
> >
> > Hi Zhenxu,
> >
> > Congratulations and welcome!  Would you please also update your
> > information (including your affiliation) to the official website?
> >
> >
> > On Tue, Mar 5, 2019 at 6:24 PM kezhenxu94  wrote:
> >>
> >> Hi The Dubbo Community:
> >>   Thank you all for your recognition and congratulations. My name is
> Zhenxu Ke.
> >> Now I work as a Full-Stack Engineer at lizhi.fm. I'm very interested
> in micro-services
> >> and enthusiastic about open-sourcing. I'll continuously contribute to
> the Dubbo project
> >> with community to make it better and easy use. Thanks again!!
> >>
> >> Best Regards！
> >> Zhenxu Ke
> >>
> >> On 2019/3/5 15:57, Minxuan Zhuang wrote:
> >>> Hi Community,
> >>>
> >>> On behalf of the Dubbo PPMC, I am pleased to announce that Zhenxu Ke,
> >>> a.k.a. kezhenxu94[1], has been voted in as a new Dubbo committer.
> >>>
> >>> Please join me to say congratulations to him!
> >>>
> >>> Zhenxu, would you please briefly introduce yourself to the community?
> >>>
> >>> [1] *https://github.com/kezhenxu94 *
> >>>
> >>
> >
> >
> > --
> > Best Regards！
> > Huxing
>
>

Re: Some problem in incubator-dubbo-samples

[Xin Wang]

Please send a pr to delete the useless files

Xianjun Ke  于2019年2月17日周日 下午6:11写道：

> recently I found that something wrong with incubator-dubbo-samples project,
> I think it's introduced
> when mergeing branch 2.7.0, pls refer to this issue [1], and we need to fix
> it.
>
> [1] https://github.com/apache/incubator-dubbo-samples/issues/57
>

Re: [ANN] Welcome new committer: Zhongming Hua

[Xin Wang]

Awesome ！   Congratulations
Huxing Zhang  于2019年2月15日周五 下午5:03写道：

> Hi,
>
> Congratulations and welcome!
>
> For the record, Iflytek is 科大讯飞, which is a famous voice recognition
> company in China.
> It is glad to see Iflytek is using Dubbo.
> It will be great if you could share some practices in production. :)
>
>
>
> On Fri, Feb 15, 2019 at 1:14 PM 华 钟明  wrote:
> >
> > Hi community,
> > Thank you all for the congratulations. My name is Zhongming Hua. I am a
> Software Engineer in Iflytek. Since I took over the business development
> related to the Dubbo framework, I started to study Dubbo in depth and try
> to provide my contribution to the community. I also hope that the Dubbo
> will be better with the community.
> >
> > Best Regards！
> > Zhongming Hua
> >
> >
> > 在 2019/2/15 下午12:29，“Imteyaz Khan” 写入:
> >
> > Congratulations.
> >
> > On Friday, February 15, 2019, LiZhenNet 
> wrote:
> >
> > > Congratulations
> > >
> > > Taosheng, Wei  于2019年2月15日周五 上午10:15写道：
> > >
> > > > Congratulations and welcome!
> > > >
> > > >
> > > >
> > > >
> > > > -- Original --
> > > > From: Huxing Zhang 
> > > > Date: Fri,Feb 15,2019 10:12 AM
> > > > To: dev 
> > > > Subject: Re: [ANN] Welcome new committer: Zhongming Hua
> > > >
> > > >
> > > >
> > > > Hi Community,
> > > >
> > > > On behalf of the Dubbo PPMC, I am pleased to announce that
> Zhongming Hua,
> > > > a.k.a. CrazyHZM[1], has been voted in as a new Dubbo committer.
> > > >
> > > > Please join me to say congratulations to him!
> > > >
> > > > Zhongming, would you please briefly introduce yourself to the
> community?
> > > >
> > > > [1] https://github.com/CrazyHZM
> > > >
> > > > --
> > > > Best Regards！
> > > > Huxing
> > >
> >
>
>
> --
> Best Regards！
>
> Huxing
>

How to integrate dubbo-registry-nacos into Fescar project?

[Xin Wang]

Hi all,
Now the Fescar project[0] will integrate dubbo-registry-nacos[1], but
there are two issues:
*  dubbo-registry-nacos[1] has no release version
*  I know dubbo-registry-nacos is being merged into Dubbo main repo [2],
 Then what kind of Maven dependency do you recommend?

 org.apache.dubbo
 dubbo
   or
   com.alibaba
   dubbo

[0] https://github.com/alibaba/fescar/
[1] https://github.com/dubbo/dubbo-registry-nacos
[2]
https://lists.apache.org/thread.html/a6753eee2f7098fcaaf12b24d5496b9f1d3f21f52ffdbc5a808ddd89@%3Cdev.dubbo.apache.org%3E

Re: [ANN] Welcome new committer: Yuhao Bi

[Xin Wang]

congratulations

在 2019年2月3日星期日，Ian Luo  写道：

> Congratulations.
>
> On Sun, Feb 3, 2019 at 9:35 AM Huxing Zhang  wrote:
>
> > Hi Community,
> >
> > On behalf of the Dubbo PPMC, I am pleased to announce that Yuhao Bi,
> > a.k.a. biyuhao[1], has been voted in as a new Dubbo committer.
> >
> > Please join me to say congratulations to him!
> >
> > Yuhao, would you please briefly introduce yourself to the community?
> >
> > [1] https://github.com/biyuhao
> >
> > --
> > Best Regards！
> > Huxing
> >
>

Re: Release check list

[Xin Wang]

I think these can be added:

1. Who can be release manager ?
2. Who can vote and what to check ?
3. Simple voting process and completion criteria ?

Huxing Zhang  于2019年2月1日周五 下午6:01写道：

> Hi,
>
> On Fri, Feb 1, 2019 at 5:55 PM Xin Wang  wrote:
> >
> > Should the  Release notes[1] be removed to Release Guide [2] ?
> > Then it is easy to find
>
> +1. I add the release guide with the link but not have enough time to move
> it.
> I am planning to work on it.
> Another problem is the Chinese version is behind the English version,
> I am planning to update it.
>
> >
> >  [1] http://dubbo.apache.org/en-us/blog/prepare-an-apache-release.html
> >  [2]
> >
> http://dubbo.apache.org/en-us/docs/developers/committer-guide/release-guide_dev.html
> >
> >
> >
> > Ian Luo  于2019年2月1日周五 下午5:37写道：
> >
> > > Agree, more eyes, more secure.
> > >
> > > On Fri, Feb 1, 2019 at 5:21 PM Huxing Zhang  wrote:
> > >
> > > > Hi,
> > > >
> > > > On Fri, Feb 1, 2019 at 4:08 PM Xin Wang 
> > > wrote:
> > > > >
> > > > > I think the template url  should be added to
> > > > > http://dubbo.apache.org/en-us/blog/prepare-an-apache-release.html
> > > >
> > > > I think it is not only the release manager and PPMC's responsibility
> > > > to do the check, anyone in this community can participate in the
> > > > release vote.
> > > >
> > > > The important thing is that we should let everyone in this community
> > > > to know that we welcome them to participate, because participate in
> > > > the release vote is am important way of making contribution.
> Meanwhile
> > > > they should know how to do it.
> > > >
> > > > I agree to add it, and I also think we should add it to new
> contributor
> > > > guide.
> > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > Huxing Zhang  于2019年2月1日周五 下午3:39写道：
> > > > >
> > > > > > Hi All,
> > > > > >
> > > > > > Out mentor Justin has provided a check list[1] for release,
> which I
> > > > > > think it is a very good guide when doing release check for the
> > > ongoing
> > > > > > release vote for spring-boot-starter and dubbo-ops
> > > > > >
> > > > > > Hopefully more users could know that what does an Apache release
> > > means
> > > > > > and what needs to be checked, and more importantly, could help
> to do
> > > > > > the checks.
> > > > > >
> > > > > > [1] https://wiki.apache.org/incubator/IncubatorReleaseChecklist
> > > > > > --
> > > > > > Best Regards！
> > > > > > Huxing
> > > > > >
> > > >
> > > >
> > > >
> > > > --
> > > > Best Regards！
> > > > Huxing
> > > >
> > >
>
>
>
> --
> Best Regards！
> Huxing
>

Re: Release check list

[Xin Wang]

I think the template url  should be added to
http://dubbo.apache.org/en-us/blog/prepare-an-apache-release.html




Huxing Zhang  于2019年2月1日周五 下午3:39写道：

> Hi All,
>
> Out mentor Justin has provided a check list[1] for release, which I
> think it is a very good guide when doing release check for the ongoing
> release vote for spring-boot-starter and dubbo-ops
>
> Hopefully more users could know that what does an Apache release means
> and what needs to be checked, and more importantly, could help to do
> the checks.
>
> [1] https://wiki.apache.org/incubator/IncubatorReleaseChecklist
> --
> Best Regards！
> Huxing
>

Re: [ANN] Welcome new committer: Kun Song

[Xin Wang]

Congratulations!

Imteyaz Khan  于2019年1月30日周三 下午3:17写道：

> Congratulations .
>
> On Wed, Jan 30, 2019 at 12:25 PM Mercy  wrote:
>
> > Congratulations! 
> >
> > Kind regards,
> > Mercy Ma
> >
> > 在 2019/1/30 上午10:01, Huxing Zhang 写道:
> > > Hi Community,
> > >
> > > On behalf of the Dubbo PPMC, I am pleased to announce that Kun Song,
> > > a.k.a. satansk[1], has been voted in as a new Dubbo committer.
> > >
> > > Please join me to say congratulations to him!
> > >
> > > Kun, would you please briefly introduce yourself to the community?
> > >
> > > [1] https://github.com/satansk
> > >
> >
>

Re: [ANN] Welcome new committer: Xianjun Ke

[Xin Wang]

Congratulations

Imteyaz Khan  于2019年1月25日周五 下午1:24写道：

> Congratulations...
>
> On Friday, January 25, 2019, Xianjun Ke  wrote:
>
> > Hi community,
> > It's an honor for me to become a committer of Dubbo.
> > My name is Xianjun Ke,working in HangZhou caocaokeji as a senior software
> > engineer.
> > I'll keep contributing to the community,let's make Apache Duddo better
> and
> > better.
> >
> > Taosheng, Wei  于2019年1月25日周五 上午11:56写道：
> >
> > > Congratulations  and welcome :)
> > >
> > >
> > >
> > >
> > > -- Original --
> > > From: LiZhenNet 
> > > Date: Fri,Jan 25,2019 11:48 AM
> > > To: dev 
> > > Subject: Re: [ANN] Welcome new committer: Xianjun Ke
> > >
> > >
> > >
> > > Congratulations ,  Thanks for your advices for my pull request.
> > >
> > > yuhang xiu  于2019年1月25日周五 上午11:46写道：
> > >
> > > > Hi, xianjun, I think your review is great and gives a lot of valuable
> > > > advice.
> > > > Congratulations on becoming a committer!
> > > >
> > > > Huxing Zhang  于2019年1月25日周五 上午11:40写道：
> > > >
> > > > > Hi Community,
> > > > >
> > > > > On behalf of the Dubbo PPMC, I am pleased to announce that Xianjun
> > Ke,
> > > > > a.k.a. kexianjun[1], has been voted in as a new Dubbo committer.
> > > > >
> > > > > Please join me to say congratulations to him!
> > > > >
> > > > > Xianjun, would you please briefly introduce yourself to the
> > community?
> > > > >
> > > > > [1] https://github.com/kexianjun
> > > > >
> > > > > --
> > > > > Best Regards！
> > > > > Huxing
> > > > >
> > > >
> >
>

Re: [Discuss] About Clean Code Plan

[Xin Wang]

+1 to support use the new features  , but test case should be added to
ensure the functions

LiZhenNet  于2019年1月25日周五 上午11:46写道：

> In addition ,There are too many duplicate codes in source code.
> And I will do some work at this weekend about this plan.
>
> Kun Song  于2019年1月25日周五 上午11:43写道：
>
> > Since 2.7 Java 8 is supported，anyone can use it now.
> >
> > 发自我的 iPhone
> >
> > > 在 2019年1月25日，上午11:24，LiZhenNet  写道：
> > >
> > > Now ,Dubbo has 167 contributors , 3125 commits. There are a lot of
> unused
> > > methods ,unused logic , nonstandard naming  in the code. And there are
> > some
> > > code that can use the new features of java to make the code more
> concise
> > > and understandable. like Lambda , Diamond Operator and so on.These are
> > easy
> > > to find and fixed because of the tips of the idea .We should do it
> before
> > > completing the incubation.
> >
>

Re: [ANN] Welcome new committer: Taosheng Wei

[Xin Wang]

Congratulations!

jun liu  于2019年1月24日周四 上午10:22写道：

> Hi, Taosheng
>
> Congratulations.
>
> Jun
>
> > On Jan 23, 2019, at 2:47 PM, Taosheng, Wei 
> wrote:
> >
> > Hi community,
> > I am honored to become part of Apache Dubbo community.
> > My name is Taosheng Wei, I am in Beijing. I am a server software
> engineer, working in a financial technology corporation focusing fund
> clearing of online pay.
> > I will keep contributing to the community. Let’s do our best to make
> Apache Dubbo community better and better.
> >
> >
> > Best regards,
> > Taosheng
> >
> >
> >
> >
> >
> > -- Original --
> > From: Huxing Zhang 
> > Date: Wed,Jan 23,2019 2:07 PM
> > To: dev 
> > Subject: Re: [ANN] Welcome new committer: Taosheng Wei
> >
> >
> >
> > Hi Community,
> >
> > On behalf of the Dubbo PPMC, I am pleased to announce that Taosheng Wei,
> > a.k.a. tswstarplanet[1], has been voted in as a new Dubbo committer.
> >
> > Please join me to say congratulations to him!
> >
> > Taosheng, would you please briefly introduce yourself to the community?
> >
> > [1] https://github.com/tswstarplanet
> >
> > --
> > Best Regards！
> > Huxing
>
>

Re: [DISCUSS]: Some thoughts on What Dubbo 3.0 is, we really should start it ASAP

[Xin Wang]

>  - Reative programming and its fundamental FP start to get adopted. We
should consider to support it.

It looks like we're thinking about "full stack asynchronization" , I think
the Spring4 shoud be upgraded to spring5

Although Spring is an optional component in Dubbo,  but spring 5 provides
some asynchronous features, such as webFlux,
 which integrates Rxjava

Here is the 《Upgrading to Spring Framework 5.x》[1] , I translated it
Chinese and wrote some opinions  of my own [2].

[1]
https://github.com/spring-projects/spring-framework/wiki/Upgrading-to-Spring-Framework-5.x
[2] http://lovepoem.github.io/2018/09/05/framework/spring5_new_features/

Ian Luo  于2019年1月23日周三 上午11:11写道：

> Thanks for Yuhao raising this good point. In my opinion, both ACL and
> transaction are important to Dubbo, and the community keep demanding the
> support on these areas. We should put them in our roadmap.
>
> Thanks,
> -Ian.
>
>
> On Tue, Jan 22, 2019 at 10:55 PM Yuhao Bi  wrote:
>
> > Hi lan and community,
> >
> > Although I have already heard "Dubbo" a few years ago,
> > but I just started to learn dubbo after the meetup last year in Chengdu
> > after it became the Apache Dubbo.
> > Maybe I'm not such that familiar with the underlying details, but after
> > the continuous participated
> > I feel like a part of the community, and free to share my opinion.
> >
> > So, here is my question and also consider it my suggestion:
> > Should we care more about Security? How can we prevent from unauthorized
> > remote call?
> > - Should we support Authentication and Authorization
> > - Should we add Spring Security or Active Directory Service support at
> the
> > framework level
> >
> > Thanks,
> > Yuhao
> >
> >
> > jun liu  于2019年1月22日周二 下午5:50写道：
> >
> > > > I think the online integration test and performance test environment
> > > should
> > > > be set up for the new features.
> > >
> > > Agree!  We should start as soon as possible, from 2.7.x.
> > >
> > > Jun
> > >
> > > > On Jan 22, 2019, at 5:43 PM, Xin Wang 
> > wrote:
> > > >
> > > > I think the online integration test and performance test environment
> > > should
> > > > be set up for the new features.
> > > >
> > > > Ian Luo  于2019年1月22日周二 下午3:04写道：
> > > >
> > > >> Yuhao, good idea.
> > > >>
> > > >> BTW, do you have any thought on what Dubbo 3.0 should be?
> > > >>
> > > >> Thanks,
> > > >> -Ian.
> > > >>
> > > >>
> > > >> On Tue, Jan 22, 2019 at 2:39 PM Yuhao Bi  wrote:
> > > >>
> > > >>> Once we have decided what to do in the next.
> > > >>> Should we have a website page to publish it? e.g. [1]
> > > >>>
> > > >>> [1]. https://phoenix.apache.org/roadmap.html
> > > >>>
> > > >>> yuneng xie  于2019年1月22日周二 下午2:25写道：
> > > >>>
> > > >>>> Hi Ian Luo,
> > > >>>>
> > > >>>> OK, i'd start to work on it soon.
> > > >>>>
> > > >>>> Ian Luo  于2019年1月17日周四 下午2:01写道：
> > > >>>>
> > > >>>>> Hi Yuneng,
> > > >>>>>
> > > >>>>> Sounds interesting. I am especially interested in reactive
> > > >> programming
> > > >>>>> support. Pls. go ahead to try implement it on 3.x branch.
> > > >>>>>
> > > >>>>> Thanks,
> > > >>>>> -Ian.
> > > >>>>>
> > > >>>>> On Thu, Jan 17, 2019 at 11:03 AM yuneng xie  >
> > > >>> wrote:
> > > >>>>>
> > > >>>>>> Hi folks,
> > > >>>>>>
> > > >>>>>> I agreed with Ian Luo on the improvement list. I also got some
> > idea
> > > >>> in
> > > >>>> my
> > > >>>>>> mind.  I'd just share with you two points below in detail which
> > i'm
> > > >>>> most
> > > >>>>>> interested in right now.
> > > >>>>>>
> > > >>>>>> 1. Upgrade  the core abstraction "Invoker", which works in sync
> > > >> mode,
> > > >>>> to
> > > >>>

Re: [Notification of V2.7.0] Status, TODOs, Possible Release Schedules.

[Xin Wang]

> 2.7.0-release has just been merged into master, please help to review.

good job ,  now everyone can get the new features on the master branch

jun liu  于2019年1月22日周二 下午5:53写道：

> 2.7.0-release has just been merged into master, please help to review.
>
> Jun
>
> > On Jan 21, 2019, at 10:42 AM, Xin Wang  wrote:
> >
> >> I am merging back the 2.7.0-release branch to master to avoid having too
> > many conflicts if do it too late, then we may need to constantly do the
> > merge with every few days before vote is done.
> >
> > Support this , then everyone can review the code on the master branch ,
> > and find some issues earlier
> >
> > jun liu  于2019年1月21日周一 上午10:21写道：
> >
> >> I am merging back the 2.7.0-release branch to master to avoid having too
> >> many conflicts if do it too late, then we may need to constantly do the
> >> merge with every few days before vote is done.
> >>
> >> Jun
> >>
> >>> On Jan 18, 2019, at 2:28 PM, Huxing Zhang  wrote:
> >>>
> >>> Hi,
> >>>
> >>> I still found some inconsistency between the source release and the
> >>> Git tag dubbo-2.7.0:
> >>>
> >>> Only in apache-dubbo-incubating-2.7.0-source-release: all
> >>> Only in apache-dubbo-incubating-2.7.0-source-release: bom
> >>> Only in apache-dubbo-incubating-2.7.0-source-release: dependencies-bom
> >>> Only in apache-dubbo-incubating-2.7.0-source-release: distribution
> >>> Only in apache-dubbo-incubating-2.7.0-source-release: dubbo-bootstrap
> >>> Only in
> >>
> apache-dubbo-incubating-2.7.0-source-release/dubbo-config/dubbo-config-spring/src/test/resources:
> >>> work
> >>> Only in apache-dubbo-incubating-2.7.0-source-release/dubbo-demo:
> >>> dubbo-demo-consumer
> >>> Only in apache-dubbo-incubating-2.7.0-source-release/dubbo-demo:
> >>> dubbo-demo-provider
> >>> Only in apache-dubbo-incubating-2.7.0-source-release/dubbo-metrics:
> >>> dubbo-metrics-default
> >>> Only in apache-dubbo-incubating-2.7.0-source-release/dubbo-test:
> >>> dubbo-test-benchmark
> >>> Only in apache-dubbo-incubating-2.7.0-source-release/dubbo-test:
> >>> dubbo-test-examples
> >>>
> >>> It is possibly due to my local environment, I am going to do it again
> >>> with clean checkout of Dubbo 2.7.0-release branch.
> >>>
> >>> On Fri, Jan 18, 2019 at 10:25 AM Huxing Zhang 
> wrote:
> >>>>
> >>>> Hi,
> >>>>
> >>>> I found that there is a file test.patch in source release, which was
> >>>> the patch I used to restore the commit I reverted yesterday.
> >>>> This is not what we want, I am going to remove this file and
> re-tagging
> >> 2.7.0.
> >>>>
> >>>>
> >>>> On Fri, Jan 18, 2019 at 9:47 AM Huxing Zhang 
> wrote:
> >>>>>
> >>>>> Hi,
> >>>>>
> >>>>> On Fri, Jan 18, 2019 at 12:08 AM jun liu 
> wrote:
> >>>>>>
> >>>>>>> Jun, could you please summarize an English version of the release
> >> note.
> >>>>>>> I will send the vote email once it is done.
> >>>>>>
> >>>>>> It’s now available here:
> >>
> https://github.com/apache/incubator-dubbo/blob/2.7.0-release/CHANGES.md#270
> >>>>>
> >>>>> Thanks for that, it looks good to me.
> >>>>>
> >>>>>> I think it’s time to prepare the upgrade guide and user docs now,
> >> which is also a key part for this release.
> >>>>>
> >>>>> Yes, we can do that while we are doing the release vote.
> >>>>>
> >>>>> I am starting the vote today.
> >>>>>>
> >>>>>> Jun
> >>>>>>
> >>>>>>> On Jan 17, 2019, at 11:58 PM, Huxing Zhang 
> >> wrote:
> >>>>>>>
> >>>>>>> Hi,
> >>>>>>>
> >>>>>>> All the preparation seems going well.
> >>>>>>> I have successfully uploaded 2.7.0 to staging repo, and upload the
> >>>>>>> release candidate to svn.
> >>>>>>> I saw that the release note is still in Chinese.
> >>>>>>>
> >>>>>>&

Re: [DISCUSS]: Some thoughts on What Dubbo 3.0 is, we really should start it ASAP

[Xin Wang]

I think the online integration test and performance test environment should
be set up for the new features.

Ian Luo  于2019年1月22日周二 下午3:04写道：

> Yuhao, good idea.
>
> BTW, do you have any thought on what Dubbo 3.0 should be?
>
> Thanks,
> -Ian.
>
>
> On Tue, Jan 22, 2019 at 2:39 PM Yuhao Bi  wrote:
>
> > Once we have decided what to do in the next.
> > Should we have a website page to publish it? e.g. [1]
> >
> > [1]. https://phoenix.apache.org/roadmap.html
> >
> > yuneng xie  于2019年1月22日周二 下午2:25写道：
> >
> > > Hi Ian Luo,
> > >
> > > OK, i'd start to work on it soon.
> > >
> > > Ian Luo  于2019年1月17日周四 下午2:01写道：
> > >
> > > > Hi Yuneng,
> > > >
> > > > Sounds interesting. I am especially interested in reactive
> programming
> > > > support. Pls. go ahead to try implement it on 3.x branch.
> > > >
> > > > Thanks,
> > > > -Ian.
> > > >
> > > > On Thu, Jan 17, 2019 at 11:03 AM yuneng xie 
> > wrote:
> > > >
> > > > > Hi folks,
> > > > >
> > > > > I agreed with Ian Luo on the improvement list. I also got some idea
> > in
> > > my
> > > > > mind.  I'd just share with you two points below in detail which i'm
> > > most
> > > > > interested in right now.
> > > > >
> > > > > 1. Upgrade  the core abstraction "Invoker", which works in sync
> mode,
> > > to
> > > > an
> > > > > abstraction works in async mode. then we can construct
> > > > > InvocationChain/FilterChain that works in async mode.  A core
> > > abstraction
> > > > > works in async mode would simplify the sync/async logic. We  no
> > longer
> > > > need
> > > > > to repeat the logic about sync-mode/async-mode in each
> > ProtocolInvoker.
> > > > > ProtocolInvoker could concentrate on async logic and we could
> handle
> > > > > sync-mode invoke all in once by wrapping the AsyncInvocationChain
> > into
> > > a
> > > > > SyncInvocationChain.
> > > > >
> > > > > 2. Support using stream-value (Fowable, Flux...)  as
> > param/returnType.
> > > > > really a nice feature.
> > > > >
> > > > > Please let me known your opinion on my points. I'm also glad to
> just
> > > give
> > > > > it a try and raise a pr.
> > > > >
> > > > >
> > > > >
> > > > > Ian Luo  于2019年1月10日周四 下午6:00写道：
> > > > >
> > > > > > Hi folks,
> > > > > >
> > > > > > Finally we managed to ramp down version 2.7.0 development, and
> > > > hopefully
> > > > > we
> > > > > > can start the vote in the early of the next week. But the main
> > > purpose
> > > > of
> > > > > > this email is not a release announcement. Instead, since we now
> > have
> > > > > > bandwidth, let's consider and discuss what we should focus out
> from
> > > > many
> > > > > > stuff we want to do. For example, we may focus more on issue and
> > pull
> > > > > > request on GitHub, or we may plan 2.7 minor releases immediately
> > > after
> > > > we
> > > > > > release 2.7.0. But today I'd like to bring up one longer term
> plan
> > > > which
> > > > > > I'm now caring most, that is, how we define what version 3.0 is?
> > and
> > > > when
> > > > > > can we get start on it? In my opinion, we need to start it right
> > from
> > > > > this
> > > > > > moment.
> > > > > >
> > > > > > I recalled Liujie Qin (@liujieqin) initialed the discussion on
> the
> > > same
> > > > > > topic [1] in July this year. I summarize his points here if you
> are
> > > too
> > > > > > impatient to read through the contents of his email :p:
> > > > > >
> > > > > > 1. Need to enhance the current extension mechanism
> > > > > > 2. Need to enhance the code base for better maintenance
> > > > > > 3. Need to support async
> > > > > > 4. Need to decouple registry server and config server
> > > > > > 5. Need to support Java8 and above so that we can use advanced
> > > features
> > > > > in
> > > > > > Dubbo's core
> > > > > >
> > > > > > I agree with most of his points in this good proposal.
> > > > > >
> > > > > > Here I'd like to initial a discussion on how we define Dubbo 3.0,
> > or
> > > in
> > > > > the
> > > > > > other word, how do the community expect from Dubbo 3.0. In my
> > > opinion,
> > > > I
> > > > > > think we need to answer the following questions in this major
> > > release:
> > > > > >
> > > > > > - Today the boundary between messaging and remoting call gets
> blur.
> > > We
> > > > > may
> > > > > > need to consider to support streaming at the protocol level.
> > > > > > - Reative programming and its fundamental FP start to get
> adopted.
> > We
> > > > > > should consider to support it.
> > > > > > - Dubbo should be redesigned to support async better, and treats
> > > async
> > > > as
> > > > > > the first class citizen. We do support async feature in 2.7.0
> > release
> > > > but
> > > > > > it is not so perfect.
> > > > > > - Micro-services has been widely adopted. How Dubbo works
> > seamlessly
> > > > with
> > > > > > micro-services becomes a question mark. We need to look into the
> > > > inter-op
> > > > > > between Dubbo and micro-services's registry server/config server.
> > The
> > > > > > support on separating registry server and 

Wanted： who is using Dubbo + Thrift ?

[Xin Wang]

Hi all，
We want to know who uses Dubbo + thrift in production. You can refer to the
following examples to provide your information to collect usage scenarios
and deepen communication

我们想统计一下谁在生产中使用 Dubbo + thrift ，您可以参考下面的样例来提供您的信息以收集下使用场景，并加深交流

Please comment in the issue：
https://github.com/dubbo/dubbo-rpc-native-thrift/issues/16

Re: [Notification of V2.7.0] Status, TODOs, Possible Release Schedules.

[Xin Wang]

>  I am merging back the 2.7.0-release branch to master to avoid having too
many conflicts if do it too late, then we may need to constantly do the
merge with every few days before vote is done.

Support this , then everyone can review the code on the master branch ,
and find some issues earlier

jun liu  于2019年1月21日周一 上午10:21写道：

> I am merging back the 2.7.0-release branch to master to avoid having too
> many conflicts if do it too late, then we may need to constantly do the
> merge with every few days before vote is done.
>
> Jun
>
> > On Jan 18, 2019, at 2:28 PM, Huxing Zhang  wrote:
> >
> > Hi,
> >
> > I still found some inconsistency between the source release and the
> > Git tag dubbo-2.7.0:
> >
> > Only in apache-dubbo-incubating-2.7.0-source-release: all
> > Only in apache-dubbo-incubating-2.7.0-source-release: bom
> > Only in apache-dubbo-incubating-2.7.0-source-release: dependencies-bom
> > Only in apache-dubbo-incubating-2.7.0-source-release: distribution
> > Only in apache-dubbo-incubating-2.7.0-source-release: dubbo-bootstrap
> > Only in
> apache-dubbo-incubating-2.7.0-source-release/dubbo-config/dubbo-config-spring/src/test/resources:
> > work
> > Only in apache-dubbo-incubating-2.7.0-source-release/dubbo-demo:
> > dubbo-demo-consumer
> > Only in apache-dubbo-incubating-2.7.0-source-release/dubbo-demo:
> > dubbo-demo-provider
> > Only in apache-dubbo-incubating-2.7.0-source-release/dubbo-metrics:
> > dubbo-metrics-default
> > Only in apache-dubbo-incubating-2.7.0-source-release/dubbo-test:
> > dubbo-test-benchmark
> > Only in apache-dubbo-incubating-2.7.0-source-release/dubbo-test:
> > dubbo-test-examples
> >
> > It is possibly due to my local environment, I am going to do it again
> > with clean checkout of Dubbo 2.7.0-release branch.
> >
> > On Fri, Jan 18, 2019 at 10:25 AM Huxing Zhang  wrote:
> >>
> >> Hi,
> >>
> >> I found that there is a file test.patch in source release, which was
> >> the patch I used to restore the commit I reverted yesterday.
> >> This is not what we want, I am going to remove this file and re-tagging
> 2.7.0.
> >>
> >>
> >> On Fri, Jan 18, 2019 at 9:47 AM Huxing Zhang  wrote:
> >>>
> >>> Hi,
> >>>
> >>> On Fri, Jan 18, 2019 at 12:08 AM jun liu  wrote:
> 
> > Jun, could you please summarize an English version of the release
> note.
> > I will send the vote email once it is done.
> 
>  It’s now available here:
> https://github.com/apache/incubator-dubbo/blob/2.7.0-release/CHANGES.md#270
> >>>
> >>> Thanks for that, it looks good to me.
> >>>
>  I think it’s time to prepare the upgrade guide and user docs now,
> which is also a key part for this release.
> >>>
> >>> Yes, we can do that while we are doing the release vote.
> >>>
> >>> I am starting the vote today.
> 
>  Jun
> 
> > On Jan 17, 2019, at 11:58 PM, Huxing Zhang 
> wrote:
> >
> > Hi,
> >
> > All the preparation seems going well.
> > I have successfully uploaded 2.7.0 to staging repo, and upload the
> > release candidate to svn.
> > I saw that the release note is still in Chinese.
> >
> > Jun, could you please summarize an English version of the release
> note.
> > I will send the vote email once it is done.
> >
> > On Thu, Jan 17, 2019 at 5:48 PM victory 
> wrote:
> >>
> >> I have check the file , it is the same as pull request #3263.
> >>
> >>
> >> Huxing Zhang  于2019年1月17日周四 下午5:34写道：
> >>
> >>> Hi Victory,
> >>>
> >>> I've mistakenly reverted your recent pull request[1].
> >>> Luckily I have restored it via the commit email message.
> >>> I've push it to 2.7.0-release branch already.
> >>> Would you please help to check it?
> >>>
> >>>
> >>> [1] https://github.com/apache/incubator-dubbo/pull/3263
> >>>
> >>> On Thu, Jan 17, 2019 at 5:08 PM victory 
> wrote:
> 
>  I have review the code and it work well in
> 
> >>>
> https://github.com/apache/incubator-dubbo-samples/tree/samples-for-2.7.0-SNAPSHOT/dubbo-samples-configcenter/dubbo-samples-configcenter-apollo
> 
>  I have merged this pull request into 2.7.0-release.
> 
>  Huxing Zhang  于2019年1月17日周四 下午2:59写道：
> 
> > Hi,
> >
> > This looks like a blocking issue, I've already tagged 2.7.0, I
> will
> > wait for it and re-do the tagging.
> >
> > On Thu, Jan 17, 2019 at 2:49 PM jun liu 
> wrote:
> >>
> >>> I am seeing that all the issue has been cleaned for the 2.7.0
> > milestone.
> >>> It looks like all the things have been settled, I am planning
> to
> >>> tag
> >>> the 2.7.0 release today.
> >>
> >> One more issue to be solved before vote.
> >> Thanks to the suggestions from the Apollo[1] community, I
> submitted a
> > PR[2] to polish the Apollo extension. Please help to review.
> >>
> >> 1. 

Re: [Notification of V2.7.0] Status, TODOs, Possible Release Schedules.

[Xin Wang]

good job

jun liu  于 2019年1月18日周五 上午12:08写道：

> > Jun, could you please summarize an English version of the release note.
> > I will send the vote email once it is done.
>
> It’s now available here:
> https://github.com/apache/incubator-dubbo/blob/2.7.0-release/CHANGES.md#270
> I think it’s time to prepare the upgrade guide and user docs now, which is
> also a key part for this release.
>
> Jun
>
> > On Jan 17, 2019, at 11:58 PM, Huxing Zhang  wrote:
> >
> > Hi,
> >
> > All the preparation seems going well.
> > I have successfully uploaded 2.7.0 to staging repo, and upload the
> > release candidate to svn.
> > I saw that the release note is still in Chinese.
> >
> > Jun, could you please summarize an English version of the release note.
> > I will send the vote email once it is done.
> >
> > On Thu, Jan 17, 2019 at 5:48 PM victory  wrote:
> >>
> >> I have check the file , it is the same as pull request #3263.
> >>
> >>
> >> Huxing Zhang  于2019年1月17日周四 下午5:34写道：
> >>
> >>> Hi Victory,
> >>>
> >>> I've mistakenly reverted your recent pull request[1].
> >>> Luckily I have restored it via the commit email message.
> >>> I've push it to 2.7.0-release branch already.
> >>> Would you please help to check it?
> >>>
> >>>
> >>> [1] https://github.com/apache/incubator-dubbo/pull/3263
> >>>
> >>> On Thu, Jan 17, 2019 at 5:08 PM victory  wrote:
> 
>  I have review the code and it work well in
> 
> >>>
> https://github.com/apache/incubator-dubbo-samples/tree/samples-for-2.7.0-SNAPSHOT/dubbo-samples-configcenter/dubbo-samples-configcenter-apollo
> 
>  I have merged this pull request into 2.7.0-release.
> 
>  Huxing Zhang  于2019年1月17日周四 下午2:59写道：
> 
> > Hi,
> >
> > This looks like a blocking issue, I've already tagged 2.7.0, I will
> > wait for it and re-do the tagging.
> >
> > On Thu, Jan 17, 2019 at 2:49 PM jun liu  wrote:
> >>
> >>> I am seeing that all the issue has been cleaned for the 2.7.0
> > milestone.
> >>> It looks like all the things have been settled, I am planning to
> >>> tag
> >>> the 2.7.0 release today.
> >>
> >> One more issue to be solved before vote.
> >> Thanks to the suggestions from the Apollo[1] community, I submitted
> a
> > PR[2] to polish the Apollo extension. Please help to review.
> >>
> >> 1. https://github.com/ctripcorp/apollo
> >> 2. https://github.com/apache/incubator-dubbo/pull/3263
> >>
> >> Jun
> >>
> >>> On Jan 17, 2019, at 10:41 AM, Huxing Zhang 
> >>> wrote:
> >>>
> >>> Hi All,
> >>>
> >>> I am seeing that all the issue has been cleaned for the 2.7.0
> > milestone.
> >>> It looks like all the things have been settled, I am planning to
> >>> tag
> >>> the 2.7.0 release today.
> >>>
> >>> dubbo-ops and dubbo-spring-boot-project should be released after
> >>> Dubbo
> >>> 2.7.0 release.
> >>>
> >>> On Wed, Jan 16, 2019 at 5:02 PM jun liu  >>>  > ken.lj...@gmail.com>> wrote:
> 
> > There is no need to shade gson into dubbo.jar, just need depency
> >>> gson
> > library.
> >
> > I have fixed it .
> > https://github.com/apache/incubator-dubbo/pull/3246 <
> > https://github.com/apache/incubator-dubbo/pull/3246> <
> > https://github.com/apache/incubator-dubbo/pull/3246 <
> > https://github.com/apache/incubator-dubbo/pull/3246>>
>  Agree.
> 
>  Well done,  merged.
> 
>  Jun
> 
> > On Jan 16, 2019, at 4:15 PM, victory 
> >>> wrote:
> >
> > There is no need to shade gson into dubbo.jar, just need depency
> >>> gson
> > library.
> >
> > I have fixed it .
> > https://github.com/apache/incubator-dubbo/pull/3246
> >
> > Ian Luo  于2019年1月16日周三 下午2:34写道：
> >
> >> We should not shade gson binaries into dubbo all in one jar
> >>> file,
> > even
> >> though there's no license issue. It is simply we should not do
> >>> this,
> >> instead, we should make sure dubbo all in one jar should have a
> > transitive
> >> dependency to gson library.
> >>
> >> I noticed it's caused
> > by'com.google.code.gson:gson' in
> >> dubbo-all/pom.xml. We should fix it.
> >>
> >> Thanks,
> >> -Ian.
> >>
> >>
> >> On Tue, Jan 15, 2019 at 5:16 PM jun liu 
> > wrote:
> >>
> >>> I noticed that a third-party source code ‘com.google <
> > http://com.google/
> >>> .gson.*’
> >>> has been compiled into the convenient maven binary jar of
> >>> 2.7.0 -
> >>> dubbo-2.7.0.jar :
> >>>
> >>> .
> >>> ├── META-INF
> >>> │   ├── DEPENDENCIES
> >>> │   ├── LICENSE
> >>> │   ├── MANIFEST.MF
> >>> │   ├── NOTICE
> >>> │   ├── assembly
> >>> │   │   └── bin
> 

Re: Dubbo snapshot version

[Xin Wang]

https://repository.apache.org/content/repositories/snapshots/org/apache/dubbo/


Yunkun Huang  于2019年1月12日周六 下午4:26写道：

> hey team,
>
> I try to find snapshot version for dubbo 2.7 but it seems not exsited in
> http://repository.apache.org/snapshots/.
>
> I can't find any related configuration in travis ci configuration, so
> would like to confirm if there is any snapshot version in any repository?
>
>
>

Re: [DISCUSS] Dubbo: Upgrade junt to junit5

[Xin Wang]

Now the pr is merged to master branch by Ian

Next  we should use junit 5 in Dubbo , the official guide is :《JUnit 5 User
Guide》

 https://junit.org/junit5/docs/current/user-guide/

Thank you !


Xin Wang  于2019年1月9日周三 上午11:02写道：

> The release time of JUnit junpiter 5.4.0 is uncertain, so I used 5.3.2.
> Because of some test cases, I copied the source code of JUnit junpiter
> 5.4.0-M1
> Do I need to modify the LICENSE file?
>
> Ian Luo  于2019年1月9日周三 上午10:53写道：
>
>> Thanks for taking care of this, Yunkun.
>>
>> -Ian.
>>
>> On Wed, Jan 9, 2019 at 10:16 AM YunKun Huang  wrote:
>>
>> > The changes looks good to me.
>> > But somehow the test coverage drop to zero, it could be some
>> compatibility
>> > issue with jacoco or codecov.
>> > I will try to investigate this later today
>> >
>> >
>> > On 2019/01/07 14:41:48, Ian Luo  wrote:
>> > > Understood. Junit 5 should be better than 4.
>> > >
>> > > Thanks,
>> > > -Ian.
>> > >
>> > > On Mon, Jan 7, 2019 at 1:38 PM Xin Wang 
>> > wrote:
>> > >
>> > > > >  I noticed that you switch all junit API to jupiter engine which
>> > > > looks pretty new to the folks who has not touched junit5. I am
>> > wondering if
>> > > > the old API works or not in junit5.
>> > > >
>> > > > Yes, I switch all junit API to jupiter engine , for example, the
>> base
>> > Api:
>> > > >  *org.junt.Test*  is changed to org.junit.jupiter.api.Test*, *
>> > > > *org.junt.Assert*   is changed to  *
>> org.junit.jupiter.api.Assertions .
>> > > > *It's
>> > > > because , compared with junit4, junit5 has greatly refactoring the
>> API
>> > > > path, and the basic API path is migrated from org.junt to
>> > > > org.junit.jupiter.api.
>> > > > The adaptation strategy of junit5 to junit4 is to put the jars of
>> > junit4
>> > > > and junit5 in the project at the same time. In this way, there will
>> be
>> > > > JUnit4 and junit5 test cases in the project at the same time. I
>> think
>> > this
>> > > > will lead to confusion, not clean code. So I switch the api to
>> junit5
>> > > > directly.
>> > > >
>> > > >
>> > > >
>> > > >
>> > > > Ian Luo  于2019年1月7日周一 上午11:27写道：
>> > > >
>> > > > > Xin,
>> > > > >
>> > > > > Your pull request looks pretty straightforward to me. I have only
>> one
>> > > > minor
>> > > > > question: I noticed that you switch all junit API to jupiter
>> engine
>> > which
>> > > > > looks pretty new to the folks who has not touched junit5. I am
>> > wondering
>> > > > if
>> > > > > the old API works or not in junit5.
>> > > > >
>> > > > > Thanks,
>> > > > > -Ian.
>> > > > >
>> > > > > On Sat, Jan 5, 2019 at 11:48 PM Xin Wang <
>> xin.victorw...@gmail.com>
>> > > > wrote:
>> > > > >
>> > > > > > Hi all,
>> > > > > >I want to upgrade the junit dependency of Dubbo, contains :
>> > > > > >
>> > > > > > * Functions*
>> > > > > >1). Upgrade junit to junit 5
>> > > > > >2). Upgrade the test cases
>> > > > > >
>> > > > > >I create a issue[1] and a pr [2] , please discuss about this
>> ，
>> > > > > >
>> > > > > > *Why do this ?*
>> > > > > >1). Some new features：test extensions 、Future of JVM
>> > testing、easier
>> > > > > > parameterized tests
>> > > > > >2).Java 8 lambda support
>> > > > > >3).  Optimized api
>> > > > > >4). Basically compatible with junit4
>> > > > > >   Please read the referenced article ：《7 reasons why you should
>> > start
>> > > > > using
>> > > > > > JUnit 5 today》[3]
>> > > > > >
>> > > > > > *How to write junit5 test case ?*
>> > > > > >Please see 《JUnit 5 User Guide》[4]
>> > > > > >
>> > > > > > What do you think about this ?
>> > > > > >
>> > > > > > [1] https://github.com/apache/incubator-dubbo/issues/3148
>> > > > > > [2] https://github.com/apache/incubator-dubbo/pull/3149
>> > > > > > [3]
>> > > > > >
>> > > > > >
>> > > > >
>> > > >
>> >
>> http://dolszewski.com/testing/7-reasons-why-you-should-start-using-junit-5-today/
>> > > > > > [4] https://junit.org/junit5/docs/current/user-guide/
>> > > > > >
>> > > > >
>> > > >
>> > >
>> >
>>
>

Re: Junit5 source file, do I need to mark it in the LICENSE file?

[Xin Wang]

Now the junit5 source code is removed， thank you all.

Ian Luo  于2019年1月10日周四 下午5:19写道：

> I think it is fine if we don't include the source code from softwares
> fallen into "Category B”. In this particular case, let's simply use junit
> 5.4.0.M1 directly to avoid it.
>
> Regards,
> -Ian.
>
>
> On Thu, Jan 10, 2019 at 4:44 PM Xin Wang  wrote:
>
> > >  Sorry I mean “convenience binary” i.e. a binary made fro a source
> > package for the convenience of users who don’t want to compile the source
> > code.
> >
> > Does it mean that if I use the jar generated from the source code of
> EPL2，
> > also need to be placed in the LICENSE file?
> >
> > Huxing Zhang  于2019年1月10日周四 下午4:34写道：
> >
> > > Hi,
> > >
> > > Can you elaborate why you need the codes in 5.4.0?
> > > Maybe we can find a way to work it around.
> > > If not, I think option 1 and option 2 looks both ok to me.
> > > If I have to choose, I choose option 1 because this is a test
> > > dependency, it should not have too much impact to the code quality.
> > > If choose option 2 and have to wait 2 month, maybe there will be lots
> > > of refactoring work like resolving conflicts.
> > >
> > >
> > > On Thu, Jan 10, 2019 at 4:09 PM Xin Wang 
> > wrote:
> > > >
> > > > If so , I think there are two methds:
> > > > 1. Use  jupiter  version5.4.0-M1 [1]: but it is a milestone version,
> > not
> > > a
> > > > release version
> > > > 2. Use  jupiter  version5.4.0: the release date is uncertain （maybe
> > need
> > > > two monthes）
> > > >
> > > > [1] https://github.com/junit-team/junit5/releases/tag/r5.4.0-M1
> > > >
> > > > Justin Mclean  于2019年1月10日周四 下午3:50写道：
> > > >
> > > > > Hi,
> > > > >
> > > > > > I have a question :I ues junit-jupiter5.3.2, but for some test
> > > cases, I
> > > > > > copied some source code from junit 5.4.0.M1 , the files are as
> > > follow :
> > > > > >org.junit.jupiter.api.support.io.TempDirectory.java
> > > > > >
> > > > > >
> > > > >
> > >
> >
> org.junit.jupiter.api.MethodDescriptororg.junit.jupiter.api.TestMethodOrderorg.junit.jupiter.api.Orderorg.junit.jupiter.api.MethodOrdererorg.junit.jupiter.api.MethodOrdererContextorg.junit.jupiter.api.MethodDescriptor
> > > > > >
> > > > > > the license is Eclipse Public License - v 2.0
> > > > > > Do I need to mark it in the LICENSE file?
> > > > >
> > > > > Sorry EPL is considered "Category B”  [1] and isn’t fully
> compatible
> > > with
> > > > > ALv2 can’t be included in a source release. Is there another way of
> > > doing
> > > > > this?
> > > > >
> > > > > if it was the connivance binary then yes you would need to put it
> in
> > > the
> > > > > LICENSE.
> > > > >
> > > > > Thanks,
> > > > > Justin
> > > > >
> > > > > 1. https://www.apache.org/legal/resolved.html#category-b
> > >
> > >
> > >
> > > --
> > > Best Regards！
> > > Huxing
> > >
> >
>

Re: Junit5 source file, do I need to mark it in the LICENSE file?

[Xin Wang]

>  Can you elaborate why you need the codes in 5.4.0?

Some old test cases need two features: temporary folder  read and
write，ordered test case
 the Jupiter 5.3.2 does not contain these features, but 5.4.0.M1 does.


> If I have to choose, I choose option 1

Yes, option 1 won't cause PR to be delayed too long.


Xin Wang  于2019年1月10日周四 下午4:43写道：

> >  Sorry I mean “convenience binary” i.e. a binary made fro a source
> package for the convenience of users who don’t want to compile the source
> code.
>
> Does it mean that if I use the jar generated from the source code of EPL2，
> also need to be placed in the LICENSE file?
>
> Huxing Zhang  于2019年1月10日周四 下午4:34写道：
>
>> Hi,
>>
>> Can you elaborate why you need the codes in 5.4.0?
>> Maybe we can find a way to work it around.
>> If not, I think option 1 and option 2 looks both ok to me.
>> If I have to choose, I choose option 1 because this is a test
>> dependency, it should not have too much impact to the code quality.
>> If choose option 2 and have to wait 2 month, maybe there will be lots
>> of refactoring work like resolving conflicts.
>>
>>
>> On Thu, Jan 10, 2019 at 4:09 PM Xin Wang 
>> wrote:
>> >
>> > If so , I think there are two methds:
>> > 1. Use  jupiter  version5.4.0-M1 [1]: but it is a milestone version,
>> not a
>> > release version
>> > 2. Use  jupiter  version5.4.0: the release date is uncertain （maybe need
>> > two monthes）
>> >
>> > [1] https://github.com/junit-team/junit5/releases/tag/r5.4.0-M1
>> >
>> > Justin Mclean  于2019年1月10日周四 下午3:50写道：
>> >
>> > > Hi,
>> > >
>> > > > I have a question :I ues junit-jupiter5.3.2, but for some test
>> cases, I
>> > > > copied some source code from junit 5.4.0.M1 , the files are as
>> follow :
>> > > >org.junit.jupiter.api.support.io.TempDirectory.java
>> > > >
>> > > >
>> > >
>> org.junit.jupiter.api.MethodDescriptororg.junit.jupiter.api.TestMethodOrderorg.junit.jupiter.api.Orderorg.junit.jupiter.api.MethodOrdererorg.junit.jupiter.api.MethodOrdererContextorg.junit.jupiter.api.MethodDescriptor
>> > > >
>> > > > the license is Eclipse Public License - v 2.0
>> > > > Do I need to mark it in the LICENSE file?
>> > >
>> > > Sorry EPL is considered "Category B”  [1] and isn’t fully compatible
>> with
>> > > ALv2 can’t be included in a source release. Is there another way of
>> doing
>> > > this?
>> > >
>> > > if it was the connivance binary then yes you would need to put it in
>> the
>> > > LICENSE.
>> > >
>> > > Thanks,
>> > > Justin
>> > >
>> > > 1. https://www.apache.org/legal/resolved.html#category-b
>>
>>
>>
>> --
>> Best Regards！
>> Huxing
>>
>

Re: Junit5 source file, do I need to mark it in the LICENSE file?

[Xin Wang]

>  Sorry I mean “convenience binary” i.e. a binary made fro a source
package for the convenience of users who don’t want to compile the source
code.

Does it mean that if I use the jar generated from the source code of EPL2，
also need to be placed in the LICENSE file?

Huxing Zhang  于2019年1月10日周四 下午4:34写道：

> Hi,
>
> Can you elaborate why you need the codes in 5.4.0?
> Maybe we can find a way to work it around.
> If not, I think option 1 and option 2 looks both ok to me.
> If I have to choose, I choose option 1 because this is a test
> dependency, it should not have too much impact to the code quality.
> If choose option 2 and have to wait 2 month, maybe there will be lots
> of refactoring work like resolving conflicts.
>
>
> On Thu, Jan 10, 2019 at 4:09 PM Xin Wang  wrote:
> >
> > If so , I think there are two methds:
> > 1. Use  jupiter  version5.4.0-M1 [1]: but it is a milestone version, not
> a
> > release version
> > 2. Use  jupiter  version5.4.0: the release date is uncertain （maybe need
> > two monthes）
> >
> > [1] https://github.com/junit-team/junit5/releases/tag/r5.4.0-M1
> >
> > Justin Mclean  于2019年1月10日周四 下午3:50写道：
> >
> > > Hi,
> > >
> > > > I have a question :I ues junit-jupiter5.3.2, but for some test
> cases, I
> > > > copied some source code from junit 5.4.0.M1 , the files are as
> follow :
> > > >org.junit.jupiter.api.support.io.TempDirectory.java
> > > >
> > > >
> > >
> org.junit.jupiter.api.MethodDescriptororg.junit.jupiter.api.TestMethodOrderorg.junit.jupiter.api.Orderorg.junit.jupiter.api.MethodOrdererorg.junit.jupiter.api.MethodOrdererContextorg.junit.jupiter.api.MethodDescriptor
> > > >
> > > > the license is Eclipse Public License - v 2.0
> > > > Do I need to mark it in the LICENSE file?
> > >
> > > Sorry EPL is considered "Category B”  [1] and isn’t fully compatible
> with
> > > ALv2 can’t be included in a source release. Is there another way of
> doing
> > > this?
> > >
> > > if it was the connivance binary then yes you would need to put it in
> the
> > > LICENSE.
> > >
> > > Thanks,
> > > Justin
> > >
> > > 1. https://www.apache.org/legal/resolved.html#category-b
>
>
>
> --
> Best Regards！
> Huxing
>

Re: Junit5 source file, do I need to mark it in the LICENSE file?

[Xin Wang]

If so , I think there are two methds:
1. Use  jupiter  version5.4.0-M1 [1]: but it is a milestone version, not a
release version
2. Use  jupiter  version5.4.0: the release date is uncertain （maybe need
two monthes）

[1] https://github.com/junit-team/junit5/releases/tag/r5.4.0-M1

Justin Mclean  于2019年1月10日周四 下午3:50写道：

> Hi,
>
> > I have a question :I ues junit-jupiter5.3.2, but for some test cases, I
> > copied some source code from junit 5.4.0.M1 , the files are as follow :
> >org.junit.jupiter.api.support.io.TempDirectory.java
> >
> >
> org.junit.jupiter.api.MethodDescriptororg.junit.jupiter.api.TestMethodOrderorg.junit.jupiter.api.Orderorg.junit.jupiter.api.MethodOrdererorg.junit.jupiter.api.MethodOrdererContextorg.junit.jupiter.api.MethodDescriptor
> >
> > the license is Eclipse Public License - v 2.0
> > Do I need to mark it in the LICENSE file?
>
> Sorry EPL is considered "Category B”  [1] and isn’t fully compatible with
> ALv2 can’t be included in a source release. Is there another way of doing
> this?
>
> if it was the connivance binary then yes you would need to put it in the
> LICENSE.
>
> Thanks,
> Justin
>
> 1. https://www.apache.org/legal/resolved.html#category-b

Junit5 source file, do I need to mark it in the LICENSE file?

[Xin Wang]

hi all
   The feature: Dubbo: Upgrade junt to junit5 [1] [2]
is ready now.

I have a question :I ues junit-jupiter5.3.2, but for some test cases, I
copied some source code from junit 5.4.0.M1 , the files are as follow :
org.junit.jupiter.api.support.io.TempDirectory.java

org.junit.jupiter.api.MethodDescriptororg.junit.jupiter.api.TestMethodOrderorg.junit.jupiter.api.Orderorg.junit.jupiter.api.MethodOrdererorg.junit.jupiter.api.MethodOrdererContextorg.junit.jupiter.api.MethodDescriptor

the license is Eclipse Public License - v 2.0
Do I need to mark it in the LICENSE file?


[1] https://github.com/apache/incubator-dubbo/pull/3149
[2]
https://lists.apache.org/thread.html/56b9c627b4736b605ea61bdda41b1dba072e21dc85f8181f9374e1ca@%3Cdev.dubbo.apache.org%3E

Re: [DISCUSS] Dubbo: Upgrade junt to junit5

[Xin Wang]

The release time of JUnit junpiter 5.4.0 is uncertain, so I used 5.3.2.
Because of some test cases, I copied the source code of JUnit junpiter
5.4.0-M1
Do I need to modify the LICENSE file?

Ian Luo  于2019年1月9日周三 上午10:53写道：

> Thanks for taking care of this, Yunkun.
>
> -Ian.
>
> On Wed, Jan 9, 2019 at 10:16 AM YunKun Huang  wrote:
>
> > The changes looks good to me.
> > But somehow the test coverage drop to zero, it could be some
> compatibility
> > issue with jacoco or codecov.
> > I will try to investigate this later today
> >
> >
> > On 2019/01/07 14:41:48, Ian Luo  wrote:
> > > Understood. Junit 5 should be better than 4.
> > >
> > > Thanks,
> > > -Ian.
> > >
> > > On Mon, Jan 7, 2019 at 1:38 PM Xin Wang 
> > wrote:
> > >
> > > > >  I noticed that you switch all junit API to jupiter engine which
> > > > looks pretty new to the folks who has not touched junit5. I am
> > wondering if
> > > > the old API works or not in junit5.
> > > >
> > > > Yes, I switch all junit API to jupiter engine , for example, the base
> > Api:
> > > >  *org.junt.Test*  is changed to org.junit.jupiter.api.Test*, *
> > > > *org.junt.Assert*   is changed to  *
> org.junit.jupiter.api.Assertions .
> > > > *It's
> > > > because , compared with junit4, junit5 has greatly refactoring the
> API
> > > > path, and the basic API path is migrated from org.junt to
> > > > org.junit.jupiter.api.
> > > > The adaptation strategy of junit5 to junit4 is to put the jars of
> > junit4
> > > > and junit5 in the project at the same time. In this way, there will
> be
> > > > JUnit4 and junit5 test cases in the project at the same time. I think
> > this
> > > > will lead to confusion, not clean code. So I switch the api to junit5
> > > > directly.
> > > >
> > > >
> > > >
> > > >
> > > > Ian Luo  于2019年1月7日周一 上午11:27写道：
> > > >
> > > > > Xin,
> > > > >
> > > > > Your pull request looks pretty straightforward to me. I have only
> one
> > > > minor
> > > > > question: I noticed that you switch all junit API to jupiter engine
> > which
> > > > > looks pretty new to the folks who has not touched junit5. I am
> > wondering
> > > > if
> > > > > the old API works or not in junit5.
> > > > >
> > > > > Thanks,
> > > > > -Ian.
> > > > >
> > > > > On Sat, Jan 5, 2019 at 11:48 PM Xin Wang  >
> > > > wrote:
> > > > >
> > > > > > Hi all,
> > > > > >I want to upgrade the junit dependency of Dubbo, contains :
> > > > > >
> > > > > > * Functions*
> > > > > >1). Upgrade junit to junit 5
> > > > > >2). Upgrade the test cases
> > > > > >
> > > > > >I create a issue[1] and a pr [2] , please discuss about this ，
> > > > > >
> > > > > > *Why do this ?*
> > > > > >1). Some new features：test extensions 、Future of JVM
> > testing、easier
> > > > > > parameterized tests
> > > > > >2).Java 8 lambda support
> > > > > >3).  Optimized api
> > > > > >4). Basically compatible with junit4
> > > > > >   Please read the referenced article ：《7 reasons why you should
> > start
> > > > > using
> > > > > > JUnit 5 today》[3]
> > > > > >
> > > > > > *How to write junit5 test case ?*
> > > > > >Please see 《JUnit 5 User Guide》[4]
> > > > > >
> > > > > > What do you think about this ?
> > > > > >
> > > > > > [1] https://github.com/apache/incubator-dubbo/issues/3148
> > > > > > [2] https://github.com/apache/incubator-dubbo/pull/3149
> > > > > > [3]
> > > > > >
> > > > > >
> > > > >
> > > >
> >
> http://dolszewski.com/testing/7-reasons-why-you-should-start-using-junit-5-today/
> > > > > > [4] https://junit.org/junit5/docs/current/user-guide/
> > > > > >
> > > > >
> > > >
> > >
> >
>

Re: [DISCUSS] Dubbo: Upgrade junt to junit5

[Xin Wang]

>  I noticed that you switch all junit API to jupiter engine which
looks pretty new to the folks who has not touched junit5. I am wondering if
the old API works or not in junit5.

Yes, I switch all junit API to jupiter engine , for example, the base Api:
 *org.junt.Test*  is changed to org.junit.jupiter.api.Test*, *
*org.junt.Assert*   is changed to  * org.junit.jupiter.api.Assertions . *It's
because , compared with junit4, junit5 has greatly refactoring the API
path, and the basic API path is migrated from org.junt to
org.junit.jupiter.api.
The adaptation strategy of junit5 to junit4 is to put the jars of junit4
and junit5 in the project at the same time. In this way, there will be
JUnit4 and junit5 test cases in the project at the same time. I think this
will lead to confusion, not clean code. So I switch the api to junit5
directly.




Ian Luo  于2019年1月7日周一 上午11:27写道：

> Xin,
>
> Your pull request looks pretty straightforward to me. I have only one minor
> question: I noticed that you switch all junit API to jupiter engine which
> looks pretty new to the folks who has not touched junit5. I am wondering if
> the old API works or not in junit5.
>
> Thanks,
> -Ian.
>
> On Sat, Jan 5, 2019 at 11:48 PM Xin Wang  wrote:
>
> > Hi all,
> >I want to upgrade the junit dependency of Dubbo, contains :
> >
> > * Functions*
> >1). Upgrade junit to junit 5
> >2). Upgrade the test cases
> >
> >I create a issue[1] and a pr [2] , please discuss about this ，
> >
> > *Why do this ?*
> >1). Some new features：test extensions 、Future of JVM testing、easier
> > parameterized tests
> >2).Java 8 lambda support
> >3).  Optimized api
> >4). Basically compatible with junit4
> >   Please read the referenced article ：《7 reasons why you should start
> using
> > JUnit 5 today》[3]
> >
> > *How to write junit5 test case ?*
> >Please see 《JUnit 5 User Guide》[4]
> >
> > What do you think about this ?
> >
> > [1] https://github.com/apache/incubator-dubbo/issues/3148
> > [2] https://github.com/apache/incubator-dubbo/pull/3149
> > [3]
> >
> >
> http://dolszewski.com/testing/7-reasons-why-you-should-start-using-junit-5-today/
> > [4] https://junit.org/junit5/docs/current/user-guide/
> >
>

Re: [DISCUSS] Dubbo: Upgrade junt to junit5

[Xin Wang]

Yes，it's so  large, because I upgrade all the cases  . I will write the
change list in more detail on the pr：
https://github.com/apache/incubator-dubbo/pull/3149

Huxing Zhang  于2019年1月7日周一 上午11:21写道：

> Hi,
>
> +1 to have it!
>
> I see the pull request is quite a large one. I would be better if you
> can provide some suggestions to the reviewers.
> For example, where should be pay more attention to.
>
> On Sat, Jan 5, 2019 at 11:48 PM Xin Wang  wrote:
> >
> > Hi all,
> >I want to upgrade the junit dependency of Dubbo, contains :
> >
> > * Functions*
> >1). Upgrade junit to junit 5
> >2). Upgrade the test cases
> >
> >I create a issue[1] and a pr [2] , please discuss about this ，
> >
> > *Why do this ?*
> >1). Some new features：test extensions 、Future of JVM testing、easier
> > parameterized tests
> >2).Java 8 lambda support
> >3).  Optimized api
> >4). Basically compatible with junit4
> >   Please read the referenced article ：《7 reasons why you should start
> using
> > JUnit 5 today》[3]
> >
> > *How to write junit5 test case ?*
> >Please see 《JUnit 5 User Guide》[4]
> >
> > What do you think about this ?
> >
> > [1] https://github.com/apache/incubator-dubbo/issues/3148
> > [2] https://github.com/apache/incubator-dubbo/pull/3149
> > [3]
> >
> http://dolszewski.com/testing/7-reasons-why-you-should-start-using-junit-5-today/
> > [4] https://junit.org/junit5/docs/current/user-guide/
>
>
>
> --
> Best Regards！
> Huxing
>

[DISCUSS] Dubbo: Upgrade junt to junit5

[Xin Wang]

Hi all,
   I want to upgrade the junit dependency of Dubbo, contains :

* Functions*
   1). Upgrade junit to junit 5
   2). Upgrade the test cases

   I create a issue[1] and a pr [2] , please discuss about this ，

*Why do this ?*
   1). Some new features：test extensions 、Future of JVM testing、easier
parameterized tests
   2).Java 8 lambda support
   3).  Optimized api
   4). Basically compatible with junit4
  Please read the referenced article ：《7 reasons why you should start using
JUnit 5 today》[3]

*How to write junit5 test case ?*
   Please see 《JUnit 5 User Guide》[4]

What do you think about this ?

[1] https://github.com/apache/incubator-dubbo/issues/3148
[2] https://github.com/apache/incubator-dubbo/pull/3149
[3]
http://dolszewski.com/testing/7-reasons-why-you-should-start-using-junit-5-today/
[4] https://junit.org/junit5/docs/current/user-guide/

Re: Happy new year 2019

[Xin Wang]

> How about using get the current year by javascript?
So that, the year in the copyright do't need to update at next year.
Not a very good method . The javascript function depend on the user's pc .
If he time of pc is incorrect, the website will appear  incorrect.

老五 <176402...@qq.com> 于2019年1月2日周三 下午1:18写道：

> Happy New Year!
>
>
> How about using get the current year by javascript?
> So that, the year in the copyright do't need to update at next year.
>
>
> Here is my PR:
> https://github.com/apache/incubator-dubbo-website/pull/226
>
>
> -- 原始邮件 --
> 发件人: "Huxing Zhang";
> 发送时间: 2019年1月2日(星期三) 中午11:11
> 收件人: "dev";
>
> 主题: Happy new year 2019
>
>
>
> Hi community.
>
> Happy New Year!
>
> It is already 2019, we need to update the copyright NOTICE file for
> the new year.
>
> I filed an issue for incubator-dubbo and incubator-dubbo-website:
>
> * https://github.com/apache/incubator-dubbo/issues/3111
> * https://github.com/apache/incubator-dubbo-website/issues/224
>
> Please add more if there are something missing.
> Please send pull request if you are interested in contribution. :)
>
>
> --
> Best Regards！
> Huxing

Re: [Notification of Dubbo Admin] about to release the first version

[Xin Wang]

Hi Minxuan Zhuang
Will this version of UI support Chinese? I think support for Chinese is
very important.
https://github.com/apache/incubator-dubbo-ops/issues/133

Minxuan Zhuang  于2018年12月28日周五 下午4:23写道：

> Hi all:
> I'm about to release the first version of Dubbo Admin, after refactoring
> and functional enhancement, the Dubbo Admin including the features below:
> 1. Repackage to 'org.apache.dubbo'
> 2. Spring boot as backend framework
> 3. Vue and Vuetify as frontend framework
> 4. Basic service search Service detail
> 5. new features in Dubbo2.7(tag route, application scope governance, etc)
> 6. compatible with dubbo 2.6 service governance
>
> I've deployed a live demo here: http://47.91.207.147/#/service,  if you
> found any issue or you have new feature requests, please fire an issue or
> submit a pull request: https://github.com/apache/incubator-dubbo-ops.
>

Re: travis ci are failing

[Xin Wang]

> Is this particular issue solved, without tuning JVM option?

Yes now ci  of  master branch passed

Ian Luo  于2018年12月28日周五 上午11:15写道：

> Is this particular issue solved, without tuning JVM option?
>
> Thanks,
> -Ian.
>
> On Thu, Dec 27, 2018 at 3:59 AM 徐靖峰  wrote:
>
> > I failed twice caused by OutOfMemery，are you the same as me？
> >
> >
> >
> >
> >
> > -- Original --
> > From: Imteyaz Khan 
> > Date: Thu,Dec 27,2018 3:24 AM
> > To: dev 
> > Subject: Re: travis ci are failing
> >
> >
> >
> > Hi all,
> >Travis CI are failing currently due to log size. Is it the same issue
> > 3052 ?
>

Re: [DISCUSSION] Call for ideas and suggestions on v2.7.0 designs and implementations.

[Xin Wang]

hi, Jun

Now the travis ci of master branch faile， I create an issue
https://github.com/apache/incubator-dubbo/issues/3052
Please take a look at it

Xin Wang  于2018年12月24日周一 下午4:38写道：

> >I have just merged dev-metadata branch into master, from now on, the
> master branch will work as the develop and release codebase of v2.7.0.
> Branch dev-metadata does not need to be kept anymore, I will delete
> dev-metadata later today if there’re no more PRs come to it.
>
> Great work, looking forward to the new features!
>
> jun liu  于2018年12月24日周一 下午4:33写道：
>
>> Hi, All
>>
>> I have just merged dev-metadata branch into master, from now on, the
>> master branch will work as the develop and release codebase of v2.7.0.
>> Branch dev-metadata does not need to be kept anymore, I will delete
>> dev-metadata later today if there’re no more PRs come to it.
>>
>> Jun
>>
>> > On Dec 21, 2018, at 11:37 AM, jun liu  wrote:
>> >
>> > Two more things to mention:
>> >
>> > 1. I am thinking of merge this dev-metadata branch back to the master.
>> Both these two branches have the same version 2.7.0-SNAPSHOT and they
>> together consist of v2.7’s release candidates. While they are evolving at
>> the same time concurrently, conflicts keep happening. I have been kept
>> merging the master branch to dev-metadata to try to avoid conflicts to the
>> most extend during the development of dev-metadata. Now, since the changes
>> in dev-metadata are stable enough, at least it won’t be a block for the
>> development in master (which is also the biggest concern why we created
>> this new branch), I think it’s time for us to merge the changes back and
>> work on the unified master branch.
>> >
>> > 2. Is there any plan for the release of OPS? Most of the new features
>> introduced in v2.7 are service governance related abilities and most users
>> have get used to using Dubbo OPS to do interoperability with their Dubbo
>> services. Thus I think it would be great if an OPS version supporting these
>> features can be released at the same time as v2.7 or slightly after it .
>> > @Minxuan @Majinkai, I know you guys are working on OPS project, any
>> news to update?
>> >
>> > Jun
>> >
>> >> On Dec 21, 2018, at 10:35 AM, jun liu > ken.lj...@gmail.com>> wrote:
>> >>
>> >>> 1. Prioritization of centralized configuration
>> >>
>> >> Now, the centralized configuration or externalized configuration is
>> implemented to has the highest priority by default. For flexible concerns,
>> a switch is designed and opened to users so that they can override the
>> default value, for example, you can use the following JVM property to give
>> centralized configuration a lower priority than the local one:
>> dubbo.configCenter.highestPriority=false.
>> >>
>> >>> 2. The logic of the route is more complicated, and the compatibility
>> with
>> >>> the original low version is guaranteed.
>> >>
>> >> When saying of complexity, I guess you mainly refer to the routing
>> module, because this module is one of the most evident parts that has
>> changed in this version and is also newly introduced. Its main purpose is
>> to improve the performance of the runtime. After all, there will be some
>> performance loss when routing is executed for address filtering every time
>> an RPC is executed.
>> >> However, I agree we should be really careful about this cache part
>> since it works as an crucial path on the RPC wire. Some possible drawbacks
>> I can come up with it now are: excessive resource usage, priority guarantee
>> of routers in chain, etc. I think we can discuss more about the technical
>> details of this part, give it more test and then decide whether to release
>> it this time or wait until it’s mature enough.
>> >>
>> >>> 3.Tag routing has been modified, how is the compatibility with the
>> original?
>> >>
>> >> It has full backward compatibility with the original implementation
>> with only the supporting of of DynamicConfiguration added.
>> >>
>> >>> 4. How does the Environment clear responsibility? It is best to have
>> an
>> >>> independent description.
>> >>
>> >> Sorry, I don’t understand this one. Basically, you can think
>> Environment as the counterpart of that in Spring. I agree we should add a
>> document describing the design purpose and how to use it.
>> >>
>> >> Jun

Re: [DISCUSSION] Call for ideas and suggestions on v2.7.0 designs and implementations.

[Xin Wang]

>I have just merged dev-metadata branch into master, from now on, the
master branch will work as the develop and release codebase of v2.7.0.
Branch dev-metadata does not need to be kept anymore, I will delete
dev-metadata later today if there’re no more PRs come to it.

Great work, looking forward to the new features!

jun liu  于2018年12月24日周一 下午4:33写道：

> Hi, All
>
> I have just merged dev-metadata branch into master, from now on, the
> master branch will work as the develop and release codebase of v2.7.0.
> Branch dev-metadata does not need to be kept anymore, I will delete
> dev-metadata later today if there’re no more PRs come to it.
>
> Jun
>
> > On Dec 21, 2018, at 11:37 AM, jun liu  wrote:
> >
> > Two more things to mention:
> >
> > 1. I am thinking of merge this dev-metadata branch back to the master.
> Both these two branches have the same version 2.7.0-SNAPSHOT and they
> together consist of v2.7’s release candidates. While they are evolving at
> the same time concurrently, conflicts keep happening. I have been kept
> merging the master branch to dev-metadata to try to avoid conflicts to the
> most extend during the development of dev-metadata. Now, since the changes
> in dev-metadata are stable enough, at least it won’t be a block for the
> development in master (which is also the biggest concern why we created
> this new branch), I think it’s time for us to merge the changes back and
> work on the unified master branch.
> >
> > 2. Is there any plan for the release of OPS? Most of the new features
> introduced in v2.7 are service governance related abilities and most users
> have get used to using Dubbo OPS to do interoperability with their Dubbo
> services. Thus I think it would be great if an OPS version supporting these
> features can be released at the same time as v2.7 or slightly after it .
> > @Minxuan @Majinkai, I know you guys are working on OPS project, any news
> to update?
> >
> > Jun
> >
> >> On Dec 21, 2018, at 10:35 AM, jun liu  ken.lj...@gmail.com>> wrote:
> >>
> >>> 1. Prioritization of centralized configuration
> >>
> >> Now, the centralized configuration or externalized configuration is
> implemented to has the highest priority by default. For flexible concerns,
> a switch is designed and opened to users so that they can override the
> default value, for example, you can use the following JVM property to give
> centralized configuration a lower priority than the local one:
> dubbo.configCenter.highestPriority=false.
> >>
> >>> 2. The logic of the route is more complicated, and the compatibility
> with
> >>> the original low version is guaranteed.
> >>
> >> When saying of complexity, I guess you mainly refer to the routing
> module, because this module is one of the most evident parts that has
> changed in this version and is also newly introduced. Its main purpose is
> to improve the performance of the runtime. After all, there will be some
> performance loss when routing is executed for address filtering every time
> an RPC is executed.
> >> However, I agree we should be really careful about this cache part
> since it works as an crucial path on the RPC wire. Some possible drawbacks
> I can come up with it now are: excessive resource usage, priority guarantee
> of routers in chain, etc. I think we can discuss more about the technical
> details of this part, give it more test and then decide whether to release
> it this time or wait until it’s mature enough.
> >>
> >>> 3.Tag routing has been modified, how is the compatibility with the
> original?
> >>
> >> It has full backward compatibility with the original implementation
> with only the supporting of of DynamicConfiguration added.
> >>
> >>> 4. How does the Environment clear responsibility? It is best to have an
> >>> independent description.
> >>
> >> Sorry, I don’t understand this one. Basically, you can think
> Environment as the counterpart of that in Spring. I agree we should add a
> document describing the design purpose and how to use it.
> >>
> >> Jun
> >>
> >>> On Dec 14, 2018, at 12:26 PM, victory  shenglic...@gmail.com>> wrote:
> >>>
> >>> All of this features are the biggest concert in the community.
> >>> I have some questions：
> >>> 1.中心化配置的优先级
> >>> 2.路由的逻辑比较复杂，和原来低版本的兼容性怎么保证
> >>> 3.Tag路由改造了，和原来的兼容性怎么样？
> >>> 4.Environment这个东西是怎么明确职责的？最好能有个独立的说明。
> >>> --
> >>> 1. Prioritization of centralized configuration
> >>> 2. The logic of the route is more complicated, and the compatibility
> with
> >>> the original low version is guaranteed.
> >>> 3.Tag routing has been modified, how is the compatibility with the
> original?
> >>> 4. How does the Environment clear responsibility? It is best to have an
> >>> independent description.
> >>>
> >>>
> >>> jun liu mailto:ken.lj...@gmail.com>>
> 于2018年12月7日周五 下午8:11写道：
> >>>
>  Hi, All
> 
>  I’ve just posted some blogs[4] on Github issues relating to the design
>  principles and implementations of V2.7.0,  the content are based
> mainly on
>  my 

[ANN] New PPMC member: Yuhang Xiu

[Xin Wang]

Hi Community,

On behalf of the Dubbo PPMC, I am pleased to announce that Yuhang Xiu[1]
has been voted in as a new Dubbo PPMC member.

Please join me to say congratulations to him!

[1] https://github.com/carryxyh
--
Best Regards！

Xin Wang

Re: About the comments coverage of the code

[Xin Wang]

> So we need to let them know the role of a class or a method clearly when
we
only look at the doc.

I think a good way is to add the report generated by Javadoc to the website
dubbo. apache. org,
we can see the effect in real time。 "what you do is what you get",。

yuhang xiu  于2018年12月20日周四 上午11:05写道：

> Hi, huxing
>
> I agree with what you said, we don't need to strictly follow some kind of
> guidance.
>
> But I think we need a very detailed doc. And this doc is based on code, and
> may be more oriented to developers.
> So we need to let them know the role of a class or a method clearly when we
> only look at the doc.
> I'd like take a look at these doc prs and give some suggestions.
>
> Regarding the goal, I think we can increase the doc coverage rate to 45%
> first, and increase the coverage by about 20% first.
> :)
>
> Huxing Zhang  于2018年12月20日周四 上午10:20写道：
>
> > Hi，
> >
> > On Wed, Dec 19, 2018 at 8:48 PM yuhang xiu  wrote:
> > >
> > > Hi, all
> > >
> > > Recently I have seen a few pr about doc. Several of them have been
> > merged.
> > > I think we have two issues to discuss:
> > > 1. What kind of comments should we add?
> > > 2. We need to define a goal.
> > >
> > > Regarding question one, I personally think that we should:
> > > 1. Explain each param of the method
> > > 2. Explain the special usage of some classes. For example, when adding
> > the
> > > doc of SerializableClassRegistry, we need to doc that this class only
> > works
> > > when using fst and kryo serialization.
> > > 3. We need to use @link or @code for the association when the class
> > > (method) is associated with other classes (methods).
> >
> > Perhaps following some guide like [1] and [2]. But I don't think we
> > should follow it strictly.
> > If using IDE like Intellij IDEA, you can easily create customized
> > Javadoc template[3], with some boilerplate content like params, return
> > values.
> >
> > >
> > > Regarding question two, I don't have a idea. Perhaps doc coverage is
> 40%
> > is
> > > a good choice. What do you think?
> >
> > Do you mean the average doc coverage,  acoording to [4], I see there
> > is an average of 28.8% java coverage, setting the goal of average
> > coverage to 40%~50% looks good to me. We can do it step by step :)
> >
> > [1] https://www.baeldung.com/javadoc
> > [2]
> >
> https://www.oracle.com/technetwork/java/javase/documentation/index-137868.html#styleguide
> > [3]
> >
> https://stackoverflow.com/questions/17607925/how-configure-intellij-idea-javadoc-templates
> > [4] https://github.com/apache/incubator-dubbo/issues/2884
> >
> > >
> > >
> > > yuhang xiu  于2018年12月18日周二 下午4:21写道：
> > >
> > > > Hello, Dave.
> > > >
> > > > (2) Have any committers reached out to the users who had trouble with
> > code
> > > >> comments to confirm these efforts will meet their concerns?
> > > >>
> > > >
> > > > I used to talk to them, but I forgot to ask them about what kind of
> > docs
> > > > are better.
> > > >
> > > > But don't worry, I still have their contact details.
> > > > I will communicate with them and hope that they will bring their
> > opinions
> > > > here to better work for developers who add comments.
> > > >
> >
> >
> >
> > --
> > Best Regards！
> > Huxing
> >
>

Re: The issues of [Enhance the test coverage] project are here waiting for you

[Xin Wang]

Hi all
It's been a long time since I started this project. I am very
pleased to announce that the test coverage of Dubbo is now 64%.
We have achieved the goal of stage 1: unit test coverage > 60%.

A lot of people submitted prs, the contributors and the number of their prs
are as follows:

   YunKun Huang (@htynkn) 5
   Ian Luo (@beiwei30) 3
   Kimm King (@kimming)   2
   Xin Wang (@lovepoem) 1
   Zonghai Shang (@zonghaishang) 1
   Song Kun   (@satansk)1
   xialongfei (@stoneapple) 1
   钟剑 (@DeadLion)1
   Yang Tao(@whanice)   1
   Qin Yulin (@qinnnyul)  1
   Yong Zhu (diecui1202) 1

   Thank you very much for your contribution.
Now there are two issues( issues 1690 [1] and  issue 1692 [2] )  left , and
then the project will be completed. If anybody want to take part in, please
leave a message on these issues?
Thank you !

[1] https://github.com/apache/incubator-dubbo/issues/1690
[2] https://github.com/apache/incubator-dubbo/issues/1692

Xin Wang  于2018年4月27日周五 上午10:24写道：

> Hi,all
>   In order to enhance the test coverage, now the project is started:
> https://github.com/apache/incubator-dubbo/projects/1,
> you can also see the related issues in the other entrance page:
> https://github.com/apache/incubator-dubbo/issues/1702
>   The test coverage guide is here:
> https://github.com/apache/incubator-dubbo/wiki/Test-coverage-guide
>
>   Welcome everyone to join in，you can comment on the issue that you're
> interest with.
>
> Xin Wang
> lovep...@hotmail.com
>
>
>
>

Re: [incubator-dubbo-samples] branch master updated: Update README.md

[Xin Wang]

I modify the  dubbo-samples/README.md because the travis ci info changed

I think this mail should be sent to notifacati...@dubbo.apache.org
automatically,   but why sent to dev@dubbo.apache.org



Huxing Zhang  于2018年12月11日周二 下午3:32写道：

> Sorry, I mean to say  let's wait a few more times.
>
> On Tue, Dec 11, 2018 at 3:18 PM Huxing Zhang  wrote:
> >
> > Hi,
> >
> > I think this notification should be sent to comm...@dubbo.apache.org.
> > As Infra said, It may take some time to set up them, let's wait a few
> > more time.On Tue, Dec 11, 2018 at 12:58 PM  wrote:
> > >
> > > This is an automated email from the ASF dual-hosted git repository.
> > >
> > > wangxin pushed a commit to branch master
> > > in repository
> https://gitbox.apache.org/repos/asf/incubator-dubbo-samples.git
> > >
> > >
> > > The following commit(s) were added to refs/heads/master by this push:
> > >  new d4e1a15  Update README.md
> > > d4e1a15 is described below
> > >
> > > commit d4e1a15edcadf82c854ce6f9bac007928b2f8eb6
> > > Author: Xin Wang 
> > > AuthorDate: Tue Dec 11 12:58:51 2018 +0800
> > >
> > > Update README.md
> > >
> > > update repo address of travis
> > > ---
> > >  README.md | 4 ++--
> > >  1 file changed, 2 insertions(+), 2 deletions(-)
> > >
> > > diff --git a/README.md b/README.md
> > > index 536fcac..ef88a8c 100644
> > > --- a/README.md
> > > +++ b/README.md
> > > @@ -2,9 +2,9 @@
> > >
> > >  Samples for Apache Dubbo (incubating)
> > >
> > > -[![Build Status](
> https://travis-ci.org/dubbo/dubbo-samples.svg?branch=master)](https://travis-ci.org/dubbo/dubbo-samples
> )
> > > +[![Build Status](
> https://travis-ci.org/apache/incubator-dubbo-samples.svg?branch=master)](https://travis-ci.org/apache/incubator-dubbo-samples
> )
> > >  [![Gitter](
> https://badges.gitter.im/alibaba/dubbo.svg)](https://gitter.im/alibaba/dubbo?utm_source=badge_medium=badge_campaign=pr-badge
> )
> > > -![license](
> https://img.shields.io/github/license/dubbo/dubbo-samples.svg)
> > > +![license](
> https://img.shields.io/github/license/apache/incubator-dubbo-samples.svg)
> > >
> > >  This repository contains a number of projects to illustrate various
> usages of Dubbo from basic to advanced, check README in each individual sub
> projects.
> > >
> > >
> >
> > --
> > Best Regards！
> > Huxing
>
>
>
> --
> Best Regards！
> Huxing
>

Re: Re: [ANN] New PPMC member: Yong Zhu

[Xin Wang]

Congratulations

KimmKing  于2018年12月3日周一 下午9:38写道：

> Congratulations
>
> At 2018-12-03 13:58:18, "Jerrick Zhu"  wrote:
> >Thanks for all Dubbo PPMC members.
> >
> >Let's work hard together to make Dubbo better.
> >
> >On Mon, Dec 3, 2018 at 1:12 PM Huxing Zhang  wrote:
> >
> >> Hi Community,
> >>
> >> On behalf of the Dubbo PPMC, I am pleased to announce that Yong Zhu[1]
> >> has been voted in as a new Dubbo PPMC member.
> >>
> >> Please join me to say congratulations to him!
> >>
> >> [1] https://github.com/diecui1202
> >> --
> >> Best Regards！
> >> Huxing
> >>
>

Re: 回复：[ANN] Welcome new committer: Liandong Chen

[Xin Wang]

Congratulations!


YunKun Huang  于2018年11月21日周三 上午9:56写道：

> Congratulations!
>
> On 2018/11/20 14:33:25, "大步流星" <835576...@qq.com> wrote:
> > Haha, welcome, personal introduction can be more detailed, what is FEer
> short. . . .
> >
> >
> >
> >
> > -- 原始邮件 --
> > 发件人: "陈连东(轩坊)";
> > 发送时间: 2018年11月20日(星期二) 晚上7:58
> > 收件人: "dev";
> >
> > 主题: 回复：[ANN] Welcome new committer: Liandong Chen
> >
> >
> >
> > Hi, Community,
> > I'm honored to join Dubbo Community!
> > As a FEer, so glad to  devote my efforts to Dubbo website.
> >
> > Hope Dubbo become  better and better!
> >
> > Best Regards!
> > Liandong Chen
> >
> >
> > --
> > 发件人：Huxing Zhang 
> > 发送时间：2018年11月20日(星期二) 16:16
> > 收件人：dev 
> > 主 题：[ANN] Welcome new committer: Liandong Chen
> >
> > Hi, Community,
> >
> > On behalf of the Dubbo PPMC, I am pleased to announce that Liandong Chen,
> > aka purple-force[1], has been voted in as a new Dubbo committer.
> >
> > Please join me to say congratulations to him!
> >
> > Liandong, would you please briefly introduce yourself to the community?
> >
> > [1] https://github.com/purple-force
> > --
> > Best Regards！
> > Huxing
>

Re: Transfer wiki New Committer Guide to Official website

[Xin Wang]

>- Some markdown files under dubbo-website/docs/zh-cn/developers should
>be translated to Chinese

I  create a  issue
https://github.com/apache/incubator-dubbo-website/issues/181  ,  If you can
help, leave a message on issue.

Ian Luo  于2018年11月20日周二 下午4:43写道：

> I rebuilt the website, now these guides should be public available.
>
> Thanks,
> -Ian.
>
> On Tue, Nov 20, 2018 at 4:32 PM Huxing Zhang  wrote:
>
> > On Sun, Nov 18, 2018 at 7:59 PM Xin Wang 
> wrote:
> > >
> > > Now  I send a pr :
> > https://github.com/apache/incubator-dubbo-website/pull/178
> >
> > Great work!
> > >
> > > Change log :
> > >
> > >- Markdown files added to these directories
> > >dubbo-website/docs/en-us/developers/
> > >dubbo-website/docs/zh-cn/developers/
> > >
> > > Something todo:
> > >
> > >- The menus are not added to dubbo-website/site_config/develop.js
> > >- The html files are not generated because my local docsite
> > environment
> > >is bad
> > >- Some markdown files under dubbo-website/docs/zh-cn/developers
> should
> > >be translated to Chinese
> >
> > Could you please create an issue on Github?
> >
> > >
> > >
> > >
> > > Xin Wang  于2018年11月16日周五 下午5:55写道：
> > >
> > > > Then I  will transfer the Chinese version  committer guide to the
> > > > http://dubbo.apache.org/en-us/docs/developers/guide_dev.html
> > > >
> > > > yuhang xiu  于2018年11月16日周五 下午5:53写道：
> > > >
> > > >> Hi,
> > > >>
> > > >> Agree with u.
> > > >> When I became a committer, I referenced the version of Xin Wang's
> > blog [1]
> > > >> and asked him some questions.
> > > >>
> > > >> The new committer can also refer to this Chinese document for the
> time
> > > >> being. Of course, you can also email specific people.
> > > >>
> > > >> [1]https://lovepoem.github.io/2018/06/05/apache-committer/
> > > >>
> > > >> Huxing Zhang  于2018年11月16日周五 下午5:48写道：
> > > >>
> > > >> > Hi Community,
> > > >> >
> > > >> > Recently we've added several committers in. I found that some of
> > them
> > > >> > might have difficulties in following the documentation. I've
> > received
> > > >> > some off-list request to explain the content.
> > > >> >
> > > >> > While they could ask on the mailing list (private@ is better,
> > because
> > > >> > they are not publicly announced as committer), I am thinking that
> we
> > > >> > should have Chinese version of the new committer guide, which
> might
> > > >> > help them easier to follow the process.
> > > >> >
> > > >> > I remember that one of the PMCs has translated it before.  But I
> > can't
> > > >> > find it. I suggest we put it to the official website for
> > > >> > developers[2].
> > > >> >
> > > >> > I am also suggesting that we should move the existing guide to
> > > >> > official website, so that people could improve them by sending
> pull
> > > >> > request.
> > > >> >
> > > >> > How do you think?
> > > >> >
> > > >> > [1]
> > https://github.com/apache/incubator-dubbo/wiki/New-Committer-Guide
> > > >> > [2] http://dubbo.apache.org/en-us/docs/developers/guide_dev.html
> > > >> >
> > > >> > --
> > > >> > Best Regards！
> > > >> > Huxing
> > > >> >
> > > >>
> > > >
> >
> >
> >
> > --
> > Best Regards！
> > Huxing
> >
>

Re: Transfer wiki New Committer Guide to Official website

[Xin Wang]

Now  I send a pr :https://github.com/apache/incubator-dubbo-website/pull/178

Change log :

   - Markdown files added to these directories
   dubbo-website/docs/en-us/developers/
   dubbo-website/docs/zh-cn/developers/

Something todo:

   - The menus are not added to dubbo-website/site_config/develop.js
   - The html files are not generated because my local docsite environment
   is bad
   - Some markdown files under dubbo-website/docs/zh-cn/developers should
   be translated to Chinese



Xin Wang  于2018年11月16日周五 下午5:55写道：

> Then I  will transfer the Chinese version  committer guide to the
> http://dubbo.apache.org/en-us/docs/developers/guide_dev.html
>
> yuhang xiu  于2018年11月16日周五 下午5:53写道：
>
>> Hi,
>>
>> Agree with u.
>> When I became a committer, I referenced the version of Xin Wang's blog [1]
>> and asked him some questions.
>>
>> The new committer can also refer to this Chinese document for the time
>> being. Of course, you can also email specific people.
>>
>> [1]https://lovepoem.github.io/2018/06/05/apache-committer/
>>
>> Huxing Zhang  于2018年11月16日周五 下午5:48写道：
>>
>> > Hi Community,
>> >
>> > Recently we've added several committers in. I found that some of them
>> > might have difficulties in following the documentation. I've received
>> > some off-list request to explain the content.
>> >
>> > While they could ask on the mailing list (private@ is better, because
>> > they are not publicly announced as committer), I am thinking that we
>> > should have Chinese version of the new committer guide, which might
>> > help them easier to follow the process.
>> >
>> > I remember that one of the PMCs has translated it before.  But I can't
>> > find it. I suggest we put it to the official website for
>> > developers[2].
>> >
>> > I am also suggesting that we should move the existing guide to
>> > official website, so that people could improve them by sending pull
>> > request.
>> >
>> > How do you think?
>> >
>> > [1] https://github.com/apache/incubator-dubbo/wiki/New-Committer-Guide
>> > [2] http://dubbo.apache.org/en-us/docs/developers/guide_dev.html
>> >
>> > --
>> > Best Regards！
>> > Huxing
>> >
>>
>

Re: Transfer wiki New Committer Guide to Official website

[Xin Wang]

Then I  will transfer the Chinese version  committer guide to the
http://dubbo.apache.org/en-us/docs/developers/guide_dev.html

yuhang xiu  于2018年11月16日周五 下午5:53写道：

> Hi,
>
> Agree with u.
> When I became a committer, I referenced the version of Xin Wang's blog [1]
> and asked him some questions.
>
> The new committer can also refer to this Chinese document for the time
> being. Of course, you can also email specific people.
>
> [1]https://lovepoem.github.io/2018/06/05/apache-committer/
>
> Huxing Zhang  于2018年11月16日周五 下午5:48写道：
>
> > Hi Community,
> >
> > Recently we've added several committers in. I found that some of them
> > might have difficulties in following the documentation. I've received
> > some off-list request to explain the content.
> >
> > While they could ask on the mailing list (private@ is better, because
> > they are not publicly announced as committer), I am thinking that we
> > should have Chinese version of the new committer guide, which might
> > help them easier to follow the process.
> >
> > I remember that one of the PMCs has translated it before.  But I can't
> > find it. I suggest we put it to the official website for
> > developers[2].
> >
> > I am also suggesting that we should move the existing guide to
> > official website, so that people could improve them by sending pull
> > request.
> >
> > How do you think?
> >
> > [1] https://github.com/apache/incubator-dubbo/wiki/New-Committer-Guide
> > [2] http://dubbo.apache.org/en-us/docs/developers/guide_dev.html
> >
> > --
> > Best Regards！
> > Huxing
> >
>

Re: A proposal for transfer dubbo-samples to github.com/apache

[Xin Wang]

I think it‘s this one : https://issues.apache.org/jira/browse/INFRA-17180

Huxing Zhang  于2018年11月14日周三 下午1:25写道：

> Hi,
>
> I am wondering that is there any update to this thread?
> On Fri, Oct 26, 2018 at 1:24 PM Jerrick Zhu  wrote:
> >
> > OK, thank u very much.
> >
> > I'll open an issue there.
> >
> > On Fri, Oct 26, 2018 at 1:22 PM Xin Wang 
> wrote:
> >
> > > Jerrick,
> > > You can create an issue in the apache infrastructure project like
> this
> > > : https://issues.apache.org/jira/browse/INFRA-16182
> > > Someone will help you to transfer the repository
> > >
> > > Jerrick Zhu  于2018年10月26日周五 上午11:36写道：
> > >
> > > > Now package name and groupId have been changed to org.apache.dubbo.
> > > >
> > > > And I've send email to contributors that haven't signed the ICLA.
> > > >
> > > > Next step is to move dubbo-samples to apache group, as the name
> > > > "incubator-dubbo-samples", who can help to do this?
> > > >
> > > > Sincerely.
> > > >
> > > > Jerrick
> > > >
> > > > On Wed, Oct 17, 2018 at 3:20 PM Jerrick Zhu 
> wrote:
> > > >
> > > > > welcome.
> > > > >
> > > > > I'll file some issues on dubbo/dubbo-samples.
> > > > >
> > > > > On Wed, Oct 17, 2018 at 3:11 PM Justin W  wrote:
> > > > >
> > > > >> I would like to contribute!
> > > > >>
> > > > >> 
> > > > >> leyou...@live.cn
> > > > >>
> > > > >> From: Jerrick Zhu<mailto:jerr...@apache.org>
> > > > >> Date: 2018-10-17 14:52
> > > > >> To: dev@dubbo.apache.org<mailto:dev@dubbo.apache.org>
> > > > >> Subject: A proposal for transfer dubbo-samples to
> github.com/apache
> > > > >> hi, community
> > > > >>
> > > > >> Now Dubbo has joined Apache, but we have lots of project that is
> not
> > > > under
> > > > >> Apache,
> > > > >> such as dubbo-samples, serialization extensions, and registry
> > > extensions
> > > > >> and so on, visit
> > > > >> https://github.com/dubbo for more information.
> > > > >>
> > > > >> Everything is hard to begin, so I suggest we could transfer these
> > > > projects
> > > > >> to Apache group
> > > > >> step by step, and dubbo-samples is a good beginning.
> > > > >>
> > > > >> To transfer dubbo-samples, we need to:
> > > > >> 1. change groupId to org.apache.dubbo
> > > > >> 2. change package name to org.apache.dubbo
> > > > >> 3. All files contain LICENSE
> > > > >> 4. Other IP clearance things
> > > > >>
> > > > >> So, anyone wants to join me to do this, please let me know.
> > > > >>
> > > > >> Any suggestions is also welcome.
> > > > >>
> > > > >> Sincerely.
> > > > >>
> > > > >> Jerrick
> > > > >>
> > > > >
> > > >
> > >
>
>
>
> --
> Best Regards！
> Huxing
>

[ANN] Welcome new committer Zhenqiang Yi

[Xin Wang]

Hi, Community,

On behalf of the Dubbo PPMC, I am pleased to announce that Zhenqiang Yi,
whose github id is manzhizhen, has been voted in as a new Dubbo committer.

Please join me to say congratulations to him!

Zhenqiang, would you please briefly introduce yourself to the community?

Best regards,
Xin

Re: [ANN] Welcome new committer Jinkai Ma

[Xin Wang]

Congratulations，Jinkai

马金凯  于2018年10月30日周二 上午11:29写道：

> Hi, all,
> It's my great honor to join the dubbo family, my name Jinkai Ma, and
> work at Handuyishe.
> I started using dubbo five years ago, and i like to participate in the
> open source community, it's very helpful to me.
> Hope the dubbo and apache communities gets better, best wish for
> everyone.
>
>
> --
> 发件人：Jun Liu 
> 发送时间：2018年10月30日(星期二) 11:12
> 收件人：dev 
> 主 题：[ANN] Welcome new committer Jinkai Ma
>
> Hi, Community,
>
> On behalf of the Dubbo PPMC, I am pleased to announce that Jinkai Ma,
> whose github id is majinkai, has been voted in as a new Dubbo committer.
>
> Please join me to say congratulations to him!
>
> Jinkai, would you please briefly introduce yourself to the community?
>
> Best regards,
> Jun
>
>

Re: A proposal for transfer dubbo-samples to github.com/apache

[Xin Wang]

Jerrick,
You can create an issue in the apache infrastructure project like this
: https://issues.apache.org/jira/browse/INFRA-16182
Someone will help you to transfer the repository

Jerrick Zhu  于2018年10月26日周五 上午11:36写道：

> Now package name and groupId have been changed to org.apache.dubbo.
>
> And I've send email to contributors that haven't signed the ICLA.
>
> Next step is to move dubbo-samples to apache group, as the name
> "incubator-dubbo-samples", who can help to do this?
>
> Sincerely.
>
> Jerrick
>
> On Wed, Oct 17, 2018 at 3:20 PM Jerrick Zhu  wrote:
>
> > welcome.
> >
> > I'll file some issues on dubbo/dubbo-samples.
> >
> > On Wed, Oct 17, 2018 at 3:11 PM Justin W  wrote:
> >
> >> I would like to contribute!
> >>
> >> 
> >> leyou...@live.cn
> >>
> >> From: Jerrick Zhu
> >> Date: 2018-10-17 14:52
> >> To: dev@dubbo.apache.org
> >> Subject: A proposal for transfer dubbo-samples to github.com/apache
> >> hi, community
> >>
> >> Now Dubbo has joined Apache, but we have lots of project that is not
> under
> >> Apache,
> >> such as dubbo-samples, serialization extensions, and registry extensions
> >> and so on, visit
> >> https://github.com/dubbo for more information.
> >>
> >> Everything is hard to begin, so I suggest we could transfer these
> projects
> >> to Apache group
> >> step by step, and dubbo-samples is a good beginning.
> >>
> >> To transfer dubbo-samples, we need to:
> >> 1. change groupId to org.apache.dubbo
> >> 2. change package name to org.apache.dubbo
> >> 3. All files contain LICENSE
> >> 4. Other IP clearance things
> >>
> >> So, anyone wants to join me to do this, please let me know.
> >>
> >> Any suggestions is also welcome.
> >>
> >> Sincerely.
> >>
> >> Jerrick
> >>
> >
>

What is the release date of v2.7.0 ?

[Xin Wang]

Hi,
   What is the release date of v2.7.0 ?
   Now the v2.7.0 https://github.com/apache/incubator-dubbo/milestone/18
has some issues  not fixed.

Re: Remove Java 9/10 on travis CI

[Xin Wang]

+1

翁 德志  于2018年9月26日周三 上午10:11写道：

> +1
>
> 
> leyou...@live.cn
>
> From: Jerrick Zhu
> Date: 2018-09-26 10:08
> To: dev@dubbo.apache.org
> Subject: Remove Java 9/10 on travis CI
> Hi, community
>
> Now Java 11 has been released, and it's a long term maintained version.
> Java 9 and Java 10 are only supported six months.
>
> So, remove Java 9 and 10 on Travis, only support Java8 and Java 11.
>
> Any thoughts?
>
> Sincerely.
>
> Jerrick
>

Re: reconstruction of dubbo ops

[Xin Wang]

Good job，
 I think you can setup a gitthub project to manage this refactoring
issue，then more people can take part in it

Minxuan Zhuang  于2018年8月16日周四 下午5:46写道：

> Hi community:
> I've commit a pull request:
> https://github.com/apache/incubator-dubbo-ops/pull/87 this is a
> reconstruction of dubbo Ops，the structure looks like:
>
>dubbo-admin
>  ---dubbo-ops-frontend
>  ---dubbo-ops-backend
>
> the front end is based on Vuetify  and generated
> with Vue-cli, frontend-maven-plugin
>  is used to do npm
> build
> with maven. Now this reconstruction version contains only skeleton, so I
> suggest to open *a new branch* for this pull request, Thanks.
>

Re: [VOTE]: Release Apache Dubbo (Incubating) 2.6.3 [RC3]

[Xin Wang]

+1
I've checked
 *  UT passed: `mvn clean install` on Mac with JDK8, it passed.
 *  Disclaimer exists
 *  signature is ok

YunKun Huang  于2018年8月10日周五 下午5:34写道：

> +1
>
> I saw same UT issue in travis one month before. but all tests pass in my
> local machine with java8.
>
> On 2018/08/10 08:56:02, Huxing Zhang  wrote:
> > Hi,
> >
> > Based on Justin's comments, I am changing my vote to +1 (binding) to
> release.
> >
> > I've checked:
> >
> > * incubator in name
> > * Disclaimer exists
> > * sha512 chesum ok
> > * signature ok
> > * git tag matches
> > * NOTICE and LICENSE exist in META-INF of jar files of binary release.
> > * Unit test passed on Java 8 + OSX
> > * Tested elegant shutdown with Tomcat 8.5.30
> >
> > Minor issues:
> > * The following UT sometime fails in my linux environment.
> > AbstractInterfaceConfigTest.checkApplication1:90 expected:<10[0]> but
> was:<10[]>
> > Need to take a look at it later, I've filed an issue here:
> > https://github.com/apache/incubator-dubbo/issues/2227
> >
> >
> > On Wed, Aug 8, 2018 at 11:17 AM Justin Mclean 
> wrote:
> > >
> > > Hi,
> > >
> > > Having extra information in license or notice is unfortunate but IMO
> it's
> > > just a documentation issue  rather than a licensing error. I think it
> can
> > > be fixed in the next release.
> >
> >
> >
> > >
> > > Thanks,
> > > Justin
> > >
> > > On Wed., 8 Aug. 2018, 11:36 am jun liu,  wrote:
> > >
> > > > > Each package MUST provide a LICENSE file and a NOTICE file which
> > > > > account for the package's exact content. LICENSE and NOTICE MUST
> NOT
> > > > > provide unnecessary information about materials which are not
> bundled
> > > > > in the package, such as separately downloaded dependencies.
> > > > >
> > > > > So I suggest to fix this issue and redo the vote.
> > > > >
> > > > > [1]
> > > >
> http://www.apache.org/legal/release-policy.html#licensing-documentation <
> > > >
> http://www.apache.org/legal/release-policy.html#licensing-documentation>
> > > > I am not sure if we need to redo the vote for this issue, I wonder
> what do
> > > > other developers think?
> > > >
> > > > Best regards,
> > > > Jun
> > > >
> > > > > On 7 Aug 2018, at 10:38, Huxing Zhang  wrote:
> > > > >
> > > > > Hi,
> > > > >
> > > > > Since we remove the hessian-lite, I suggest we remove the license
> info
> > > > > in LICENSE.
> > > > >
> > > > > I checked ASF release policy[1], it says:
> > > > >
> > > > > Each package MUST provide a LICENSE file and a NOTICE file which
> > > > > account for the package's exact content. LICENSE and NOTICE MUST
> NOT
> > > > > provide unnecessary information about materials which are not
> bundled
> > > > > in the package, such as separately downloaded dependencies.
> > > > >
> > > > > So I suggest to fix this issue and redo the vote.
> > > > >
> > > > > [1]
> > > >
> http://www.apache.org/legal/release-policy.html#licensing-documentation
> > > > >
> > > > >
> > > > >
> > > > > On Mon, Aug 6, 2018 at 1:59 PM Jun Liu  wrote:
> > > > >>> Hello Dubbo Community,
> > > > >>
> > > > >> This is a call for vote to release Apache Dubbo (Incubating)
> version
> > > > 2.6.3.
> > > > >>
> > > > >> The release candidates (RC3):
> > > > >> https://dist.apache.org/repos/dist/dev/incubator/dubbo/2.6.3
> > > > >>
> > > > >> Git tag for the release (RC3):
> > > > >> https://github.com/apache/incubator-dubbo/tree/dubbo-2.6.3
> > > > >>
> > > > >> Hash for the release tag:
> > > > >> 22899a4b395411496ebf03c514e7674e8073e0c3
> > > > >>
> > > > >> Release Notes:
> > > > >>
> https://github.com/apache/incubator-dubbo/blob/dubbo-2.6.3/CHANGES.md
> > > > >>
> > > > >> The artifacts have been signed with Key : 28681CB1, which can be
> found
> > > > in the keys file:
> > > > >> https://dist.apache.org/repos/dist/dev/incubator/dubbo/KEYS
> > > > >>
> > > > >> The vote will be open for at least 72 hours or until necessary
> number
> > > > of votes are reached.
> > > > >>
> > > > >> Please vote accordingly:
> > > > >>
> > > > >> [ ] +1 approve
> > > > >> [ ] +0 no opinion
> > > > >> [ ] -1 disapprove with the reason
> > > > >>
> > > > >> The previously RC2 vote thread:
> > > > >>
> > > >
> https://lists.apache.org/thread.html/39a25c905a46e7281b96f98a23f795c796616a9a20623c0bed8b90db@%3Cdev.dubbo.apache.org%3E
> > > > >>
> > > > >> Thanks,
> > > > >> The Apache Dubbo (Incubating) Team
> > > > >>
> > > > >
> > > > >
> > > > > --
> > > > > Best Regards！
> > > > > Huxing
> > > >
> > > >
> >
> >
> >
> > --
> > Best Regards！
> > Huxing
> >
>

Re: [Proposal] Dubbo Shenzhen Meetup

[Xin Wang]

+1 (binding) to hold Shenzhen meetup!

Huxing Zhang  于2018年7月20日周五 下午3:37写道：

> +1 (binding) to hold Shenzhen meetup!
>
> On Mon, Jul 16, 2018 at 1:42 PM, Huxing Zhang  wrote:
> > Hi Dubbo PMC,
> >
> > I am requesting the PMC for the approval of holding a half-day meetup
> > in Shenzhen on July 29th (Sunday). The purpose is to build the
> > community and listen to end users.
> >
> > * What is the topic focus of the event?
> > Topics including state of the Dubbo, Dubbo eco-system, and user
> > practices for using Dubbo. Details are listed below.
> >
> > * Who is organising the event
> > PMCs of Apache Dubbo (incubating)
> >
> > * When is the event
> > 2018.7.29 09:00-12:15
> >
> > * How many attendees are expected
> > 200~400
> >
> > * How much PMC involvement is there already
> > PMC are responsible to decide the topics.
> >
> > * Which marks are requested
> > Name of "Apache Dubbo (Incubating)"
> >
> > * How will the event selection work?
> > Topics will be selected by the Dubbo PMC
> >
> > * Is this for profit or non-profit?
> > Non-profit
> >
> > I am following [1] for the procedure.
> >
> > [1] http://community.apache.org/events/small-events.html
> >
> >
> > Below is a detailed agenda for the meetup.
> >
> > ## Date
> >
> > 2018.7.29 09:00-12:15
> >
> > ## Venue
> >
> > No. 16 Gao Xin Nan Qi Dao, Nanshan District, Shenzhen
> > 深圳市南山区高新南七道16深圳空体新媒体实验室有限公司
> >
> > ## Schedule
> >
> > 09:00-10:00 Check-in
> > 10:00-10:45 Apache Dubbo(incubating) Open Source Status and 2.7 Milestone
> > 10:45-11:30 The practice of microservice in Lexin
> > 11:30-12:15 Dubbo Service Mesh Agent with Akka and Netty
> >
> > ## Detailed Description
> >
> > ### Topic
> > Apache Dubbo(incubating) Open Source Status and 2.7 Milestone
> >
> > ### Summary
> > Dubbo is a distributed RPC framework developed by Alibaba, which has been
> > favored by developers since it was opened in 2012 and has been widely
> used
> > in service solutions.
> > Dubbo has caused a lot of discussion in the community since it donated
> > Apache last year. This topic brings you the changes and new features of
> > Dubbo 2.7.
> >
> > ### Speaker
> > Zhixuan Chen(hengyunabc), technical expert of Alibaba, developer of
> Dubbo,
> > MicroServices framework.
> >
> > -
> > ### Topic
> > The practice of microservice in Lexin
> >
> > ### Summary
> > Shares the architecture evolution process from single one php web
> > application to microservice in lexin,  include the 1st generation of
> > pure php microservice,  the 2nd generation of transfering from php to
> > java in core system,  and 3rd generation build now
> >
> > ### Speaker
> > Kang Bin(robinkang), senior architect of Lexin, director of
> > architecture center, led the team to build Lexin's
> > 1st and 2nd generation of architecture of microservice. Currently is
> > also responsible for the 3rd generation architecture build of
> > hybrid cloud and mutlti-active IDC architecture
> >
> > -
> > ### Topic
> > Dubbo Service Mesh Agent with Akka and Netty
> >
> > ### Summary
> > Shares the design idea and coding practice of build a Dubbo Service
> > Mesh Agent with Akka and netty.
> >
> > ### Speaker
> > Huang wenjun(whisperwind), senior developer of Goldlok Edu.
> >
> > Thank Alibaba for sponsoring this event.
> >
> > --
> > Best Regards！
> > Huxing
>
>
>
> --
> Best Regards！
> Huxing
>

[Discuss] Delete the code of dubbo/hessian-lite module of the 2.6.x and 2.5.x branches

[Xin Wang]

HI,all
  Now in the master branch, the hessian-lite module is migrated to
https://github.com/dubbo/hessian-lite
  But in the 2.6.x and 2.5.x branches, there also exist hessian-lite
module。These three hessian-lite modules are maintained independently of
each other。Now if we release the code of master and  2.6.x to maven
center，the version of hessian-lite module will have a conflict.
  So I think we can delete dubbo/hessian-lite module of the 2.6.x and
2.5.x branches，and use https://github.com/dubbo/hessian-lite
  What do you think about it ？

Re: [ANN] New committer: htynkn(YunKun Huang)

[Xin Wang]

Congratulations！

Huxing Zhang  于2018年7月10日周二 下午4:34写道：

> Hi All,
>
> On behalf of the Dubbo PPMC, I am pleased to announce that
> htynkn(YunKun Huang) has been voted in as a new Dubbo committer.
>
> Please join me to say congratulations to him!
>
> htynkn,
>
> Would you please briefly introduce yourself to the community?
>
> --
> Best Regards！
> Huxing
>

Re: 20k Github stars for Dubbo

[Xin Wang]

Awesome

Zhanhui Li  于2018年7月9日周一 下午2:52写道：

> Congratulations!
>
> > 在 2018年7月9日，下午2:42，Mercy  写道：
> >
> > Great Job!
> >
> >
> > Kind regards,
> >
> > Mercy
> >
> >
> > 在 2018/7/9 上午11:51, Huxing Zhang 写道:
> >> Hi All,
> >>
> >> I am happy to announce that Dubbo has reached 20k Github stars
> >> today[1], an important milestone for Dubbo.
> >>
> >> Dubbo is the first Java project that reaches 20k Github stars[2] in
> >> Apache Software Foundation, the second most[3] in terms of all
> >> languages in the foundation.
> >>
> >> Dubbo is open sources in 2012, till now, it is the most popular RPC
> >> framework in China, and has been adopted by many companies for their
> >> production system, including:
> >>
> >> Internet companies:
> >> * Alibaba
> >> * Dangdang
> >> * Qunar
> >> * Netease
> >> * etc.
> >>
> >> State-owned enterprises:
> >> * Industrial and Commercial Bank of China
> >> * China Telecom
> >> * China Life
> >> * etc.
> >>
> >> More use case can be found at the homepage:
> http://dubbo.incubator.apache.org/
> >>
> >> As an incubator project, the Dubbo PPMC will continue to make the
> >> community open and diverse, and we are more than happy to have
> >> everyone come to contribute, any question can be discussed on dev
> >> mailing list.
> >>
> >> [1] https://github.com/apache/incubator-dubbo
> >> [2]
> https://github.com/search?l=Java=desc=org%3Aapache=stars=Repositories
> >> [3]
> https://github.com/search?o=desc=org%3Aapache=stars=Repositories
> >>
> >
> >
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [Discuss] new version of dubbo ops

[Xin Wang]

Authority system should be redesigned：
1、Smaller granularity permissions control
2、Can match the authority system of the business system itself


马金凯  于2018年7月5日周四 下午3:51写道：

> How about pluggable alarms module
>
>
> -- 原始邮件 --
> 发件人: "Zonghai Shang";
> 发送时间: 2018年7月5日(星期四) 下午3:39
> 收件人: "dev";
>
> 主题: Re: [Discuss] new version of dubbo ops
>
>
>
> +1 for merge admin and monitor to one
> +1 for use bootstrap+Vue.js for front end rendering, rest framwork is more
> flexible.
>
> Andrea Del Bene  于2018年7月5日周四 下午3:26写道：
>
> > +1 for merge admin and monitor to one
> > +0.5 for use bootstrap+Vue.js. I wouldn't choose to implement it with a
> > SPA/JavaScript framework. Don't get me wrong, this kind of technology is
> > great if have to integrate with a third-part service or if you want to
> sell
> > your software as a service, but in this case (imho) it doesn't make much
> > sense. Choosing a JavaScript/REST architecture means working double on
> > server side since you have to implement both your business logic and the
> > REST APIs to expose it. It also means that you have to adopt a
> token-based
> > authentication mechanism which is usually far more complex than a
> > session-based one. So I wouldn't move away from a Java web framework.
> >
> > Just my 2 cents.
> >
> >
> > On Thu, Jul 5, 2018 at 8:44 AM, Yang Tao  wrote:
> >
> > > +1 +1
> > >
> > > Yong Zhu  于2018年7月5日周四 上午11:05写道：
> > >
> > > > +1 for merge admin and monitor to one
> > > > +1 for use bootstrap+Vue.js
> > > >
> > > > On Thu, Jul 5, 2018 at 11:00 AM Minxuan Zhuang 
> > > > wrote:
> > > >
> > > > > Hi,Community：
> > > > >
> > > > > Previously, I changed Dubbo ops back end framework from webx into
> > > spring
> > > > > boots. Now I have some suggestions about what to do next:
> > > > >
> > > > > Two ultimate goals:
> > > > > 1. Make Dubbo admin and Dubbo ops  to be  a  project
> > > > > 2. change the front end frame to the popular bootstrap+Vue.js
> > > > > The new version of Dubbo ops contains all functions in the current
> > > > version,
> > > > > including service research, weight adjustment, and information
> check
> > in
> > > > > monitor.
> > > > > Do you have any other suggestions ? please feel free to reply this.
> > > > >
> > > >
> > >
> >
> >
> >
> > --
> > Andrea Del Bene.
> > Apache Wicket committer.
> >

[Discuss] Blog topic collection

[Xin Wang]

Hi，all
The new Dubbo official website system adds a blog module
http://dubbo.apache.org/#/? Lang=zh-cn. I think we will publish some
articles on Dubbo best practices below.

The topics I can think of are as follows:

1. Dubbo and APM monitoring: Dubbo and pinpoint, Dubbo and Zipkin, Dubbo
and skywalking

2. Dubbo and distributed transaction: open source distributed transaction
integration

3. Dubbo and multilingual client integration (Python, nodejs, go...)

Do you still have any other topics ? please feel free to reply this.

Re: Requirements for upgrading the netty4 version

[Xin Wang]

+1
A complete test is required

Yong Zhu  于2018年7月4日周三 下午6:01写道：

> +1
>
> Make sure the compatibility.
>
> On Wed, Jul 4, 2018 at 5:58 PM yuhang xiu  wrote:
>
> > agree.
> >
> > 2018-07-04 17:56 GMT+08:00 Zonghai Shang :
> >
> > > Hi Dubbers!
> > >
> > > Because the `dubbo-rpc-http2` and `etcd3` registry modules have been
> > > scheduled into the development plan, but will rely on the
> > > `netty-http2-codec` feature provided by netty (not supported by netty
> > > version 4.0.35). It is recommended to upgrade to the 4.1.25-final
> version
> > > and perform a full regression test.
> > >
> > > Thank you in advance
> > >
> > > yiji
> > >
> >
>

Re: Donate dubbo-php-framework

[Xin Wang]

  Congratulations !

robinkang(康彬)  于2018年7月4日周三 上午11:41写道：

> hi, guys
>
>with the help of Ian Luo and yong zhu, we have transferred our
> dubbo-php-framework to dubbo community  , its git address is :
>
> https://github.com/dubbo/dubbo-php-framework,  we wish you will like it,
> and make it better togother : )
>
> -邮件原件-
> 发件人: Yong Zhu [mailto:diecui1...@gmail.com]
> 发送时间: 2018年5月23日 11:04
> 收件人: dev@dubbo.apache.org
> 抄送: redshi(史红哲); royzhu(朱乐超)
> 主题: Re: Donate dubbo-php-framework
>
> That's great. Welcome to Dubbo community.
>
> Jerrick
>
> On Wed, May 23, 2018 at 10:49 AM, Ian Luo  wrote:
>
> > Robin,
> >
> > It's awesome. We really need dubbo PHP implementation, and now it
> > looks we will have one soon :) You can put it in dubbo eco system
> > which's hosted under github.com/dubbo.
> >
> > Welcome to community.
> >
> > Cheers,
> > -Ian.
> >
> > On Tue, May 22, 2018 at 8:49 PM robinkang(康彬)
> > 
> > wrote:
> >
> > > Hello Dubbo community,
> > >
> > > We hava developed dubbo-php-framework which compatible with dubbo java.
> > > This framework include client , server and registry, it is a
> > > complete solution for micro-service on php platform,  have running
> > > on our product environment for two years more.
> > >
> > > Now, we would like to donate to Dubbo community, and we have signed
> > > SGA
> > by
> > > following
> > > https://github.com/apache/incubator-dubbo/wiki/Software-donation-guide
> .
> > > The source code will be open sourced soon.
> > >
> > > Tks
> > >
> > > 免责声明
> > >
> > >
> > > 此电子邮件包含本公司的机密或者专用信息，仅供标明收件地址的个人或团体使用。如果您不是此电子邮件的预期收件人，请勿阅读、复制、
> > 转发或存储此邮件。如果您已误收此邮件，请通知发件人并删除全部原始信息（包括任何原始信息的备份），并且禁止散布或分发全部或部分原始信息。
> > 本公司对于因转载本电子邮件而产生的任何损失不承担任何责任，也不担保本电子邮件中信息的准确性、适当性或完整性，
> > 并且对此产生的任何错误或疏忽不承担任何责任。
> > >
> > > lexinfintech, Inc. 
> > >
> > >
> >
>
> 免责声明
>
>
> 此电子邮件包含本公司的机密或者专用信息，仅供标明收件地址的个人或团体使用。如果您不是此电子邮件的预期收件人，请勿阅读、复制、转发或存储此邮件。如果您已误收此邮件，请通知发件人并删除全部原始信息（包括任何原始信息的备份），并且禁止散布或分发全部或部分原始信息。本公司对于因转载本电子邮件而产生的任何损失不承担任何责任，也不担保本电子邮件中信息的准确性、适当性或完整性，并且对此产生的任何错误或疏忽不承担任何责任。
>
> lexinfintech, Inc. 
>
>

Re: Promoting Dubbo in social media

[Xin Wang]

 twitter +1

jun liu  于2018年6月22日周五 上午11:09写道：

> > * Twitter
> > * Facebook
> > * Weibo
> > * Wechat Official Accounts
> > * Others
> >
> > Of course the official website will have the latest news, but I think
> > a Twitter account will definitely help to build the community from
> not
> > only China but all over the world.
>
> I am +1 for twitter.
>
> Best regards,
> Jun
>
> > On 21 Jun 2018, at 10:45 PM, Huxing Zhang  wrote:
> >
> > Hi,
> >
> > I am planning to register a Twitter account using the
> > priv...@dubbo.apache.org mail address, because it is a private mail
> > address, and all the PPMC can share the login credentials, any concern
> > about it?
> >
> > On Thu, Jun 21, 2018 at 4:16 PM, Yong Zhu  wrote:
> >> +1 for Twitter, face to all over the world.
> >>
> >> On Thu, Jun 21, 2018 at 1:25 PM Ian Luo  wrote:
> >>
> >>> +1, let's tweat :)
> >>>
> >>> On Thu, Jun 21, 2018 at 8:57 AM Yunkun Huang  wrote:
> >>>
>  good idea.
> 
>  I think to choose only one is easy to start this work.
> 
>  On 2018/06/20 13:31:02, Huxing Zhang  wrote:
> > Hi All,
> >
> > In order to help promote Dubbo to the world, I am thinking about
> > setting up a social media account for Dubbo, for example, we can
> > choose one (or more) of the following:
> >
> > * Twitter
> > * Facebook
> > * Weibo
> > * Wechat Official Accounts
> > * Others
> >
> > Of course the official website will have the latest news, but I think
> > a Twitter account will definitely help to build the community from
> not
> > only China but all over the world.
> >
> > I have checked some of the ASF incubating project, e.g.
> Skywalking[1],
> > ServiceComb[2], they all have official twitter accounts.
> >
> > [1] https://twitter.com/AsfSkyWalking
> > [2] https://twitter.com/ServiceComb
> >
> > --
> > Best Regards！
> > Huxing
> >
> 
> >>>
> >
> >
> >
> > --
> > Best Regards！
> > Huxing
>
>

Re: [Proposal] Dubbo Shanghai Meetup

[Xin Wang]

+1，This is a great opportunity for developers to communicate with each other

Mercy  于2018年6月15日周五 下午3:05写道：

> +1, Good Jobs.
>
>
> Kind regards,
>
> Mercy Ma
>
>
> 在 2018/6/14 下午11:45, Huxing Zhang 写道:
> > Hi Dubbo PMC,
> >
> > I am requesting the PMC for the approval of holding a half-day meetup
> > in Shanghai to build the community and provide a way to listen to end
> > users in order to make Dubbo better.
> >
> > * What is the topic focus of the event?
> > Topics including status of Dubbo, Dubbo with cloud native, Dubbo
> > eco-system, and user practices for using Dubbo. Details are listed
> > below.
> >
> > * Who is organising the event
> > PMCs of Apache Dubbo (incubating)
> >
> > * When is the event
> > 2018.6.23 13:00-17:15
> >
> > * How many attendees are expected
> > 200~400
> >
> > * How much PMC involvement is there already
> > PMC are responsible to decide the topics.
> >
> > * Which marks are requested
> > Name of "Apache Dubbo (Incubating)"
> >
> > * How will the event selection work?
> > Topics will be selected by the Dubbo PMC
> >
> > * Is this for profit or non-profit?
> > Non-profit
> >
> > I am following [1] for the procedure.
> >
> > [1] http://community.apache.org/events/small-events.html
> >
> >
> > Below is a detailed agenda for the meetup.
> >
> > ## Date
> >
> > 2018.6.23 13:00-17:15
> >
> > ## Venue
> >
> > International Roadshow Hall, 1st floor, No. 800 Naxian Road
> > Zhangjiang International Innovation Harbor, Pudong Xinqu District,
> Shanghai
> > 浦东新区纳贤路800号张江国际创新港 一楼（国际路演厅）
> >
> > ## Schedule
> >
> > 13:00-14:00 Check-in
> > 14:00-14:45 Apache Dubbo(incubating) Open Source Status and Roadmap(Yong
> Zhu)
> > 14:45-15:30 Thoughts of Dubbo Cloud Native (Mercy Ma)
> > 15:30-15:45 Tea break
> > 15:45-16:30 Nacos - Contribute to Dubbo Ecology, Alibaba Service
> Registry and
> > Configuration Center Open Source Initiative (Guo Ping)
> > 16:30-17:15 Internet financial with dubbo (Zhiwei Pan)
> >
> > ## Detailed Description
> >
> > Topic:
> > Apache Dubbo(incubating) Open Source Status and Roadmap
> >
> > Abstract:
> > Dubbo is a distributed RPC framework developed by Alibaba, which
> > has been favored by developers since it was opened in 2012 and has been
> > widely used in service solutions. Now there has nearly 20,000 stars on
> > github after remaintenance, with a huge response in the community. This
> > topic brings you the recent works as well as some thoughts with the
> roadmap.
> >
> > Speaker Bio:
> > Yong Zhu(Jerrick), senior technical expert of Alibaba, developer
> > of Dubbo, MicroServices framework.
> >
> > -
> > Topic:
> > Thoughts of Dubbo Cloud Native
> >
> > Abstract:
> > Discuss about Dubbo Cloud Native that includes introduction to Dubbo
> > Spring Boot Project, integration with Spring Cloud, and some thoughts
> > of supporting popular CNCF projects.
> >
> > Speaker Bio:
> > Mercy Ma (mercyblitz), Technical expert of Alibaba, developer of
> > Apache Dubbo, work at Micro-Services Architecture involving
> > infrastructure build and technical integration.
> >
> > -
> > Topic:
> > Nacos - Contribute to Dubbo Ecology, Alibaba Service Registry and
> > Configuration Center Open Source Initiative
> >
> > Abstract:
> > Shares the new challenges faced by the service registration center and
> > service configuration management in the modern application
> service-centric
> > architecture in the cloud era, and the latest open source project Nacos.
> >
> > Speaker Bio:
> > Guo Ping (Penn), senior technical expert of Alibaba, head of the product
> > line of soft load and configuration center, led the team to build
> Alibaba's
> > soft load balancing system and operates the world's largest production
> > configuration center system. Currently, he is also responsible for the
> ACM
> > cloud application configuration management products ACM and ANS (EDAS
> > component market).
> >
> > -
> > Topic:
> > Internet financial with dubbo
> >
> > Abstract:
> > How to use Dubbo to split and manage services during the rapid
> > development of Internet Finance
> >
> > Speaker Bio:
> > Zhiwei Pan, 上海融之家金融信息服务有限公司
> >
> > Thank Alibaba for sponsoring this event.
> >
>
>

Re: Supportted java version

[Xin Wang]

+1 to support java8 in a new deploy branch: 2.7.x

We can use the new features of JDK， such as ：lambda expression, functional
programming

Yong Zhu  于2018年6月13日周三 上午11:36写道：

> +1
>
> We are now repackaging dubbo to org.apache[1]. It's convenient to get
> compatible with custom extension and SPI in 1.8
>
> [1]
>
> https://lists.apache.org/thread.html/769b7f813a46bdbf5ad4046c1037af301dee673317c9c7545161fed3@%3Cdev.dubbo.apache.org%3E
>
> On Wed, Jun 13, 2018 at 11:25 AM, 修宇航  wrote:
>
> > +1
> > 1.8 is the latest adjective version of jdk. It makes sth easy in dubbo.
> >
> > 2018-06-13 11:18 GMT+08:00 hty...@gmail.com :
> >
> > > strong +1 for switch to java8
> > >
> > > After we switch to java8, it will be a great stuff if we can apply new
> > > language feature to dubbo project.
> > >
> > > On 2018/06/13 03:09:03, Ian Luo  wrote:
> > > > Hi All,
> > > >
> > > > Since java7 has been announced EOL long time before [1], I think we
> > > should
> > > > switch to Java 8. Once it's done, we can start to use FP, streaming
> > API,
> > > > default interface and many other new features introduced since Java
> 8,
> > > and
> > > > make the code cleaner and faster.
> > > >
> > > > But considering Dubbo is widely deployed, and some users may have not
> > > > switched to Java 8 yet, we should keep Java 7 support on branch
> 2.6.x,
> > > but
> > > > we should definitely switch the development activities on master
> branch
> > > and
> > > > fix severe bug only on branch 2.6.x.
> > > >
> > > > What do you think?
> > > >
> > > > Thanks,
> > > > -Ian.
> > > >
> > > > 1.
> https://www.infoq.com/news/2015/05/Oracle-Ends-Java-7Public-Updates
> > > >
> > > > On Wed, Mar 28, 2018 at 9:34 AM htynkn  wrote:
> > > >
> > > > > hey team,
> > > > >
> > > > >
> > > > > What's the supportted java version for dubbo now?
> > > > >
> > > > >
> > > > > In travis file, I can see it's using java7 and java8. do we have
> > > offical
> > > > > support java9 or even java10?
> > > > >
> > > > >
> > > > > Regards,
> > > > > Yunkun
> > > >
> > >
> >
>

Re: [DISCUSS] Changing Dubbo logo and Dubbo website

[Xin Wang]

Firstly，I think a new website with navigation bar and rich content is
necessary.

Then the question is:
   How to discuss and decide on the design of a logo and website？Anyone
here gives his own design, and then we vote to choose one?

Mercy  于2018年6月12日周二 下午5:01写道：

> I think Dubbo requires new logo ASAP.
>
>
> Kind regards,
>
> Mercy Ma
>
>
> 在 2018/6/8 上午10:56, Huxing Zhang 写道:
> > Hi All,
> >
> > I'd like to bring a discussion about changing Dubbo logo and website.
> >
> > Background:
> > * Dubbo's current logo[1] was designed about 5 years ago and has
> > served for us very well. As Dubbo has joined Apache, I think it is
> > time to have a new logo to embrace the new era.
> > * Dubbo's the current website has provide very useful information for
> > users to quickly learn the basic architecture and bootstrap the first
> > Dubbo application. However I think there is still lots of work we can
> > improve, for example:
> > * no navigation bar/side bar, it is not easy for user to find the
> > link to documentation
> > * no introduction to Dubbo's core features
> > * the current documentation is using gitbooks, the content is not
> > well organized and has inconsistent style with the website
> > * no official blogs
> > * no introduction to the community
> > * no introduction to the eco-system
> >
> > Combining the thoughts, I think it is necessary to have a brand new
> > website and new logo.
> >
> > Any comments?
> >
> > [1]
> https://pic1.zhimg.com/v2-ef111936140375fa6adeba8b740c1d44_1200x500.jpg
>
>

Re: Dubbo new logo and new website

[Xin Wang]

Hi，huxing

How can you show the design of logo and website at present? Let's discuss
about it.

Justin Mclean  于2018年6月10日周日 下午2:31写道：

> Hi,
>
> > Designing a new logo requires skills which the committers might lack of.
>
> They might they may not or they may know people who help, several projects
> I know have gotten a new logo this way.
>
> Thanks,
> Justin

Re: Planing to rename dubbo package to org.apache

[Xin Wang]

>Now, there also have 23 PRs under reviewing, we need to fix them first,
merge or close it

I think what we need to do now is to set up a deadline to deal with these
23 PRs quickly.


Jun Liu  于2018年6月8日周五 上午10:04写道：

> > I suggest that we have to freeze new comming PR after notification
> community.
>
> I don’t think it’s necessary to freeze PRs.
>
> To some extend, it'is the PRs containing pretty much changes that will
> have most of the compatibility problems. Since currently most of the
> features under progress are developing by the Dubbo team or some
> contributors who keeps a close contact with Dubbo community, we can avoid
> the compatibility problem to the greatest extend.
>
> Even though, we should still make sure that the whole community get fully
> notified of the package rename plan, so they can start or refactor their
> patches based on the codebase before or after rename.
>
> Best regards,
> Jun
>
> > On 7 Jun 2018, at 3:42 PM, Mercy  wrote:
> >
> > I suggest that we have to freeze new comming PR after notification
> community.
> >
> >
> > Kind regards,
> >
> > Mercy Ma
> >
> >
> > 在 2018/6/7 下午3:32, Yong Zhu 写道:
> >> Now, there also have 23 PRs under reviewing, we need to fix them first,
> >> merge or close it. Then we rename the package ASAP.
> >
>
>