Re: [VOTE]: Release Apache Dubbo-go v1.1.0

[kimm king]

[v] +1 release the software

Shunyu Lei  于2019年9月5日周四 下午9:38写道：

> +1
>
> Ian Luo  于2019年9月5日周四 下午9:25写道：
>
> > +1 to approve. I checked the items below:
> >
> >
> > [v]  Are release files in correct location?
> >
> > [v] Are the digital signature and hashes correct?
> >
> > [v] Do LICENSE and NOTICE files exists?
> >
> > [v] Is the LICENSE and NOTICE text correct?
> >
> > [v] Is the NOTICE year correct?
> >
> > [v] Un-included software dependencies are not mentioned in LICENSE or
> > NOTICE?
> >
> > [v] License information is not mentioned in NOTICE?
> >
> > [x] Is there any 3rd party code contained inside the release? If so:
> >
> > [v] Does the software have a compatible license?
> >
> > [v] Are all software licenses mentioned in LICENSE?
> >
> > [v] Is the full text of the licenses (or pointers to it) in LICENSE?
> >
> > Is any of this code Apache licensed? Do they have NOTICE files? If so:
> >
> > [v] Have relevant parts of those NOTICE files been added to this NOTICE
> > file?
> >
> > [v] Do all source files have ASF headers?
> >
> > [v] Do the contents of the release match with what's tagged in version
> > control?
> >
> > [x] Are there any unexpected binary files in the release?
> >
> > [v] Can you compile from source? Are the instruction clear?
> >
> >
> > I vote with:
> >
> > [v] +1 release the software
> >
> > [ ] +0 not sure if it should be released
> >
> > [ ] -1 don’t release the software because...
> >
> >
> > The README.md doesn't contain the clear instructions for build and unit
> > test, but I think this minor issue can be fixed in the next release.
> >
> >
> > Regards,
> >
> > -Ian.
> >
> > On Wed, Sep 4, 2019 at 8:17 PM Stocks Alex 
> > wrote:
> >
> > > Hello Dubbo/Dubbogo Community,
> > >
> > >  This is a call for vote to release Apache Dubbo-go version v1.1.0.
> > >  The release candidates:
> > > https://dist.apache.org/repos/dist/dev/dubbo/dubbo-go/1.1.0/
> > >  Git tag for the release:
> > >  https://github.com/apache/dubbo-go/tree/1.1
> > >  Hash for the release tag:
> > >  e63630a5bd140da5c3643a602c8787ad264d550c
> > >  Release Notes:
> > >  https://github.com/apache/dubbo-go/blob/1.1/CHANGE.md
> > >  The artifacts have been signed with Key :0D963B35B7F1E689, which can
> be
> > >  found in the keys file:
> > >  https://dist.apache.org/repos/dist/dev/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-go Team
> > >
> >
>

Re: [DISCUSS] Migrating projects under dubbo group

[kimm king]

Of course, dubbo-dotnet is also need to transfer.

Huxing Zhang  于2019年4月26日周五 下午5:56写道：

