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

[Yong Zhu]

+1

I've checked `mvn clean install` on Mac with JDK8, it's pass. And the
compatible problem about 2.5.9 and 2.5.10 is also fixed.

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
>
>

Proposal for deprecated o.a.d.c.extension.Activate#before and #after

[Yong Zhu]

hi, community

I've checked the whole source code, these two methods haven't be used.
Instead, #order is used more frequent.

More important, use these two properties for sorting is not correct. There
has a issue and PR about it. See #1926
 and #639


So, I suggest deprecating these two method on annotation Activate.


How do you think?


Sincerely.


Jerrick

Re: 2.6.3 compatible problem with 2.5.[9, 10]

[Yong Zhu]

hi, Jason

Thanks for your reporting. This is exactly a big compatible problem.

I suggest cancel the current release for 2.6.3, fix this problem ASAP.

How do you guys think?

Sincerely.

Jerrick

On Fri, Aug 3, 2018 at 10:44 AM Jason Joo  wrote:

> add the table as image:
>
>
>
> best regards,
>
> Jason
>
> On Aug 3, 2018, at 10:38, Jason Joo  wrote:
>
> hey, everyone
>
> Today i found a big compatible problem in our staging env.
>
> Issue has been submitted as
> https://github.com/apache/incubator-dubbo/issues/2174 <
> https://github.com/apache/incubator-dubbo/issues/2174>
>
> And we can check it quickly in below table:
>
> dubbo protocol fail
> 2.5.8 2.5.8 no
> 2.5.9 2.0.0(spec)
> 2.0.1(impl)(why 2.0.1?) yes
> 2.5.10 2.0.0(spec)
> 2.0.1(impl) yes
> 2.6.1 2.0.0 no
> 2.6.2 2.0.0 no
> 2.6.2 2.0.1 no
>
>
> Maybe the best way to solve this is to patch 2.6.3(just released) and
> change it to "2.0.2"
>
> Any opinion?
>
> It's better to document the change log of protocol versions.
>
>
> best regards,
>
> Jason
>
>
>

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

[Yong Zhu]

+1

All test cases pass, my environment:
* JDK: 1.8
* OS: Mac OSX

On Thu, Aug 2, 2018 at 1:11 PM YunKun Huang  wrote:

> I run `mvn clean pakcage` in Mac with java 8. All pass
>
> On 2018/08/02 01:39:03, Huxing Zhang  wrote:
> > Hi,
> >
> > On Wed, Aug 1, 2018 at 5:44 PM, Andrea Del Bene 
> wrote:
> > > Hi,
> > >
> > > running 'mvn clean test' on 2.6.3 release branch and on 2.6.x tag I
> get a
> > > failure with the following unit test:
> > >
> > >
> ---
> > > Test set: com.alibaba.dubbo.config.AbstractInterfaceConfigTest
> > >
> ---
> > > Tests run: 38, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.127
> sec
> > > <<< FAILURE! - in com.alibaba.dubbo.config.AbstractInterfaceConfigTest
> > > checkApplication1(com.alibaba.dubbo.config.AbstractInterfaceConfigTest)
> > > Time elapsed: 0.006 sec  <<< FAILURE!
> > > junit.framework.ComparisonFailure: expected:<10[0]> but was:<10[]>
> > > at
> > >
> com.alibaba.dubbo.config.AbstractInterfaceConfigTest.checkApplication1(AbstractInterfaceConfigTest.java:90)
> > >
> > > I'm working on Ubuntu 16.04 64 bit, Maven 3.5.3 and Java 1.8.0_181. At
> the
> > > moment I have no clue about what might be wrong. On branch master
> > > (2.7.0-SNAPSHOT) everything is ok, every test passes.
> >
> > This is weird, the test passed without any error on my MACOS laptop.
> > Are you constantly getting this error? If so I guess the best way is
> debugging.
> > This test basically writes the property to a file, and then read it
> > back in
> com.alibaba.dubbo.config.AbstractInterfaceConfig#checkApplication.
> >
> > If it occurs occasionally, I would suggest to add some logs in
> > com.alibaba.dubbo.config.AbstractInterfaceConfig#checkApplication to
> > see what happened to
> > ConfigUtils.getProperty(Constants.SHUTDOWN_WAIT_KEY);
> >
> > >
> > >
> > > On Wed, Aug 1, 2018 at 10:06 AM, Huxing Zhang 
> wrote:
> > >
> > >> +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:
> > >> * There are some typo in CHANGES.md, I saw it fixed in 2.6.3 release
> > >> branch, but not included in the release candidate.
> > >> * I think we need to add more examples to the convenient binary
> > >> release, so that users can quickly try Dubbo out, currently there is
> > >> only packaged jars.
> > >>
> > >> On Tue, Jul 31, 2018 at 11:51 AM, Jun Liu  wrote:
> > >> > Hello Dubbo Community,
> > >> >
> > >> > This is a call for vote to release Apache Dubbo (Incubating) version
> > >> 2.6.3.
> > >> >
> > >> > The release candidates (RC2):
> > >> > https://dist.apache.org/repos/dist/dev/incubator/dubbo/2.6.3
> > >> >
> > >> > Git tag for the release (RC2):
> > >> > https://github.com/apache/incubator-dubbo/tree/dubbo-2.6.3
> > >> >
> > >> > Hash for the release tag:
> > >> > a8be0eaaddab198ed03b0150d4db03e2b22f023f
> > >> >
> > >> > Release Notes:
> > >> >
> https://github.com/apache/incubator-dubbo/blob/2.6.3-release/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 RC1 vote thread:
> > >> > https://lists.apache.org/thread.html/6371153d4fd5645615c14518f70f42
> > >> 3134b08148c2fba72e5bb63a55@%3Cdev.dubbo.apache.org%3E
> > >> >
> > >> > Thanks,
> > >> > The Apache Dubbo (Incubating) Team
> > >> >
> > >> > Best regards,
> > >> > Jun
> > >> >
> > >>
> > >>
> > >>
> > >> --
> > >> Best Regards！
> > >> Huxing
> > >>
> > >
> > >
> > >
> > > --
> > > Andrea Del Bene.
> > > Apache Wicket committer.
> >
> >
> >
> > --
> > Best Regards！
> > Huxing
> >
>

Re: 100 contributors for Dubbo

[Yong Zhu]

That's awesome.

We're on the way, and need you.

On Wed, Aug 1, 2018 at 4:34 PM yuhang xiu  wrote:

> Congratulation!
>
> :)
>
> 2018-08-01 16:31 GMT+08:00 Huxing Zhang :
>
> > Hi,
> >
> > It is great to see that we have reached 100 contributors[1] for Dubbo.
> >
> > Contributions are always welcome for everyone!
> >
> > You can also check the "How can I contribute" section of README.md[2]
> > and CONTRIBUTING.md[3] for how to contribute. Please let me know if
> > there is something missing there.
> >
> > [1] https://github.com/apache/incubator-dubbo
> > [2] https://github.com/apache/incubator-dubbo/blob/master/README.md
> > [3]
> https://github.com/apache/incubator-dubbo/blob/master/CONTRIBUTING.md
> >
> > --
> > Best Regards！
> > Huxing
> >
>

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

[Yong Zhu]

The source dir unzipped from the source zip is named
'incubator-dubbo-dubbo-2.6.3'. Here `dubbo` is duplicated.

Is this intentional?

On Mon, Jul 30, 2018 at 10:06 AM Jun Liu  wrote:

> > I think I found an issue that may need to rebuild the release candidate.
> >
> > The source release contains a binary:
> >
> > ./.mvn/wrapper/maven-wrapper.jar
>
> Yes, you are right, I have just checked and found the binary in the exact
> position.
> We can start the rebuild today.
>
> I failed to notice that the rat and style plugin are closed by default
> when building the release candidate locally, I will open them in the next
> RC, they can help to check this kind of problems.
>
> Best regards,
> Jun
>
> > On 29 Jul 2018, at 16:14, Huxing Zhang  wrote:
> >
> > Hi,
> >
> > I think I found an issue that may need to rebuild the release candidate.
> >
> > The source release contains a binary:
> >
> > ./.mvn/wrapper/maven-wrapper.jar
> >
> > Actually I run `mvn verify -Drat.skip=false`, as a result it found the
> > archive in target/rat.txt but did not fail.
> >
> > Notes: 3
> > Binaries: 0
> > Archives: 1
> > Standards: 3
> >
> > Apache Licensed: 3
> > Generated Documents: 0
> >
> > JavaDocs are generated, thus a license header is optional.
> > Generated files do not require license headers.
> >
> > 0 Unknown Licenses
> >
> > Archives:
> >
> > + .mvn/wrapper/maven-wrapper.jar
> >
> > Previous discussion:
> >
> https://lists.apache.org/thread.html/491ecd01802c48df8d906548e1d1db188c39a9546f958e834198d276@%3Cdev.dubbo.apache.org%3E
> >
> >
> > Other details:
> >
> > * 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:
> > * There are some typo in CHANGES.md, I saw it fixed in 2.6.3 release
> > branch, but not included in the release candidate.
> >
> > On Thu, Jul 26, 2018 at 5:48 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 (RC1):
> >> https://dist.apache.org/repos/dist/dev/incubator/dubbo/2.6.3
> >>
> >> Git tag for the release (RC1):
> >> https://github.com/apache/incubator-dubbo/tree/dubbo-2.6.3
> >>
> >> Hash for the release tag:
> >> a8be0eaaddab198ed03b0150d4db03e2b22f023f
> >>
> >> Release Notes:
> >> https://github.com/apache/incubator-dubbo/blob/2.6.3-release/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
> >>
> >> Thanks,
> >> The Apache Dubbo (Incubating) Team
> >>
> >
> > --
> > Best Regards！
> > Huxing
>
>