> Hi,
>
> On Fri, Apr 26, 2019 at 5:50 PM kimm king  wrote:
> >
> > I will transfer jms-for-apache-dubbo rpc-xmlrpc-for-apache-dubbo
> awesome-dubbo to ASF before the end of May.
>
> There is a pull request to merge rpc-xmlrpc-for-apache-dubbo into
> incubator-dubbo, so I think there is no need to transfer.
> What about dubbo-dotnet project?
>
>
> >
> > Huxing Zhang  于2019年4月26日周五 下午4:01写道：
> >>
> >> 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
> >> > * metrics
> >> > * hessian-lite
> >> > * dubbo-sentinel-support
> >> > * awesome-dubbo
> >> > * dubbo-remoting-js
> >> > * egg-dubbo-rpc
> >> > * rpc-native-thrift-for-apache-dubbo
> >> > * intellij-idea-plugin
> >> > * initializr
> >> >
> >> >
> >> > If you are the project owner, could you please confirm that:
> >> >
> >> > 1) are you willing to transferred to ASF or not.
> >> > 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
> >> > - If the code belongs to your company, you need to sign the SGA[3]
> >> > - request ASF infra to transfer the project
> >> > 3) if not, please indicate that which group you will transfer to.
> >> >
> >> > 2. Gain write access to your project after transfer
> >> >
> >> > If your project has been transferred to ASF, you will lose write
> >> > access temporally. The Dubbo community will vote you in as committer
> >> > by following standard ASF way. This means you have to contribute to
> >> > the project for some time in order to earn enough merit.
> >> >
> >> > 3. After the transition is done, delete group A.
> >> >
> >> > The community will summarize and keep track of the status here[4].
> >> >
> >> >
> >> > [1] https://en.wikipedia.org/wiki/Dubbo
> >> > [2]
> http://dubbo.apache.org/en-us/docs/developers/contributor-guide/cla-signing-guide_dev.html
> >> > [3]
> http://dubbo.apache.org/en-us/docs/developers/contributor-guide/software-donation-guide_dev.html
> >> > [4]
> https://github.com/apache/incubator-dubbo/wiki/Apache-Dubbo-external-ecosystem-status
> >> >
> >> >
> >> >
> >> > --
> >> > Best Regards！
> >> > Huxing
> >>
> >>
> >>
> >> --
> >> Best Regards！
> >> Huxing
>
>
>
> --
> Best Regards！
> Huxing
>

Re: [DISCUSS] Migrating projects under dubbo group

[kimm king]

I will transfer jms-for-apache-dubbo rpc-xmlrpc-for-apache-dubbo
awesome-dubbo to ASF before the end of May.

Huxing Zhang  于2019年4月26日周五 下午4:01写道：

> 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
> > * metrics
> > * hessian-lite
> > * dubbo-sentinel-support
> > * awesome-dubbo
> > * dubbo-remoting-js
> > * egg-dubbo-rpc
> > * rpc-native-thrift-for-apache-dubbo
> > * intellij-idea-plugin
> > * initializr
> >
> >
> > If you are the project owner, could you please confirm that:
> >
> > 1) are you willing to transferred to ASF or not.
> > 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
> > - If the code belongs to your company, you need to sign the SGA[3]
> > - request ASF infra to transfer the project
> > 3) if not, please indicate that which group you will transfer to.
> >
> > 2. Gain write access to your project after transfer
> >
> > If your project has been transferred to ASF, you will lose write
> > access temporally. The Dubbo community will vote you in as committer
> > by following standard ASF way. This means you have to contribute to
> > the project for some time in order to earn enough merit.
> >
> > 3. After the transition is done, delete group A.
> >
> > The community will summarize and keep track of the status here[4].
> >
> >
> > [1] https://en.wikipedia.org/wiki/Dubbo
> > [2]
> http://dubbo.apache.org/en-us/docs/developers/contributor-guide/cla-signing-guide_dev.html
> > [3]
> http://dubbo.apache.org/en-us/docs/developers/contributor-guide/software-donation-guide_dev.html
> > [4]
> https://github.com/apache/incubator-dubbo/wiki/Apache-Dubbo-external-ecosystem-status
> >
> >
> >
> > --
> > Best Regards！
> > Huxing
>
>
>
> --
> Best Regards！
> Huxing
>

Re: Re: [Dubbo- support tag router feature] Add a new Router implement -- TagRouter

[Kimm King]

Ian& Wangxin & Kirito:

I  think we should consider that it's time to separate dubbo-cluster project 
into some subprojects such as loadbalance\router and so on after moving them to 
dubbo repo.



KimmKing(kimmk...@163.com)
 == In me the tiger sniffs the rose. ==

 
From: Ian Luo
Date: 2018-08-18 00:32
To: dev
Subject: Re: [Dubbo- support tag router feature] Add a new Router implement -- 
TagRouter
very nice feature the community keeps asking, I will look into it.
 
On Fri, Aug 17, 2018 at 2:45 PM 徐靖峰  wrote:
 
> this topic is related to
> https://github.com/apache/incubator-dubbo/pull/2228
>
> What is the purpose of the change
>
> Support tag router feature for dubbo.
>
> some pain points
>
>
>
> fact1: some applications changed at the same time in different branch,like
> A,B,C.
>
> fact2: some applications didn't change ,but deploy repeatedly，like D,E.
>
> fact3: if a new feature need to be tested, all 5 application need to be
> deployed.
>
> fact4: isolation by feature is not friendly to parallel development.
>
> use tag
>
>
>
> fact: changed applications are incremental deployment
>
> some cases
>
>
>
> usage
>
> consumer
> RpcContext.getContext().setAttachment("request.tag","red");
> i suggest you can use filter or SPI to set this attachment, notice that
> RpcContext is bound to Thread.
>
> provider
> @Bean public ApplicationConfig applicationConfig() {
>  ApplicationConfig applicationConfig = new ApplicationConfig();
>  applicationConfig.setName("provider-book"); // instruct tag
> router Map parameters = new HashMap<>();
>  parameters.put(Constants.ROUTER_KEY, "tag");
>  applicationConfig.setParameters(parameters); return
> applicationConfig; }
> Brief changelog
>
> add unit property for dubbo.xsd.
>
> add TagRouter,TagRouterFactory.
>
> add SPI statement for adding TagRouter automatically.
>
> fix a small bug(may be not) in
> org.apache.dubbo.registry.integration.RegistryDirectory#route，exclude
> runtime routers, avoid to filter some runtime invokers.
>
> Verifying this change
>
> Here is more detail about Unit Test:
> org.apache.dubbo.rpc.cluster.router.tag.TagRouterTest
> I have verified that the unit test has been correct and passed.
>
> Here is more detail about a Integration Test:
> clone the repository
> https://github.com/lexburner/Dubbo-Sample-TagRouter.git,can see the route
> tag feature.
>
> Follow this checklist to help us incorporate your contribution quickly and
> easily:
>
>  Make sure there is a GITHUB_issue filed for the change (usually before
> you start working on it). Trivial changes like typos do not require a
> GITHUB issue. Your pull request should address just this issue, without
> pulling in other changes - one PR resolves one issue.
>
>  Format the pull request title like [Dubbo-XXX] Fix UnknownException when
> host config not exist #XXX. Each commit in the pull request should have a
> meaningful subject line and body.
>
>  Write a pull request description that is detailed enough to understand
> what the pull request does, how, and why.
>
>  Write necessary unit-test to verify your logic correction, more mock a
> little better when cross module dependency exist. If the new feature or
> significant change is committed, please remember to add integration-test in
> test module.
>
>  Run mvn clean install -DskipTests & mvn clean test-compile
> failsafe:integration-test to make sure unit-test and integration-test pass.
>
>  If this contribution is large, please follow the Software Donation Guide.

Re: Re: 100 contributors for Dubbo

[Kimm King]

Nice



KimmKing(kimmk...@163.com)
 == In me the tiger sniffs the rose. ==

 
From: YunKun Huang
Date: 2018-08-01 20:03
To: dev@dubbo.apache.org
Subject: Re: 100 contributors for Dubbo
Good news :)
 
On 2018/08/01 11:11:50, 凝雨  wrote: 
> Great！
> 
> Yong Zhu  于2018年8月1日周三 下午4:44写道：
> 
> > 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
> > > >
> > >
> >
> 
> 
> -- 
> Keep Real！
> 

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

[Kimm King]

that's alright.
and I will add a target for across platforms, such as .net core on Windows and 
Mono on MacOS/Linux.



KimmKing(kimmk...@163.com)
 == In me the tiger sniffs the rose. ==

 