Re: Proposal for releasing hessian-lite 3.2.4

[Yong Zhu]

hi, Ian

The release note is here: https://github.com/dubbo/hessian-lite/releases

On Wed, Jul 25, 2018 at 8:23 PM Ian Luo  wrote:

> Jerrick, do we have a release note planned so that the whole community
> understand what gets updated?
>
> Thanks,
> -Ian.
>
> On Tue, Jul 24, 2018 at 10:51 AM Yong Zhu  wrote:
>
> > hi, community
> >
> > Since hessian-lite module has been moved to dubbo eco system, the
> community
> > have fixed 2 bugs, the corresponding commits are [1] and [2].
> >
> > So I suggest releasing 3.2.4 for hessian-lite. The branch is
> > https://github.com/dubbo/hessian-lite/tree/3.2.4
> >
> > How do you guys think?
> >
> > [1]
> >
> >
> https://github.com/dubbo/hessian-lite/commit/447d963c915340c2fdb0fa720de3ed6236263df0
> > [2]
> >
> >
> https://github.com/dubbo/hessian-lite/commit/891c2b039e917cbd51606d23d934f8e11df9763b
> >
> > Sincerely.
> >
> > Jerrick
> >
>

Proposal for releasing hessian-lite 3.2.4

[Yong Zhu]

hi, community

Since hessian-lite module has been moved to dubbo eco system, the community
have fixed 2 bugs, the corresponding commits are [1] and [2].

So I suggest releasing 3.2.4 for hessian-lite. The branch is
https://github.com/dubbo/hessian-lite/tree/3.2.4

How do you guys think?

[1]
https://github.com/dubbo/hessian-lite/commit/447d963c915340c2fdb0fa720de3ed6236263df0
[2]
https://github.com/dubbo/hessian-lite/commit/891c2b039e917cbd51606d23d934f8e11df9763b

Sincerely.

Jerrick

Re: 答复: draft for Dubbo extension guide

[Yong Zhu]

That's awesome.

On Mon, Jul 23, 2018 at 2:16 PM Huxing Zhang  wrote:

> Thanks for the draft!
>
> I have posted to Wiki[1] with minor tweaks.
>
> [1] https://github.com/apache/incubator-dubbo/wiki/Dubbo-extension-guide
>
>
> On Mon, Jul 16, 2018 at 1:32 PM, Ian Luo  wrote:
> > +1, it should be a part of contribution guide on dubbo website.
> >
> > On Mon, Jul 16, 2018 at 11:05 AM Huxing Zhang  wrote:
> >
> >> Wonderful!
> >>
> >> I think this can be go to Wiki/Contributor Guide.
> >>
> >> How to you guys think?
> >>
> >> But Ideally Github wiki can only be modified by committers, which is
> >> not very contributor-friendly.
> >>
> >> I am thinking of migrating them to website. But I think it is off-topic.
> >>
> >> On Sun, Jul 15, 2018 at 10:45 AM, wu tianbiao 
> wrote:
> >> > I have test the problem.
> >> > I use windows10 mail app send email, and can use outlook receive
> >> attachment.
> >> > But the mail app cannot receive itself.
> >> > I searched the Google, Maybe a lot of mail client cannot receive.
> >> > So just copy the content to mail.
> >> >
> >> > Below is the detail:
> >> > Dubbo Use Microkernel + Plugin design pattern，Microkernel only
> >> responsible for assembly Plugin, the functions of Dubbo are implemented
> by
> >> extension points, it means that all functions of Dubbo can be replaced
> by
> >> self defined extension by user.
> >> >
> >> > ## Dubbo Ecosystem
> >> > Dubbo recommend to put extension to dubbo [ecosystem](
> github.com/dubbo).
> >> Use this pattern will keep the core dubbo cleaner and decrease the
> >> maintains work. with less code also speed up core dubbo build process.
> >> >
> >> > ## dependency
> >> > Implement your own dubbo Extension, in general is just dependence on
> API
> >> jar correspond to what you want.
> >> > for example:
> >> > ```xml
> >> > 
> >> > org.apache.dubbo
> >> > dubbo-serialization-api
> >> > ${dubbo.version}
> >> > 
> >> > ```
> >> >
> >> > ## Src Guide
> >> > Usually, implement special extension, just need reference the
> [Developer
> >> Guide](http://dubbo.apache.org/#/docs/dev/build.md?lang=en-us) docs.
> >> implement necessary interface and adept extension to dubbo. Except this,
> >> some others should under consider:
> >> > 1. Well Tested. You should write junit and mock test to eliminate
> >> potential bugs.
> >> > 2. No Warning, If some warning cannot to avoid, use @SuppressWarnings
> to
> >> suppress it, but do not abuse it.
> >> > 3. README. Add necessary readme to show how to use your extension, and
> >> something to take notice.
> >> > 4. License. make sure of use Apache License 2.0.
> >> >
> >> > ## Notify the Community
> >> > 1. commit you code to [GitHub](https://github.com).
> >> > 2. join the mail list (option).[HowTo](
> >> https://github.com/apache/incubator-dubbo/issues/1393)
> >> > 2. send email to notify the community.
> >> > 3. usually, after you send email, community will discuss your
> extension.
> >> and mentors of dubbo group will contact you for transfer project to
> dubbo
> >> ecosystem.
> >> >
> >> > ## Transfer Project to Dubbo Group
> >> > 1. dubbo mentors will ask you, grant your project owner to dubbo.
> >> > 2. dubbo mentors will create a new project under dubbo group and
> invite
> >> you join the project.
> >> > 3. Accept invitation, so you can transfer your project to new project
> >> under dubbo group.
> >> > 4. dubbo mentors do code review. after that you may make some improve
> to
> >> code.
> >> >
> >> > End. Good Luck!
> >> >
> >> > 发送自 Windows 10 版邮件<https://go.microsoft.com/fwlink/?LinkId=550986>应用
> >> >
> >> > 
> >> > 发件人: wu tianbiao 
> >> > 发送时间: Sunday, July 15, 2018 9:29:47 AM
> >> > 收件人: dev@dubbo.apache.org
> >> > 主题: 答复: draft for Dubbo extension guide
> >> >
> >> >
> >> > I’m sure that had send attachment. But when received, it lost!
> >> >
> >> > This reply mail, send attachment again!
> >> >
> >> > If fai

Re: Re: Donate sentinel-dubbo-adapter

[Yong Zhu]

Cool, Looking forward that.
On Mon, Jul 23, 2018 at 4:51 PM 赵奕豪(宿何)  wrote:

> That's a good suggestion. We're already working on the blog post about
> Sentinel and the Dubbo adapter. Once it's finished, we'll send a PR to the
> Dubbo website repository.
>
>
> Best Regrads,
> Eric
> --
> 发件人：秦金卫 
> 发送时间：2018年7月23日(星期一) 16:40
> 收件人：dev 
> 抄 送：赵奕豪(宿何) ; 林佳梁(子矜) <
> jialiang.li...@taobao.com>; 刘军(陆龟) 
> 主 题：Re:Re: Donate sentinel-dubbo-adapter
>
> By the way, cause sentinel is a new open source project, I think the
> community don't know it well, it's better that Authors write a blogpost to
> describe how to use it and how it works.
> 在 2018-07-23 15:55:49，"Huxing Zhang"  写道：
> >Hi,
> >
> >Let's wait for some time to see what other people think.
> >
> >Typically a decision is made by lazy consensus[1].
> >
> >[1] https://community.apache.org/committers/decisionMaking.html
> >
> >On Mon, Jul 23, 2018 at 3:15 PM, 赵奕豪(宿何) 
> wrote:
> >> Hi,
> >>
> >> Thanks for your guidance. I've read the extension guide and separated
> the
> >> code into this repository:
> >> https://github.com/sczyh30/alibaba-sentinel-dubbo-adapter. Could you
> please
> >> help us to do the transfer work?
> >>
> >>
> >> Regrads
> >>
> >> --
> >> 发件人：Huxing Zhang 
> >> 发送时间：2018年7月23日(星期一) 14:28
> >> 收件人：dev ; 赵奕豪(宿何) 
> >> 抄 送：林佳梁(子矜) ; 刘军(陆龟)  >
> >> 主 题：Re: Donate sentinel-dubbo-adapter
> >>
> >> Hi,
> >>
> >> Welcome!
> >>
> >> I think your proposal should go under the ecosystem, could you please
> >> follow the extension guide [1].
> >>
> >> Basically this means you may separate your code into a dedicated
> >> repository, and the admin of Dubbo group will help you to do the
> >> transfer work.
> >>
> >> [1]
> https://github.com/apache/incubator-dubbo/wiki/Dubbo-extension-guide
> >>
> >> On Mon, Jul 23, 2018 at 10:48 AM, 赵奕豪(宿何) 
> wrote:
> >>> Hello Dubbo community,
> >>>
> >>> We have developed sentinel-dubbo-adapter which intergrates with Alibaba
> >>> Sentinel, a flow control library opensourced by Alibaba. This adapter
> >>> includes two Dubbo filters which enables Sentinel to protect Dubbo
> service
> >>> consumers and providers.
> >>>
> >>> Now, we would like to donate it to Dubbo community, and we have signed
> SGA
> >>> by following
> >>> https://github.com/apache/incubator-dubbo/wiki/Software-donation-guide.
> The
> >>> source code is available here:
> >>>
> https://github.com/alibaba/Sentinel/tree/master/sentinel-adapter/sentinel-dubbo-adapter
> .
> >>>
> >>>
> >>> Regards
> >>
> >>
> >>
> >> --
> >> Best Regards！
> >> Huxing
> >
> >
> >
> >--
> >Best Regards！
> >Huxing
>

Re: [Discuss]Suggestion for solve issues more quickly and effectively

[Yong Zhu]

On Fri, Jul 20, 2018 at 4:01 PM Huxing Zhang  wrote:

> Hi,
>
> On Thu, Jul 19, 2018 at 6:11 PM, yuhang xiu  wrote:
> > I think it is better.
> > :)
> >
> > 2018-07-19 11:04 GMT+08:00 Yong Zhu :
> >
> >> How about 'NEED-CLOSE' ?
>
> This keyword is not special enough, which may introduces false positive[1].
> For examples, the following query will match some unrelated issues.
>
Right, it's not suitable. So continue to use `&` ?  Any
conclusions ?

>
> [1]
> https://github.com/apache/incubator-dubbo/issues?utf8=%E2%9C%93=is%3Aissue+is%3Aopen+NEED-CLOSE
>
> >>
> >> On Wed, Jul 18, 2018 at 6:38 PM yuhang xiu  wrote:
> >>
> >> > I agree.
> >> > But, is '&' too long to use ?  How about a abbreviation
> >> like
> >> > & or sth?
> >> >
> >> > (Sorry about last mail..)
> >> >
> >> > 2018-07-18 18:37 GMT+08:00 yuhang xiu :
> >> >
> >> > > I agree.
> >> > > But, is '&' too long to use ?  How about a
> abbreviation
> >> > > like & or
> >> > >
> >> > > 2018-07-18 18:22 GMT+08:00 Huxing Zhang :
> >> > >
> >> > >> Hi,
> >> > >>
> >> > >> I just have a new idea!
> >> > >>
> >> > >> For an issue that is ready to be closed, anyone can comment with
> >> > >> special characters, say, &.
> >> > >>
> >> > >> So committers can search the issue with the special characters, and
> >> > >> deal with it.
> >> > >>
> >> > >> https://github.com/apache/incubator-dubbo/issues?utf8=%E2%
> >> > >> 9C%93=is%3Aissue+is%3Aopen+%26READY-TO-CLOSE%26
> >> > >>
> >> > >> In this way, we can encourage users to check the existing issues
> and
> >> > mark
> >> > >> them.
> >> > >>
> >> > >> How do you think?
> >> > >>
> >> > >> On Tue, Jul 17, 2018 at 1:56 PM, Huxing Zhang 
> >> > wrote:
> >> > >> > On Tue, Jul 10, 2018 at 11:39 PM, Mark Thomas 
> >> > wrote:
> >> > >> >> On 10/07/18 07:04, jun liu wrote:
> >> > >> >>> Hi All,
> >> > >> >>>
> >> > >> >>> Now the community has become very active, pull requests and
> issues
> >> > >> are being reported in a certain amount every day, in contrast, our
> >> > response
> >> > >> seems not fast enough and issues bumped up.
> >> > >> >>>
> >> > >> >>> I've thought of a duty table for temporarily solving this
> problem,
> >> > >> committers on duty are responsible for responding to community
> >> > activities,
> >> > >> classify issues and resolve/assign issues, by doing that, we can
> >> > guarantee
> >> > >> at least some of the committers devote enough time to the community
> >> > every
> >> > >> day.
> >> > >> >>>
> >> > >> >>> Remember that we still need to encourage users to participate
> in
> >> any
> >> > >> kind of contribution, and anyone can still participate in the
> >> community
> >> > at
> >> > >> any time.
> >> > >> >>>
> >> > >> >>> Here’s an example duty form: https://github.com/apache/incu
> >> > >> bator-dubbo/wiki/Duty-Form
> >> > >> >>> Remember label issues: https://github.com/apache/incu
> >> > >> bator-dubbo/wiki/Label-an-Issue
> >> > >> >>>
> >> > >> >>> Do you guys have any ideas of how to achieve this goal?
> >> > >> >>
> >> > >> >> Just remember that every committer is a volunteer and that they
> get
> >> > to
> >> > >> >> choose what they work on. Allocating committers to tasks isn't
> >> > >> something
> >> > >> >> that happens on an ASF project.
> >> > >> >>
> >> > >> >> Growing the community is the obvious answer to an increasing
> >> backlog
> >> > of
> >> > >> >> issues. If you haven't already seen it I strongly recommend
> reading
>

Re: Re: Donate sentinel-dubbo-adapter

[Yong Zhu]

+1 for a blog to introducing how to use and how it works. It's recommended
that the blog is located in http://dubbo.apache.org/#!/blog?lang=en-us

On Mon, Jul 23, 2018 at 4:41 PM 秦金卫  wrote:

> By the way, cause sentinel is a new open source project, I think the
> community don't know it well, it's better that Authors write a blogpost to
> describe how to use it and how it works.
> 在 2018-07-23 15:55:49，"Huxing Zhang"  写道：
> >Hi,
> >
> >Let's wait for some time to see what other people think.
> >
> >Typically a decision is made by lazy consensus[1].
> >
> >[1] https://community.apache.org/committers/decisionMaking.html
> >
> >On Mon, Jul 23, 2018 at 3:15 PM, 赵奕豪(宿何) 
> wrote:
> >> Hi,
> >>
> >> Thanks for your guidance. I've read the extension guide and separated
> the
> >> code into this repository:
> >> https://github.com/sczyh30/alibaba-sentinel-dubbo-adapter. Could you
> please
> >> help us to do the transfer work?
> >>
> >>
> >> Regrads
> >>
> >> --
> >> 发件人：Huxing Zhang 
> >> 发送时间：2018年7月23日(星期一) 14:28
> >> 收件人：dev ; 赵奕豪(宿何) 
> >> 抄 送：林佳梁(子矜) ; 刘军(陆龟)  >
> >> 主 题：Re: Donate sentinel-dubbo-adapter
> >>
> >> Hi,
> >>
> >> Welcome!
> >>
> >> I think your proposal should go under the ecosystem, could you please
> >> follow the extension guide [1].
> >>
> >> Basically this means you may separate your code into a dedicated
> >> repository, and the admin of Dubbo group will help you to do the
> >> transfer work.
> >>
> >> [1]
> https://github.com/apache/incubator-dubbo/wiki/Dubbo-extension-guide
> >>
> >> On Mon, Jul 23, 2018 at 10:48 AM, 赵奕豪(宿何) 
> wrote:
> >>> Hello Dubbo community,
> >>>
> >>> We have developed sentinel-dubbo-adapter which intergrates with Alibaba
> >>> Sentinel, a flow control library opensourced by Alibaba. This adapter
> >>> includes two Dubbo filters which enables Sentinel to protect Dubbo
> service
> >>> consumers and providers.
> >>>
> >>> Now, we would like to donate it to Dubbo community, and we have signed
> SGA
> >>> by following
> >>> https://github.com/apache/incubator-dubbo/wiki/Software-donation-guide.
> The
> >>> source code is available here:
> >>>
> https://github.com/alibaba/Sentinel/tree/master/sentinel-adapter/sentinel-dubbo-adapter
> .
> >>>
> >>>
> >>> Regards
> >>
> >>
> >>
> >> --
> >> Best Regards！
> >> Huxing
> >
> >
> >
> >--
> >Best Regards！
> >Huxing
>

Re: [Discuss]Suggestion for solve issues more quickly and effectively

[Yong Zhu]

How about 'NEED-CLOSE' ?

On Wed, Jul 18, 2018 at 6:38 PM yuhang xiu  wrote:

> I agree.
> But, is '&' too long to use ?  How about a abbreviation like
> & or sth?
>
> (Sorry about last mail..)
>
> 2018-07-18 18:37 GMT+08:00 yuhang xiu :
>
> > I agree.
> > But, is '&' too long to use ?  How about a abbreviation
> > like & or
> >
> > 2018-07-18 18:22 GMT+08:00 Huxing Zhang :
> >
> >> Hi,
> >>
> >> I just have a new idea!
> >>
> >> For an issue that is ready to be closed, anyone can comment with
> >> special characters, say, &.
> >>
> >> So committers can search the issue with the special characters, and
> >> deal with it.
> >>
> >> https://github.com/apache/incubator-dubbo/issues?utf8=%E2%
> >> 9C%93=is%3Aissue+is%3Aopen+%26READY-TO-CLOSE%26
> >>
> >> In this way, we can encourage users to check the existing issues and
> mark
> >> them.
> >>
> >> How do you think?
> >>
> >> On Tue, Jul 17, 2018 at 1:56 PM, Huxing Zhang 
> wrote:
> >> > On Tue, Jul 10, 2018 at 11:39 PM, Mark Thomas 
> wrote:
> >> >> On 10/07/18 07:04, jun liu wrote:
> >> >>> Hi All,
> >> >>>
> >> >>> Now the community has become very active, pull requests and issues
> >> are being reported in a certain amount every day, in contrast, our
> response
> >> seems not fast enough and issues bumped up.
> >> >>>
> >> >>> I've thought of a duty table for temporarily solving this problem,
> >> committers on duty are responsible for responding to community
> activities,
> >> classify issues and resolve/assign issues, by doing that, we can
> guarantee
> >> at least some of the committers devote enough time to the community
> every
> >> day.
> >> >>>
> >> >>> Remember that we still need to encourage users to participate in any
> >> kind of contribution, and anyone can still participate in the community
> at
> >> any time.
> >> >>>
> >> >>> Here’s an example duty form: https://github.com/apache/incu
> >> bator-dubbo/wiki/Duty-Form
> >> >>> Remember label issues: https://github.com/apache/incu
> >> bator-dubbo/wiki/Label-an-Issue
> >> >>>
> >> >>> Do you guys have any ideas of how to achieve this goal?
> >> >>
> >> >> Just remember that every committer is a volunteer and that they get
> to
> >> >> choose what they work on. Allocating committers to tasks isn't
> >> something
> >> >> that happens on an ASF project.
> >> >>
> >> >> Growing the community is the obvious answer to an increasing backlog
> of
> >> >> issues. If you haven't already seen it I strongly recommend reading
> >> this
> >> >> post that talks about Apache Beam's experience in this area:
> >> >>
> >> >> https://lists.apache.org/thread.html/33a6c3aa0fffa6e961aa2b8
> >> 61ebde333d898a5e1062d0d71d0e13d46@%3Cdev.community.apache.org%3E
> >> >
> >> > Hi,
> >> >
> >> > I agree that we can not force anyone to do anything in the project.
> >> >
> >> > But we can still discuss how we can clean up this issue faster.
> >> >
> >> > When I was reading the legacy issues recently, I've learned something
> >> > that I would like to share.
> >> >
> >> > 1. Some of the issue are quite similar, these frequently asked
> >> > question can be summarized to the FAQ, and I think the FAQ should be
> >> > improved by anyone. That means the current FAQ should be put to
> >> > somewhere other than Wiki.
> >> > 2. Some of issues are not clearly described, making us hard to
> >> > reproduce, or reported long time ago. For these kind of issues, I
> >> > think simply reply with "Thanks for your question, would you please
> >> > try the latest version? I am going to close this issue now. Feel free
> >> > to reopen it if the problem still exists." and close it will be fine.
> >> > 3. Triage the issue with labels. This make not even committers but
> >> > contributors easily to find. For example, a label of "good start
> >> > issue" or "help wanted" may attract new users to easily jump in and
> >> > help. I've also added to "How can I contribute" in README.
> >> >
> >> >
> >> >
> >> >
> >> >>
> >> >> Mark
> >> >
> >> >
> >> >
> >> > --
> >> > Best Regards！
> >> > Huxing
> >>
> >>
> >>
> >> --
> >> Best Regards！
> >> Huxing
> >>
> >
> >
>

Re: [eco-system]create a new project to implement dotnet/c# dubbo library

[Yong Zhu]

On Wed, Jul 18, 2018 at 1:49 PM 翁 德志  wrote:

> I notice that it's only a empty project. So when will this begin?
>
I think this email is just a proposal,  right?

> IMO, using .net core would be better.
>
Great. Suggestion is welcome for a proposal.

> thx
>
> 
> leyou...@live.cn
>
> 发件人： 秦金卫
> 发送时间： 2018-07-18 01:54
> 收件人： dev@dubbo
> 主题： [eco-system]create a new project to implement dotnet/c# dubbo library
> Hi, community,
> I have created a new eco-system project to implement dotnet/c# dubbo
> library.
>
>
> ## Project Target
> - support any dotnet/c# system as a dubbo client/consumer to invoke dubbo
> remote services
> - support any dotnet/c# service to export as a dubbo remote
> service/provider
> - support any dotnet/c# consumer/provider to access dubbo registry centers
>
>
> ## Project Structure
> - dubbo-dotnet-common: this module contains some common objects and utils.
> - dubbo-dotnet-registry:  this module support to access dubbo registry
> centers.
> - dubbo-dotnet-server: this module support to export dubbo services.
> - dubbo-dotnet-client: this module support to invorke dubbo services.
> - dubbo-dotnet-demo: this module is a demo for using dotnet library.
>
>
> Project URL: https://github.com/dubbo/dubbo-dotnet
> Welcome everybody join us to make it better and discuss here.
>
>
> : )
>
>

Re: [eco-system]create a new project to implement dotnet/c# dubbo library

[Yong Zhu]

That's awesome.



On Wed, Jul 18, 2018 at 9:29 AM Huxing Zhang  wrote:

> Good to hear that!
>
> On Wed, Jul 18, 2018 at 5:40 AM, xin.victorw...@gmail.com
>  wrote:
> >
>
>
>
> --
> Best Regards！
> Huxing
>

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

[Yong Zhu]

+1 for delete dubbo/hessian-lite module of the 2.6.x and 2.5.x branches

On Fri, Jul 13, 2018 at 9:47 AM Xin Wang  wrote:

> 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: 答复: avro serialization implement

[Yong Zhu]

That's great.

On Thu, Jul 12, 2018 at 1:49 PM wu tianbiao  wrote:

> Ok, I’m be happy to do.
>
> I plan complete before Sunday, so we can discuss at weekend, and make some
> improve.
>
>
>
> Good luck!
>
>
>
> 
> 发件人: Huxing Zhang 
> 发送时间: Thursday, July 12, 2018 1:36:42 PM
> 收件人: dev@dubbo.apache.org
> 主题: Re: 答复: avro serialization implement
>
> Hi,
>
> Great suggestion! Since you have experienced, would you mind draft a
> document about this process?
>
> On Thu, Jul 12, 2018 at 10:54 AM, wu tianbiao  wrote:
> > Hi all,
> >
> > I have transfer Dubbo-serialize-avro to Dubbo ecosystem.
> >
> > Huxing’s suggestion is good idea. When I do this, I feel some confused.
> We should add a guild about this work.
> >
> > 1. Pull request template should add well-marked description of Dubbo
> ecosystem.
> >
> > 2. Dubbo home page, Developer guild, and so on should make some
> change.
> >
> > 3. Good extension project template.
> >
> > 4. When I do transfer, Dubbo dependency should change to group to
> Alibaba.
> >
> >
> >
> >
> >
> > 
> > 发件人: Huxing Zhang 
> > 发送时间: Thursday, July 12, 2018 10:22:33 AM
> > 收件人: dev@dubbo.apache.org
> > 主题: Re: avro serialization implement
> >
> > Hi,
> >
> > Do we have a documentation/guide about how to help projects go into
> > the ecosystem?
> >
> > On Wed, Jul 11, 2018 at 8:10 PM, Ian Luo  wrote:
> >> Tianbao,
> >>
> >> I've created https://github.com/dubbo/dubbo-serialization-avro, and
> also
> >> invite you into dubbo group. Pls. login github and accept my invitation,
> >> then you are ready to go :)
> >>
> >> Welcome to the community.
> >>
> >> Thanks,
> >> -Ian.
> >>
> >> On Wed, Jul 11, 2018 at 12:32 PM wu tianbiao 
> wrote:
> >>
> >>> OK，I understand.
> >>>
> >>> Let’s do this.
> >>>
> >>>
> >>>
> >>> 发送自 Windows 10 版邮件应用
> >>>
> >>>
> >>>
> >>> 
> >>> 发件人: Ian Luo 
> >>> 发送时间: Wednesday, July 11, 2018 10:09:20 AM
> >>> 收件人: dev@dubbo.apache.org
> >>> 主题: Re: avro serialization implement
> >>>
> >>> My GitHub id is beiwei30. Let's do this, I will create one new project
> >>> under dubbo group, then invite you into dubbo group so that you could
> >>> migrate your code into this new project. What do you think?
> >>>
> >>> On Tue, Jul 10, 2018 at 6:01 PM wu tianbiao 
> wrote:
> >>>
> >>> > Hi Ian Luo,
> >>> >
> >>> > I’m sorry to say, I can’t operate on GitHub.
> >>> >
> >>> > And I just invite lan[https://github.com/lan] as collaborator.
> >>> >
> >>> > Did you mind to show me more detail?
> >>> >
> >>> > Thx very much!
> >>> >
> >>> >
> >>> >
> >>> > 发送自 Windows 10 版邮件应用
> >>> >
> >>> >
> >>> >
> >>> > 
> >>> > 发件人: Ian Luo 
> >>> > 发送时间: Tuesday, July 10, 2018 10:54:49 AM
> >>> > 收件人: dev@dubbo.apache.org
> >>> > 主题: Re: avro serialization implement
> >>> >
> >>> > TianBiao,
> >>> >
> >>> > Would you mind to grant me the ownership of your project so that I
> could
> >>> > transfer your project into dubbo eco system [1]?
> >>> >
> >>> > Thanks,
> >>> > -Ian.
> >>> >
> >>> > 1. http://github.com/dubbo
> >>> >
> >>> > On Mon, Jul 9, 2018 at 5:56 PM wu tianbiao 
> wrote:
> >>> >
> >>> > > Hi all,
> >>> > >
> >>> > > As @diecui1202 mention, now Dubbo
> >>> > > recommend place extensions at ecosystem.
> >>> > >
> >>> > > So I move the RP to an separate project.
> >>> > >
> >>> > >
> >>> > >
> >>> > > addressed here:
> >>> https://github.com/playaround88/dubbo-serialization-avro
> >>> > >
> >>> > >
> >>> > >
> >>> > > Thx all
> >>> > >
> >>> > >
> >>> > >
> >>> > > 
> >>> > > From: wu tianbiao 
> >>> > > Sent: Monday, July 9, 2018 3:52:06 PM
> >>> > > To: dev
> >>> > > Subject: avro serialization implement
> >>> > >
> >>> > > Hi all,
> >>> > >
> >>> > > I post a PR for avro serialization implement. URL:
> >>> > > https://github.com/apache/incubator-dubbo/pull/1994
> >>> > >
> >>> > > As @chickenlj mention, so send an
> mail
> >>> > here
> >>> > > to discuss whether to remove this extension to the ecos.
> >>> > >
> >>> > >
> >>> > >
> >>> > >
> >>> > >
> >>> >
> >>>
> >
> > --
> > Best Regards！
> > Huxing
>
>
>
> --
> Best Regards！
> Huxing
>

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

[Yong Zhu]

Congrats.

On Tue, Jul 10, 2018 at 4:47 PM Xin Wang  wrote:

> 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: avro serialization implement

[Yong Zhu]

Great, welcome to contribute

On Mon, Jul 9, 2018 at 5:56 PM wu tianbiao  wrote:

> Hi all,
>
> As @diecui1202 mention, now Dubbo
> recommend place extensions at ecosystem.
>
> So I move the RP to an separate project.
>
>
>
> addressed here: https://github.com/playaround88/dubbo-serialization-avro
>
>
>
> Thx all
>
>
>
> 
> From: wu tianbiao 
> Sent: Monday, July 9, 2018 3:52:06 PM
> To: dev
> Subject: avro serialization implement
>
> Hi all,
>
> I post a PR for avro serialization implement. URL:
> https://github.com/apache/incubator-dubbo/pull/1994
>
> As @chickenlj mention, so send an mail here
> to discuss whether to remove this extension to the ecos.
>
>
>
>
>

Re: 20k Github stars for Dubbo

[Yong Zhu]

What a new stage! Congratulations!
On Mon, Jul 9, 2018 at 3:34 PM Shalitha Suranga 
wrote:

> Awesome!! congrats
>
> On Mon, Jul 9, 2018 at 12:39 PM Prateek Chanda 
> wrote:
>
> > Congratulations!!  Maybe I can contribute to it when I get free time.
> >
> > Prateek
> >
> >
> >
> > On 9 July 2018 at 12:15, Zhanhui Li  wrote:
> >
> > > 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;
> > > type=Repositories
> > > >>
> > > >
> > > >
> > > >
> > > > -
> > > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > > For additional commands, e-mail: general-h...@incubator.apache.org
> > >
> > >
> > > -
> > > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> > > For additional commands, e-mail: dev-h...@community.apache.org
> > >
> > >
> >
>
>
> --
> Regards,
>
> *Shalitha Suranga Bsc. CS (UG)*
> www.shalithasuranga.me
>

Re: [Discuss] new version of dubbo ops

[Yong Zhu]

+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.
>

Re: Re: Donate dubbo-php-framework

[Yong Zhu]

hi, robinkang, please file a PR for adding php to the ecosystem of dubbo,
see http://dubbo.apache.org/#/community?lang=zh-cn

Jerrick

On Wed, Jul 4, 2018 at 6:33 PM 秦金卫  wrote:

> Amazing.
>
> 在 2018-07-04 14:27:34，"Huxing Zhang"  写道：
> >On Wed, Jul 4, 2018 at 1:20 PM, Ian Luo  wrote:
> >> cool, now we have a field-tested php solution for the community:)
> >>
> >> Thanks,
> >> -Ian.
> >>
> >> On Wed, Jul 4, 2018 at 11:41 AM robinkang(康彬) <
> robink...@lexinfintech.com>
> >> wrote:
> >>
> >>> 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 : )
> >
> >Hi mentors,
> >
> >One thing need to confirm here: Is ip clearance process needed here?
> >I got confused when I was doing the ip clearance for dubbox
> >documentation last time, it turned out that the ip clearance process
> >is for TLP.
> >I did some search on the incubator list, and found this[2], but it
> >seems it is still under discussion.
> >
> >[1]
> https://lists.apache.org/thread.html/e0f8f5e308752903220535c8e6f4c0a5ec92bde78700676409e43087@%3Cgeneral.incubator.apache.org%3E
> >[2]
> https://lists.apache.org/thread.html/1e0f67758623ab688929830bf90e2aff446df7c2c286c4898cc7c893@%3Cgeneral.incubator.apache.org%3E
> >
> >>>
> >>> -邮件原件-
> >>> 发件人: 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. <http://www.lexinfintech.com/>
> >>> > >
> >>> > >
> >>> >
> >>>
> >>> 免责声明
> >>>
> >>>
> >>>
> 此电子邮件包含本公司的机密或者专用信息，仅供标明收件地址的个人或团体使用。如果您不是此电子邮件的预期收件人，请勿阅读、复制、转发或存储此邮件。如果您已误收此邮件，请通知发件人并删除全部原始信息（包括任何原始信息的备份），并且禁止散布或分发全部或部分原始信息。本公司对于因转载本电子邮件而产生的任何损失不承担任何责任，也不担保本电子邮件中信息的准确性、适当性或完整性，并且对此产生的任何错误或疏忽不承担任何责任。
> >>>
> >>> lexinfintech, Inc. <http://www.lexinfintech.com/>
> >>>
> >>>
> >
> >
> >
> >--
> >Best Regards！
> >Huxing
>