From: Yong Zhu
Date: 2018-07-18 14:07
To: dev
Subject: Re: [eco-system]create a new project to implement dotnet/c# dubbo 
library
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.
>
>
> : )
>
>

[Proposal]update thrift version from 0.8 to 0.11 to support native thrift protocol

[Kimm King]

Hi, community.

## Problems
 When I enhance rpc-thrift module test coverage this week, I found its 
thirft version is too old.
 Cause thrift-0.8.x is not support more than one service in a thrift 
server, dubbo create a MultiServiceProcessor to hold multiple Services，
 and add some custom binary bytes transported before thrift binary data in 
this dubbo-rpc-thrift module.

 So a native thrift client can't consume a 'thrift' service exported by 
dubbo-rpc-thrift.This module actually equals to a thrift-like serialization.
 Since thrift-0.9.1, the native thrift library was also supporting multiple 
services by a TMultiplexedProcessor, we can resolve this problem simply and 
directly.

## Target
Make a perfect and simple dubbo-rpc-thrift module  to support native thrift 
protocol

## Solution
Update thrift version to 0.11.0 and modify service mapping mechanism by 
replacing custom MultiServiceProcessor with formal TMultiplexedProcessor.



KimmKing(kimmk...@163.com)
 == In me the tiger sniffs the rose. ==

Re: Re: [Discuss] Blog topic collection

[Kimm King]

4、 docker



KimmKing(kimmk...@163.com)
 == In me the tiger sniffs the rose. ==

 
From: Ian Luo
Date: 2018-07-05 10:42
To: dev
Subject: Re: [Discuss] Blog topic collection
good idea, since website is now ready, any dubbo relevant article is
welcomed in blog category.
 
Thanks,
-Ian.
 
On Thu, Jul 5, 2018 at 10:34 AM Xin Wang  wrote:
 
> 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: Re: [VOTE]: Release Apache Dubbo (Incubating) 2.6.2 [RC2]

[Kimm King]

+1 vote



KimmKing(kimmk...@163.com)
 == In me the tiger sniffs the rose. ==

 
From: Mercy
Date: 2018-06-01 10:40
To: dev; Jun Liu
Subject: Re: [VOTE]: Release Apache Dubbo (Incubating) 2.6.2 [RC2]
+1,  the code and signature are both Ok.
 
 
Kind regards,
 
Mercy
 
 
在 2018/5/29 下午4:01, Jun Liu 写道:
> Dear Dubbo Community,
>
> I am pleased to announce that the dubbo community has approved the release of 
> 2.6.2 RC2.
>
> The vote has opened for 72+ hours and passed with:
> 3 binding "+1" votes, and 1 non-binding "+1" votes
> no "0" votes
> no "-1" votes
>
> The vote thread:
> https://lists.apache.org/thread.html/38560cb159a5c32d0cf98485c9fe791505fbc52d18d86a37713582f0@%3Cdev.dubbo.apache.org%3E
>
> +1, Huxing Zhang (binding)
> +1, Ian Luo (binding)
> +1, Jun Liu (binding)
>
> +1, Yong Zhu (non-binding)
>
> We'll continue to start the IPMC vote now.
>
> Thanks.
> Jun,
> on behalf of the Apache Dubbo (Incubating) Team
>
>> On 28 May 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: Re: About Keeping dubbo's version to be SNAPSHOT on master branch

[Kimm King]

+1



KimmKing(kimmk...@163.com)
 == In me the tiger sniffs the rose. ==

 
From: Yong Zhu
Date: 2018-04-25 17:48
To: dev
Subject: Re: About Keeping dubbo's version to be SNAPSHOT on master branch
+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: Where is the document for the restful configuration?

[Kimm King]

just like dubbox



KimmKing(kimmk...@163.com)
 == In me the tiger sniffs the rose. ==

 
 /mg
?? 2018-03-28 16:11
 dev