Re: Requirements for upgrading the netty4 version

[Yong Zhu]

+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

[Yong Zhu]

Cool.

I suggest next step is to translate the docs/startup and README to English.
Also, any forwards plans are recommended to discuss here via email.

Welcome to Dubbo community again!

Jerrick

On Wed, Jul 4, 2018 at 11:41 AM robinkang(康彬) 
wrote:

> 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. <http://www.lexinfintech.com/>
> > >
> > >
> >
>
> 免责声明
>
>
> 此电子邮件包含本公司的机密或者专用信息，仅供标明收件地址的个人或团体使用。如果您不是此电子邮件的预期收件人，请勿阅读、复制、转发或存储此邮件。如果您已误收此邮件，请通知发件人并删除全部原始信息（包括任何原始信息的备份），并且禁止散布或分发全部或部分原始信息。本公司对于因转载本电子邮件而产生的任何损失不承担任何责任，也不担保本电子邮件中信息的准确性、适当性或完整性，并且对此产生的任何错误或疏忽不承担任何责任。
>
> lexinfintech, Inc. <http://www.lexinfintech.com/>
>
>

The compatible module after changing package to 'org.apache.dubbo'

[Yong Zhu]

Hi, all

>From 2.7.x, `Dubbo` has renamed package to `org.apache.dubbo`, so
`dubbo-compatible`[1] module is provided.