?? Where is the document for the restful configuration?
Hi, all 
 
 
Where is the document about the configuration of rest ? Could someone know 
about this?
 
 
thanks.
 
 
best regrads!
 
 
by Quan yiming

Re: Re: How to add Apache license head to the files of hessian-lite sub project

[Kimm King]

In my opion, it's better to keep author info for respect.
Just think sometimes other guys copy your codes.



KimmKing(kimmk...@163.com)
 == In me the tiger sniffs the rose. ==

 
发件人： Wang Xin
发送时间： 2018-03-13 22:02
收件人： dev@dubbo.apache.org
主题： Re: How to add Apache license head to the files of hessian-lite sub project
Should the author info be removed?  @author Scott Ferguson
 
Xin Wang
lovep...@hotmail.com<mailto:lovep...@hotmail.com>
 
 
 
在 2018年3月13日，下午7:50，Mark Thomas <ma...@apache.org<mailto:ma...@apache.org>> 写道：
 
On 13/03/18 06:03, Ian Luo wrote:
+1 to keep original license info since it’s Apache License 1.0.
 
Mentors, would you mind to guide us on this particular problem?
 
Leave the ALv1.1 headers (with the copyright) in place.
 
The text from section 3 should appear in the NOTICE file.
 
Mark
 
 
 
Thanks,
-Ian.
 
On 12 Mar 2018, at 7:02 PM, Kimm King 
<kimmk...@163.com<mailto:kimmk...@163.com>> wrote:
 
I think keeping the notice is awesome.
 
 
 
KimmKing(kimmk...@163.com<mailto:kimmk...@163.com>)
== In me the tiger sniffs the rose. ==
 
 
发件人： Wang Xin
发送时间： 2018-03-12 18:01
收件人： dev@dubbo.apache.org<mailto:dev@dubbo.apache.org>
主题： How to add Apache license head to the files of hessian-lite sub project
Hi,all
 Now I’m adding Apache license head to the Dubbo project.  I find that ,the 