For compatibility with older versions, we provider the following most
popular APIs(classes/interfaces):

* com.alibaba.dubbo.rpc.Filter / Invocation / Invoker / Result / RpcContext
/ RpcException
* com.alibaba.dubbo.config.annotation.Reference / Service
* com.alibaba.dubbo.config.spring.context.annotation.EnableDubbo
* com.alibaba.dubbo.common.Constants / URL
* com.alibaba.dubbo.common.extension.ExtensionFactory
* com.alibaba.dubbo.common.serialize.Serialization / ObjectInput /
ObjectOutput
* com.alibaba.dubbo.cache.CacheFactory / Cache
* com.alibaba.dubbo.rpc.service.EchoService / GenericService

The above APIs work fine with some unit tests in the test root[2].

Except these APIs, others provided in `dubbo-compatible` are just bridge
APIs without any unit tests, they may work with wrong. If you have any
demand for them, you could:

* Implement your own extensions with new APIs. (RECOMMENDED)
* Follow `com.alibaba.dubbo.rpc.Filter` to implement bridge APIs, and then
contribute to community.
* Open issue on github.

By the way, We will remove this module some day, so it's recommended that
implementing your extensions with new APIs at the right time.

Now we need your help: Any other popular APIs are missing?

For compatible module, any suggestions are welcome. Thanks.

Jerrick

[1] https://github.com/apache/incubator-dubbo/tree/master/dubbo-compatible
[2]
https://github.com/apache/incubator-dubbo/tree/master/dubbo-compatible/src/test

Re: Planing to rename dubbo package to org.apache

[Yong Zhu]

The groupId has been changed to "org.apache.dubbo".

Thanks for all your suggestions.

On Fri, Jun 15, 2018 at 2:34 PM Ian Luo  wrote:

> merged, now it is critical to provide dubbo compatibility package as soon
> as possible, since the current code base will effect existing dubbo samples
> and dubbo apps.
>
> BTW, +1 to maven groupId change without doubt.
>
> Thanks,
> -Ian.
>
> On Fri, Jun 15, 2018 at 2:23 PM Yong Zhu  wrote:
>
> > Since the pacakge has been rename to org.apache, new PRs can be sent with
> > confidence.
> >
> > Next step, I'll add dubbo-compatible.
> >
> > Another question, I suggest rename groupId to org.apache with this big
> > change, What do you think?
> >
> > On Thu, Jun 14, 2018 at 9:25 AM Yong Zhu  wrote:
> >
> > > Now, I'll start to do this task, and then send a PR to master. At the
> > same
> > > time, I'll add a new module named "dubbo-compatible" to support old
> > > extensions, this will take some time.
> > >
> > > On Fri, Jun 8, 2018 at 2:09 PM Ian Luo  wrote:
> > >
> > >> agree, let's address the exiting PRs as soon as possible, to make the
> > >> renaming package effort easier.
> > >>
> > >> -Ian.
> > >>
> > >> On Fri, Jun 8, 2018 at 10:31 AM Xin Wang  wrote:
> > >>
> > >> > >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.
> > >> > > >
> > >> > >
> > >> > >
> > >> >
> > >>
> > >
> >
>

Re: [ANNOUNCE] Apache Dubbo (incubating) Shanghai meetup on June, 23rd

[Yong Zhu]

Cheers!

Hope to see you again on next meetup at Shenzhen.

On Mon, Jul 2, 2018 at 2:29 PM Huxing Zhang  wrote:

> Hi,
>
> The Dubbo Shanghai Meetup has been held successfully on June 23rd.
>
> I would like to share some of the statistics:
>
> * Number of registration: ~700
> * Number of on site check-in: 300+
> * Live stream watches: 1+
>
> Event details:
> https://github.com/apache/incubator-dubbo/wiki/20180623-Shanghai-Meetup
> (slides and articles for each topic available)
>
> Cheers!
>
> On Thu, Jun 21, 2018 at 5:16 PM, Huxing Zhang  wrote:
> > Hi All,
> >
> > The Apache Dubbo community is pleased to announce the Shanghai meetup,
> > which will be held on June 23rd.
> >
> > Details can be found here:
> > https://github.com/apache/incubator-dubbo/wiki/20180623-Shanghai-Meetup
> >
> > --
> > Best Regards！
> > Huxing
>
>
>
> --
> Best Regards！
> Huxing
>