hessian-lite sub project is totally  copied from hessian project 
(http://hessian.caucho.com/) , it’s package is modified and maintained here.
The hessian project complies with Apache license 1.1. The license head in each 
file is as the following:
What should I do with it?
 
/*
* Copyright (c) 2001-2004 Caucho Technology, Inc.  All rights reserved.
*
* The Apache Software License, Version 1.1
*
* Redistribution and use in source and binary forms, with or without
* modification, are permitted provided that the following conditions
* are met:
*
* 1. Redistributions of source code must retain the above copyright
*notice, this list of conditions and the following disclaimer.
*
* 2. Redistributions in binary form must reproduce the above copyright
*notice, this list of conditions and the following disclaimer in
*the documentation and/or other materials provided with the
*distribution.
*
* 3. The end-user documentation included with the redistribution, if
*any, must include the following acknowlegement:
*   "This product includes software developed by the
*Caucho Technology (http://www.caucho.com/)."
*Alternately, this acknowlegement may appear in the software itself,
*if and wherever such third-party acknowlegements normally appear.
*
* 4. The names "Burlap", "Resin", and "Caucho" must not be used to
*endorse or promote products derived from this software without prior
*written permission. For written permission, please contact
*i...@caucho.com<mailto:i...@caucho.com><mailto:i...@caucho.com>.
*
* 5. Products derived from this software may not be called "Resin"
*nor may "Resin" appear in their names without prior written
*permission of Caucho Technology.
*
* THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESSED OR IMPLIED
* WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
* OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
* DISCLAIMED.  IN NO EVENT SHALL CAUCHO TECHNOLOGY OR ITS CONTRIBUTORS
* BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY,
* OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT
* OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR
* BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
* WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE
* OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN
* IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
*
* @author Scott Ferguson
*/
 
 
Xin Wang
lovep...@hotmail.com<mailto:lovep...@hotmail.com><mailto:lovep...@hotmail.com>
 
 
 
 
 
 

Re: How to add Apache license head to the files of hessian-lite sub project

[Kimm King]

I think keeping the notice is awesome.



KimmKing(kimmk...@163.com)
 == In me the tiger sniffs the rose. ==

 
发件人： Wang Xin
发送时间： 2018-03-12 18:01
收件人： dev@dubbo.apache.org
主题： How to add Apache license head to the files of hessian-lite sub project
Hi,all
   Now I’m adding Apache license head to the Dubbo project.  I find that 
,the hessian-lite sub project is totally  copied from hessian project 
(http://hessian.caucho.com/) , it’s package is modified and maintained here.
   The hessian project complies with Apache license 1.1. The license head in 
each file is as the following:
  What should I do with it?
 
/*
* Copyright (c) 2001-2004 Caucho Technology, Inc.  All rights reserved.
*
* The Apache Software License, Version 1.1
*
* Redistribution and use in source and binary forms, with or without
* modification, are permitted provided that the following conditions
* are met:
*
* 1. Redistributions of source code must retain the above copyright
*notice, this list of conditions and the following disclaimer.
*
* 2. Redistributions in binary form must reproduce the above copyright
*notice, this list of conditions and the following disclaimer in
*the documentation and/or other materials provided with the
*distribution.
*
* 3. The end-user documentation included with the redistribution, if
*any, must include the following acknowlegement:
*   "This product includes software developed by the
*Caucho Technology (http://www.caucho.com/)."
*Alternately, this acknowlegement may appear in the software itself,
*if and wherever such third-party acknowlegements normally appear.
*
* 4. The names "Burlap", "Resin", and "Caucho" must not be used to
*endorse or promote products derived from this software without prior
*written permission. For written permission, please contact
*i...@caucho.com.
*
* 5. Products derived from this software may not be called "Resin"
*nor may "Resin" appear in their names without prior written
*permission of Caucho Technology.
*
* THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESSED OR IMPLIED
* WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
* OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
* DISCLAIMED.  IN NO EVENT SHALL CAUCHO TECHNOLOGY OR ITS CONTRIBUTORS
* BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY,
* OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT
* OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR
* BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
* WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE
* OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN
* IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
*
* @author Scott Ferguson
*/
 
 
Xin Wang
lovep...@hotmail.com
 
 
 

Dubbo dev-list Mail Page

[Kimm King]

hi, everyone,
As Mark's suggestion:,
Mail page you may be better off using the one hosted at Apache rather than 
markmail.
We can view all mail posts here: 
https://lists.apache.org/list.html?dev@dubbo.apache.org



KimmKing(kimmk...@163.com)
 == In me the tiger sniffs the rose. ==

Re: Re: On double dubbo starters

[Kimm King]

I think mentor means in another thread:
 we could publish something to maven central repository as usual until 
transition is done.



KimmKing(kimmk...@163.com)
 == In me the tiger sniffs the rose. ==

 
From: Ian Luo
Date: 2018-03-08 21:40
To: dev
Subject: Re: On double dubbo starters
 
> On 8 Mar 2018, at 9:22 PM, Ian Luo  wrote:
> 
> Sure, then we will not publish anything to maven repository until transition 
> is done.
> 
 
Oops, I think I misunderstood. Mark, could you pls. confirm we could still 
publish release from the “old” repositories during the transition?
 
Thanks,
-Ian.
 
 
> Adrian, I guess this decision shouldn’t stop your further development work 
> since you could depend on the snapshot build anyway. We will try our best to 
> work with Mark and other apache mentors to boost the transition as fast as 
> possible.
> 
> Thanks,
> -Ian.
> 
> 
> 
>> On 8 Mar 2018, at 5:40 PM, Mark Thomas  wrote:
>> 
>> On 07/03/18 11:41, Ian Luo wrote:
>>> Hi Mark,
>>> 
>>> Pls. check my comments below.
>> 
>> Thanks for the additional information.
>> 
>> Until the code transitions to the ASF (which I hope is fairly soon), and
>> especially if the community needs a release, then you are able to
>> publish releases as you have done previously.
>> 
>> Once the code transitions to the ASF, the ASF release policy applies.
>> Depending on where you start from, it can take a little work to get
>> everything aligned to the policy but that only needs to be done once.
>> 
>> Mark
>> 
>> 
>>> 
>>> Thanks,
>>> -Ian.
>>> 
>>> 
 On 7 Mar 2018, at 6:09 PM, Mark Thomas  wrote:
 
 On 07/03/18 09:49, Ian Luo wrote:
> Hi Adrian,
> 
> First of all, my apology for the confusion. The project under dubbo [1] 
> group is the official project we plan to maintain in long term for Spring 
> Boot support. I encourage you try it first and share your feedback if 
> there’s any. 
> 
> In order to not block Adrian’s work, I suggest to publish it with the 
> existing groupId/artifactId since we can always republish with the new 
> groupId/artifactId in the next release cycle after the transition 
> finishes.
> 
> To dubbo’s mentors, I am not sure if it is appropriated for my proposal. 
> Pls. correct me once you read the message since we plan to release 
> spring-boot-starter officially very soon (by the end of this week or the 
> early of the next week).
> 
> Thanks,
> -Ian. 
> 
> 1.  https://github.com/dubbo/dubbo-spring-boot-project 
 
 Hi,
 
 I need a little more information before offering an opinion.
 
 1. Who is the "we" that intends to publish the release?
>>> 
>>> [iluo]: Here “we” means dubbo development team. 
>>> 
 
 2. How will the release be named (including Maven co-ordinates)?
>>> 
>>> [iluo]: It will be com.alibaba.boot:dubbo-spring-boot-starter at this 
>>> moment. 
>>> 
 
 3. Is it intended that this code will become part of Apache Dubbo? If
 so, what stage is this code at in its transition to the ASF?
>>> 
>>> [iluo]: It’s a side project [1] of Apache Dubbo. All projects under dubbo 
>>> group [2] will be included in this transition, you could check details from 
>>> JIRA issue DUBBO-3 [3].
>>> 
>>> 
>>> 1. https://github.com/dubbo/dubbo-spring-boot-project
>>> 2. https://github.com/dubbo
>>> 3. https://issues.apache.org/jira/projects/DUBBO/issues/DUBBO-3
>>> 
 
 Thanks,
 
 Mark
 
 
> 
> 
>> On 7 Mar 2018, at 5:04 PM, Adrian Cole  wrote:
>> 
>> Hi, all
>> 
>> I'm working on spring-cloud-sleuth tracing integration with dubbo.
>> We've had users requesting dubbo for a while now for spring boot
>> applications.
>> 
>> https://github.com/spring-cloud/spring-cloud-sleuth/issues/710
>> 
>> One of the commitments we made was to have dubbo tracing included for
>> spring boot 2 applications, leveraging the efforts we made in the
>> Zipkin library Brave (which similarly had a backlog of dubbo
>> interest).
>> 
>> The good news is that, I've been able to get this working, which is 
>> awesome.
>> 
>> https://github.com/openzipkin/sleuth-webmvc-example/compare/add-dubbo-tracing
>> 
>> I'm only waiting a couple small patches and we are ready to go! The
>> community have been great and the plugin changes quickly in the right
>> direction.
>> 
>> I ran into a glitch as I was told that the plugin I use, the "alibaba"
>> variant, is not official. Rather, the "dubbo" one was.
>> 
>> https://github.com/alibaba/dubbo-spring-boot-starter < I am using this
>> and it works
>> https://github.com/dubbo/dubbo-spring-boot-project < haven't tried this, 
>> yet
>> 
>> I would like to try the other version, but it seems to be in release
>> limbo. For example, it is