Re: CNCF Landscape

[Yong Zhu]

+1

It's a good approach to let global know Dubbo.

On Mon, Jul 2, 2018 at 10:13 AM Huxing Zhang  wrote:

> Hi All,
>
> At LC3 last month I have talked with the guys from the CNCF about
> Dubbo to be part of the CNCF landscape[1]. I got that everyone can
> propose it by sending a pull request.
>
> There are many Apache projects listed in the CNCF landscape, e.g.
> Kafka, Flink, RocketMQ, Zookepper, etc.
>
> I suggest we add Dubbo to the CNCF landscape. I think it will help to
> attract more global attention to Dubbo community.
>
> How do you think?
>
> [1] https://landscape.cncf.io/
>
> --
> Best Regards！
> Huxing
>

Re: Next meetup in Shenzhen?

[Yong Zhu]

+1. It's a wonderful news for guys in Shenzhen.

On Tue, Jun 26, 2018 at 2:34 PM Ian Luo  wrote:

> one side question, do we have a summary report for Shanghai meetup?
>
> On Tue, Jun 26, 2018 at 2:20 PM Huxing Zhang  wrote:
>
> > Hi,
> >
> > The Shanghai meetup has been very successful last weekend, I think we
> > should continue to hold meetups around China, I suggest we should keep
> > the meetup every one or two month in the next few months. How about we
> > do the next meetup in Shenzhen in July? Any ideas or topics are
> > welcome!
> >
> > --
> > Best Regards！
> > Huxing
> >
>

Re: Github Issue template

[Yong Zhu]

The exception stacktrace is also necessary.

Jerrick

On Thu, Jun 21, 2018 at 10:28 PM Huxing Zhang  wrote:

> On Thu, Jun 21, 2018 at 9:37 PM, YunKun Huang  wrote:
> > we also need java version
>
> Yeah, good catch!
>
> > Yunkun Huang On 06/21/2018 18:19, Huxing Zhang wrote: Hi All, We have
> pull request template, it works very well for us. When I am reviewing the
> issues, I found some of them difficult to follow up because they do not
> provide enough information. I think we also need an issue template for
> reporting issues. What I can think of is: * A checkbox to make sure the
> reporter has searched the existing issues before. (I learn from [1] and I
> like it.) * What Dubbo version are you using? * What environment are you
> using?  (Windows/linux etc.) * How to reproduce this issue? * What is the
> expected result? * What is the actual result? How do you think? [1]
> https://github.com/ant-design/ant-design/issues/10979 -- Best Regards！
> Huxing
>
>
>
> --
> Best Regards！
> Huxing
>

Re: 一个dubbo文档错误

[Yong Zhu]

Can't agree more.

Tiny contribution is also welcome. Tiny is beautiful.

Jerrick

On Thu, Jun 21, 2018 at 4:30 PM 秦金卫  wrote:

> i think you can take a PR to fix it
>
>
>
>
> | |
> 秦金卫
> 邮箱：kimmk...@163.com
> |
>
> 签名由 网易邮箱大师 定制
>
> 在2018年06月21日 15:38，Ivey Chen 写道：
> dubbo开发者你好：
>在阅读dubbo用户手册的时候发现有一处文档错误。
>
>
> 在protocol的配置说明中payload参数默认是8M，换算后应该是8388608，但是文档中写的是88388608。这个错误在中文文档和英文文档中均存在。
> 网址：英文：
>
> https://dubbo.incubator.apache.org/books/dubbo-user-book-en/references/xml/dubbo-protocol.html
> 中文：
>
> https://dubbo.incubator.apache.org/books/dubbo-user-book/references/xml/dubbo-protocol.html
>

Re: Promoting Dubbo in social media

[Yong Zhu]

+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
> > >
> >
>

Re: Pull request policy

[Yong Zhu]

notificat...@dubbo.apache.org +1

On Wed, Jun 20, 2018 at 9:39 AM Xin Wang  wrote:

> notificat...@dubbo.apache.org +1
>
> Huxing Zhang  于2018年6月20日周三 上午9:32写道：
>
> > On Tue, Jun 19, 2018 at 11:08 PM, Huxing Zhang 
> wrote:
> > > On Mon, Jun 18, 2018 at 5:13 AM, Mark Thomas  wrote:
> > >> On 17/06/18 16:46, Huxing Zhang wrote:
> > >>> Hi Community,
> > >>>
> > >>> I suggest we review the pull request merge policy. I've seen pull
> > >>> request merged but break the build. [1]
> > >>>
> > >>> My suggestion:
> > >>>
> > >>> 0. Change must use pull request, even for committers.
> > >>> 1. pull request must pass the CI build
> > >>> 2. pull request must be merged by another committer
> > >>> 3. pull request must pass review from at least one committer
> > >>>
> > >>> Thoughts?
> > >>
> > >> My recommendation is don't do it.
> > >>
> > >> You are creating multiple barriers to progress. Generally, social
> > >> controls result in a better community than technical controls.
> > >>
> > >> My suggestion is to ensure that emails about broken CI builds go to
> the
> > >> dev list and that there is a community expectation that
> > >
> > > That's a good idea. How can we enable it? Currently the build failure
> > > email is only sent to the one who commits the change or the one who
> > > merges the pull request.
> > > I think it is better to go to dev list. Maybe we can ask the infra to
> do
> > it.
> >
> >
> > After some googling, I found it can be configured in .travis.yml.
> > [1] https://docs.travis-ci.com/user/notifications/
> >
> > For example:
> >
> > notifications:
> >   email:
> > - dev@dubbo.apache.org
> >
> >
> > notificat...@dubbo.apache.org or dev@dubbo.apache.org, which one is
> > better?
> >
> > Let us wait and see what others think.
> >
> > >
> > >> if you break the
> > >> build you fix it ASAP. Further, if the build isn't fixed in a timely
> > >> manner then it should be acceptable for any committer to revert the
> > >> commit that broke the build if they wish.
> > >>
> > >> Of course, I'm not a committer here and this is just a recommendation.
> > >>
> > >> Mark
> > >
> > > --
> > > Best Regards！
> > > Huxing
> >
> >
> >
> > --
> > Best Regards！
> > Huxing
> >
>

Re: About the start error for “dubbo admin”

[Yong Zhu]

Now dubbo admin only works under JDK8. So please try it in JDK7 or JDK6.

As we are considering do some work on dubbo admin, you can check the prior
thread:
https://lists.apache.org/thread.html/523f1fefc98c96ae4b0c55b3e8f69e237ca91a0c7c5221dfe247d65f@%3Cdev.dubbo.apache.org%3E

On Fri, Jun 15, 2018 at 10:02 AM Yunkun Huang  wrote:

> Could you try jdk 8?
>
> There is a similar issue reported on jdk9. I guess jdk10 has the same
> issue.
>
> https://github.com/apache/incubator-dubbo-ops/issues/14
>
> On 2018/06/15 01:11:27, "Kakarotto" <1136232...@qq.com> wrote:
> > .Dear：
> >When I use tomcat to start dubbo admin, report
> error（java.lang.IllegalArgumentException: Unknown flag 0x1000）. zookeeper
> start ok.
> >software version:
> >dubbo:2.62 release
> >dubbo admin:2.0.0
> >zookeeper:3.4.12
> >tomcat:9.0.9
> >jdk:10.0.1
> >
> >error message(localhost.2018-06-15.log):
> >
> >
> >
> >
> >
> >
> > 请帮忙看下，我网上找了没发现解决方法，谢谢
>

Re: 0 pull request today

[Yong Zhu]

Great day.

On Thu, Jun 14, 2018 at 10:44 AM Ian Luo  wrote:

> Folks,
>
> Today we reached one achievement, that is, we've cleaned up all pull
> requests, and right now github shows 0 pull request on
> https://github.com/apache/incubator-dubbo/pulls. Congratulations to
> everyone and let's do same on the issues.
>
> BTW, look forward to seeing more PRs incoming :)
>
> Thanks,
> -Ian.
>

Re: Planing to rename dubbo package to org.apache

[Yong Zhu]

Now, I'll start to do this task, and then send a PR to master. At the same
time, I'll add a new module named "dubbo-compatible" to support old
extensions, this will take some time.

On Fri, Jun 8, 2018 at 2:09 PM Ian Luo  wrote:

> agree, let's address the exiting PRs as soon as possible, to make the
> renaming package effort easier.
>
> -Ian.
>
> On Fri, Jun 8, 2018 at 10:31 AM Xin Wang  wrote:
>
> > >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.
> > > >
> > >
> > >
> >
>

Re: Supportted java version

[Yong Zhu]

+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: Refactor Dubbo metrics

[Yong Zhu]

+1 for providing an easy way to integrate with existing popular
monitoring/tracing systems

On Wed, Jun 13, 2018 at 8:41 AM, hty...@gmail.com  wrote:

> easy integration to existing popular monitoring systems +1
>
> I think this is very important since many companies already have their own
> monitor system, it's better to provide an easy way to integrate with them
>
> On 2018/06/08 03:44:31, Huxing Zhang  wrote:
> > Hi All,
> >
> > I have took some time to look into the current implementation of Dubbo
> > metrics, and I have some observations:
> >
> > * There is no uniform API for recording the metrics, current
> > implementation is located separately in MonitorFilter and
> > ActiveLimitFilter/ExecuteLimitFilter, and it is possible to have
> > duplicate records if ActiveLimitFilter or ExecuteLimitFilter is turned
> > on.
> > * There is only total count and total response time for service/method
> > rpc calls, no statistics within a specific interval, as well as
> > response time in percentiles.
> > * No thread pool related metrics
> > * No uniform API for expose such metrics, e.g. via HTTP or JMX. This
> > make is hard for external monitoring system to scrape data from Dubbo.
> > Meanwhile, other features like circuit breaker will find it hard to
> > utilize these metrics for judgement.
> >
> > Therefore, I am considering to refactor the current implement of
> > metrics, with the following improvement:
> >
> > * Extract an uniform API for recording, and exposing the metrics
> > * Add more metric types, e.g. interval base metrics, histograms, etc.
> > * Provide easy integration to existing popular monitoring systems such
> > as Prometheus
> >
> > Any thoughts?
> >
> > --
> > Best Regards！
> > Huxing
> >
>

Re: Dubbo new logo and new website

[Yong Zhu]

+1 for sending a PR to https://github.com/apache/incubator-dubbo-website

On Wed, Jun 13, 2018 at 1:39 AM, Huxing Zhang  wrote:

> On Tue, Jun 12, 2018 at 5:06 PM, 修宇航  wrote:
> > Maybe a new repository?
> > I think it is good to create a new repository which everyone can fork and
> > submit their design(logo or doc).
>
> > The repository should have two branch named logo and doc. Good design or
> > doc will be merged into these branches.
>
> I would prefer forking
> https://github.com/apache/incubator-dubbo-website and send a pull
> request to it.
>
> > Maybe the new repository is created in https://github.com/dubbo?
>
> >
> >
> > 2018-06-12 16:36 GMT+08:00 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
> >>
>
> --
> Best Regards！
> Huxing
>

Re: Moving hessian-lite from Dubbo codebase to eco-system

[Yong Zhu]

+1

We could delay and close it first. At an appropriate time reopen it.

On Mon, Jun 11, 2018 at 5:46 PM, Ian Luo  wrote:

> Hi Jerrick & others,
>
> Since hessian-lite module is now moved out into dubbo group, should we
> close issue#1701[1], one part of our code coverage project [2]?
>
> Regards,
> -Ian.
>
> 1. https://github.com/apache/incubator-dubbo/issues/1701
> 2. https://github.com/apache/incubator-dubbo/projects/1
>
> On Thu, Jun 7, 2018 at 10:38 AM Yong Zhu  wrote:
>
> > Hi, all
> >
> > Now hessian-lite module has been moved to
> > https://github.com/dubbo/hessian-lite
> >
> > Thanks for your help.
> >
> > Jerrick
> >
> > On Mon, Jun 4, 2018 at 3:32 PM, Yong Zhu  wrote:
> >
> > > After discussing, we are about to do this in next major version, which
> is
> > > 2.7.x.
> > >
> > > The corresponding issue has also been created on github:
> > > https://github.com/apache/incubator-dubbo/issues/1778
> > >
> > > On Thu, May 17, 2018 at 2:29 PM, Mercy  wrote:
> > >
> > >> Please do it since 2.7.x!
> > >>
> > >>
> > >>
> > >> 在 2018/5/16 上午11:11, Jun Liu 写道:
> > >>
> > >>> Now we are considering that moving it to Dubbo eco-system, which is
> > >>>> https://github/dubbo.
> > >>>>
> > >>>> How do you think about this?
> > >>>>
> > >>> I agree with moving hessian-lite to the dubbo eco-system. If we do
> > that,
> > >>> we may need to upgrade the core dubbo version to 2.7.x to identify
> > >>> incompatible usage of dependencies.
> > >>>
> > >>> On 11 May 2018, at 3:57 PM, Yong Zhu  wrote:
> > >>>>
> > >>>> Hi,
> > >>>>
> > >>>> hessian-lite a customized version of the official hessian maintained
> > >>>> inside
> > >>>> Dubbo, and it's relatively stable, only upgrading for special
> bugfix.
> > >>>>
> > >>>> It's version(3.2.2) is different from Dubbo(now 2.6.2), and their
> > >>>> release
> > >>>> paces are also different.
> > >>>>
> > >>>> Now we are considering that moving it to Dubbo eco-system, which is
> > >>>> https://github/dubbo.
> > >>>>
> > >>>> How do you think about this?
> > >>>>
> > >>>> Thanks.
> > >>>> Jerrick
> > >>>>
> > >>>
> > >>
> > >
> >
>

Re: plan to do some transformation on dubbo admin and dubbo monitor

[Yong Zhu]

Webx doesn't support JDK8 and Spring4 neither.

+1 for doing that.

On Fri, Jun 8, 2018 at 1:05 PM, Huxing Zhang  wrote:

> On Fri, Jun 8, 2018 at 11:57 AM, Minxuan Zhuang 
> wrote:
> > Hi community:
> >
> > the recent version of dubbo admin is quite old, it has some problems:
> >
> > * it cannot compile and run in JDK 8
> >
> > * the dependency of webX  is out of date
> >
> > * the dubbo admin and dubbo monitor are two separated projects and hasn't
> > update for a long time.
> >
> >
> >  for these reasons,  I'm considering  to do serval  transformation:
> >
> > * change the framework from webX to spring boot.
>
> +100 for that! Webx has stopped maintenance for quite a long time, it
> does not support Java 9+, it is time to be replaced.
>
> >
> > * optimize the appearance with new front end framework.
> >
> > * integrate dubbo admin with dubbo monitor
> >
> > *  integrate with new dubbo features and enhance the existing modules
> >
> >
> >  If you have any suggestions or requires about dubbo admin(and dubbo
> > monitor),  please discuss here
>
>
>
> --
> Best Regards！
> Huxing
>

Re: Planing to rename dubbo package to org.apache

[Yong Zhu]

On Fri, Jun 8, 2018 at 10:04 AM, Jun Liu  wrote:

> I suggest that we have to freeze new comming PR after notification
> community.
>
>
> I don’t think it’s necessary to freeze PRs.
>

+1


>
> 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.
>
>
I'll start a new thread to notify the community ASAP.


> 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.
>
>
>
>

Planing to rename dubbo package to org.apache

[Yong Zhu]

Hi, all

As discussing before, we could start this in master(2.7.x) now.

The previous discuss thread:
https://lists.apache.org/thread.html/a981ec4fc34db42a246a83aa4a8ec9eaedd9322f94403788cac60898@%3Cdev.dubbo.apache.org%3E

Now, there also have 23 PRs under reviewing, we need to fix them first,
merge or close it. Then we rename the package ASAP.

After that, new PRs with bugfix need to be merged into 2.6.x and master,
other PRs with big changes or new feature only need to be merged into
master.

How do you guys think?

Best regards,
Jerrick

Re: [ANN] New committer: zonghaishang(yiji)

[Yong Zhu]

Congratulation.

On Thu, Jun 7, 2018 at 11:37 AM, shang zonghai 
wrote:

> Hi all,
>
> Thank you for your congratulation，It is a great honor to be a member of
> the committer, my name is zonghaishang(yiji)， I come from Youzan Technology
> Co., Ltd.
> In the future, I will work with the dubbo team to create a better dubbo
> ecosystem, will also better serve the community.
>
> Best Regards！
> yiji
>
> > 在 2018年6月7日，11:20，Huxing Zhang  写道：
> >
> > Hi all,
> >
> > On behalf of the Dubbo PPMC, I am pleased to announce that
> > zonghaishang (aka. yiji) has been voted in as a new Dubbo committer.
> >
> > Please join me to say congratulations to him!
> >
> > To yiji,
> >
> > Would you please briefly introduce yourself to the community?
> >
> > --
> > Best Regards！
> > Huxing
>
>

Re: Moving hessian-lite from Dubbo codebase to eco-system

[Yong Zhu]

After discussing, we are about to do this in next major version, which is
2.7.x.

The corresponding issue has also been created on github:
https://github.com/apache/incubator-dubbo/issues/1778

On Thu, May 17, 2018 at 2:29 PM, Mercy  wrote:

> Please do it since 2.7.x!
>
>
>
> 在 2018/5/16 上午11:11, Jun Liu 写道:
>
>> Now we are considering that moving it to Dubbo eco-system, which is
>>> https://github/dubbo.
>>>
>>> How do you think about this?
>>>
>> I agree with moving hessian-lite to the dubbo eco-system. If we do that,
>> we may need to upgrade the core dubbo version to 2.7.x to identify
>> incompatible usage of dependencies.
>>
>> On 11 May 2018, at 3:57 PM, Yong Zhu  wrote:
>>>
>>> Hi,
>>>
>>> hessian-lite a customized version of the official hessian maintained
>>> inside
>>> Dubbo, and it's relatively stable, only upgrading for special bugfix.
>>>
>>> It's version(3.2.2) is different from Dubbo(now 2.6.2), and their release
>>> paces are also different.
>>>
>>> Now we are considering that moving it to Dubbo eco-system, which is
>>> https://github/dubbo.
>>>
>>> How do you think about this?
>>>
>>> Thanks.
>>> Jerrick
>>>
>>
>

Re: [VOTE]: Release Apache Dubbo (Incubating) 2.6.2 [RC2]

[Yong Zhu]

+1

I have checked the build process with Java 1.8, it's success and all test
cases are pass.

Jerrick

On Mon, May 28, 2018 at 9:26 PM, Jun Liu  wrote:

> Hi All,
>
> This vote has opened for more than 72 hours in community, i think we
> should start the apache vote by tomorrow.
>
> Please reply to this email if you have any question with this release
> candidate.
>
> Best regards,
> Jun
>
> > On 25 May 2018, at 11:01 AM, Jun Liu  wrote:
> >
> > Hello Dubbo Community,
> >
> > This is a call for vote to release Apache Dubbo (Incubating) version
> 2.6.2.
> >
> > The release candidates (RC2):
> > https://dist.apache.org/repos/dist/dev/incubator/dubbo/2.6.2
> >
> > Git tag for the release (RC2):
> > https://github.com/apache/incubator-dubbo/tree/dubbo-2.6.2
> >
> > Hash for the release tag:
> > 5eeb240337ccfbc820d4bde023d8cf643f33d735
> >
> > Release Notes:
> > https://github.com/apache/incubator-dubbo/blob/dubbo-2.6.2/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
> >
> > Thanks,
> > The Apache Dubbo (Incubating) Team
>
>

Re: Donate dubbo-php-framework

[Yong Zhu]

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. 
> >
> >
>

Re: dubbo samples project

[Yong Zhu]

Here should be with applause.

On Tue, May 22, 2018 at 2:42 PM, Minxuan Zhuang  wrote:

> Hi all:
>I'm writing to tell you that I have made a dubbo-sample project to
> collect the examples of dubbo usage. At present, there are 19 samples, the
> github address is https://github.com/dubbo/dubbo-samples, Welcome to
> submit
> your code to this project.
>

Re: [VOTE]: Release Apache Dubbo (Incubating) 2.6.2 [RC1]

[Yong Zhu]

+1

All UT passed with JDK 1.8 and JDK 9 on my mac.

Some minor issues I meet:
- When compile sources on JDK 10, a NPE is thrown by
maven-javadoc-plugin:3.0.0, which is a known issue
https://stackoverflow.com/questions/49460751/execution-attach-javadocs-of-goal-org-apache-maven-pluginsmaven-javadoc-plugin
- When run test on JDK 9, the process is interrupted by
maven-checkstyle-plugin:3.0.0 accidentally.

Best regards,
Jerrick

2018-05-18 12:53 GMT+08:00 Jun Liu :

> +1
>
> I have checked that the source release works fine:
> 1. All UT passed with JDK 1.7
> 2. All core features work fine with a certain amount of demos.
> 3. Review passed for changes mentioned in release notes.
>
> Best regards,
> Jun
>
> > On 15 May 2018, at 11:49 AM, Jun Liu  wrote:
> >
> > Hello Dubbo Community,
> >
> > This is a call for vote to release Apache Dubbo (Incubating) version
> 2.6.2.
> >
> > The release candidates:
> > https://dist.apache.org/repos/dist/dev/incubator/dubbo/2.6.2 <
> https://dist.apache.org/repos/dist/dev/incubator/dubbo/2.6.2>/
> >
> > Git tag for the release:
> > https://github.com/apache/incubator-dubbo/tree/dubbo-2.6.2 <
> https://github.com/apache/incubator-dubbo/tree/dubbo-2.6.2>
> >
> > Hash for the release tag:
> > afab04c53edab38d52275d2a198ea1aff7a4f41e
> >
> > Release Notes:
> > https://github.com/apache/incubator-dubbo/releases/tag/
> untagged-4775c0a22c60fca55118  incubator-dubbo/releases/tag/untagged-4775c0a22c60fca55118>
> >
> > 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 <
> 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
> >
> > Thanks,
> > The Apache Dubbo (Incubating) Team
>
>

Moving hessian-lite from Dubbo codebase to eco-system

[Yong Zhu]

Hi,

hessian-lite a customized version of the official hessian maintained inside
Dubbo, and it's relatively stable, only upgrading for special bugfix.

It's version(3.2.2) is different from Dubbo(now 2.6.2), and their release
paces are also different.

Now we are considering that moving it to Dubbo eco-system, which is
https://github/dubbo.

How do you think about this?

Thanks.
Jerrick

Re: About Keeping dubbo's version to be SNAPSHOT on master branch

[Yong Zhu]

+1


2018-04-24 17:37 GMT+08:00 Ian Luo :

> +1
>
> Once we get the snapshot URL of apache maven repo, we could configure
> travis CI to publish snapshots automatically once the build passes.
>
> On Tue, Apr 24, 2018 at 11:30 AM, Mercy  wrote:
>
> > Hi all,
> >
> >
> > I suggest keeping *SNAPSHOT*  for new Dubbo developement version on
> > master branch , is like Spring Projects approach
> > .
> For
> > example,  current release version of dubbo is *2.6.1*,  *2.6.2* will be
> > next release and its *SNAPSHOT*(*2.6.2-SNAPSHOT) *cound be synchronized
> > on master branch , the community developers could learn and use the
> latest
> > code for new features that are traced in *2.6.2 *milestone, they don't
> > have to wait next release and might participate in discuss.
> >
> >
> > If you had any idea, let's discuss ! Thank you for your time.
> >
> >
> > Kind regards,
> >
> > Mercy
> >
>

Re: [DISCUSS] Dubbo Release schedule

[Yong Zhu]

hi, Justin

As John said in
https://lists.apache.org/thread.html/c4bc85049b02b179ef1c785b7c1a3d29c5832e389a93f2b0d91151a0@%3Cdev.dubbo.apache.org%3E

It is not mandatory to change the project groupId to org.apache.dubbo in
the first release. Is that right? We will finished it before graduating.

2018-04-19 8:48 GMT+08:00 Justin Mclean :

> Hi,
>
> > 0. Should we have release manager for these artifacts? Is there any
> > committer volunteer to be release manager?
>
> In general Apache project do have release managers.
>
> > 1. Should we keep the release cycle for 2.6.x?  Our first Apache
> > release might take some time because we have bunch of things to do
> > [1][2][3]. If we need to do keep it, we'd better enter code freeze
> > soon as start to prepare for the release.
>
> I would suggest making a release branch and not doing a code freeze as the
> release may take a little time to get right.
>
> One issue I’m concerned about is IP clearance [1] as that is likely to
> block the release.
>
> Thanks,
> Justin
>
> 1 https://issues.apache.org/jira/browse/DUBBO-3
>
>

Re: List volume and issue tracking

[Yong Zhu]

I have the same feeling.

IMO, all the issue emails should be sent to iss...@dubbo.apache.org, all
the PR emails should be sent to comm...@dubbo.apache.org. How do you think?
and who can help to fix this?

And I think we should use github issues, and move all the Jira issues to
github.

2018-04-03 16:43 GMT+08:00 Mark Thomas :

> All,
>
> I've been away for just over a week and come back to find over 300
> unread emails on the dev list.
>
> A large proportion of these messages are comments on pull requests? Is
> dev@ the right list for those?
>
> Another large proportion appear to be comments on issues? Is dev@ the
> right list for those?
>
> Generally, the recommendation is to split into multiple lists based on
> audience rather than topic. For some projects it therefore makes sense
> to have all dev related traffic going to a single list. For others,
> particularly large projects, it makes sense to split the dev traffic.
>
> The project appears to be using GitHub issues and Jira. That is
> confusing. I'd recommend that you select one issue tracker and stick to it.
>
> Finally, the github issues seem to be a mix of bugs and support
> questions. Is that the way the podling wants to use github issues?
>
> I have no view on what the 'right' answers to the above questions are.
> I'm asking them to get the podling thinking about the issues. What, if
> anything, to do about any of the above is for the podling to decide.
>
>
> Mark
>

Re: About the parent pom, groupId and package name of Dubbo project

[Yong Zhu]

John, I got it, thanks so much.

2018-03-16 18:46 GMT+08:00 John D. Ament <johndam...@apache.org>:

> On Fri, Mar 16, 2018 at 3:47 AM Yong Zhu <diecui1...@gmail.com> wrote:
>
> > Hi, all
> >
> > I'm working on this issue:
> >
> > https://issues.apache.org/jira/projects/DUBBO/issues/
> DUBBO-7?filter=allopenissues
> >
> > I have the below questions:
> >
> > 1. Shall we need to change the pom.xml parent to org.apache:apache:19 ?
> Now
> > we use sonatype oss as the central repository.
> >
>
> You don't have to use apache parent pom, however you should expect to build
> against our nexus instance instead of sonatype's oss.  If you read through
> the new setup instructions, you can follow them pretty closely except use
> our nexus instance.
>
>
> > 2. Shall we need to change all the java package name to org.apache.* ? If
> > do this, users will encounter the upgrading problem.
> >
>
> The current package is com.alibaba.dubbo right?  Unfortunately this puts us
> into a "you have to rename it" situation.  Including the company name in
> the package is a problem for our branding/trademarks.
>
>
> > 3. Now, our groupId is "com.alibaba", shall we need to change it to
> > "org.apache"?
> >
>
> Most projects follow a "org.apache.projectName" naming scheme.  So
> org.apache.dubbo would be expected.
>
>
> >
> > Thanks.
> >
> > Yong Zhu.
> >
>

Re: dubbo.io is not accessible, working to fix it

[Yong Zhu]

Hi,

A suggestion is that we host all web resources to dubbo.apache.org, and
also keep dubbo.io by redirecting dubbo.io to dubbo.apache.org because of
the existing users.

Thanks.

2018-03-16 13:03 GMT+08:00 Justin Mclean :

> Hi,
>
> > Right now I think it is better to keep both since dubbo.io is already
> > widely known.
>
> I suggest you read up on ASF branding policy in particular [1] and [2].
> While there have been a couple of exceptions to this it’s probably best to
> migrate that content over to the apache.org site.
>
> Thanks,
> Justin
>
> 1. https://www.apache.org/foundation/marks/pmcs#websites
> 2. https://www.apache.org/foundation/marks/pmcs#nonapache