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

[Huxing Zhang]

Hi,

This looks like a blocking issue, I've already tagged 2.7.0, I will
wait for it and re-do the tagging.

On Thu, Jan 17, 2019 at 2:49 PM jun liu  wrote:
>
> > I am seeing that all the issue has been cleaned for the 2.7.0 milestone.
> > It looks like all the things have been settled, I am planning to tag
> > the 2.7.0 release today.
>
> One more issue to be solved before vote.
> Thanks to the suggestions from the Apollo[1] community, I submitted a PR[2] 
> to polish the Apollo extension. Please help to review.
>
> 1. https://github.com/ctripcorp/apollo
> 2. https://github.com/apache/incubator-dubbo/pull/3263
>
> Jun
>
> > On Jan 17, 2019, at 10:41 AM, Huxing Zhang  wrote:
> >
> > Hi All,
> >
> > I am seeing that all the issue has been cleaned for the 2.7.0 milestone.
> > It looks like all the things have been settled, I am planning to tag
> > the 2.7.0 release today.
> >
> > dubbo-ops and dubbo-spring-boot-project should be released after Dubbo
> > 2.7.0 release.
> >
> > On Wed, Jan 16, 2019 at 5:02 PM jun liu  > > wrote:
> >>
> >>> There is no need to shade gson into dubbo.jar, just need depency gson
> >>> library.
> >>>
> >>> I have fixed it . https://github.com/apache/incubator-dubbo/pull/3246 
> >>>  
> >>>  >>> >
> >> Agree.
> >>
> >> Well done,  merged.
> >>
> >> Jun
> >>
> >>> On Jan 16, 2019, at 4:15 PM, victory  wrote:
> >>>
> >>> There is no need to shade gson into dubbo.jar, just need depency gson
> >>> library.
> >>>
> >>> I have fixed it . https://github.com/apache/incubator-dubbo/pull/3246
> >>>
> >>> Ian Luo  于2019年1月16日周三 下午2:34写道：
> >>>
>  We should not shade gson binaries into dubbo all in one jar file, even
>  though there's no license issue. It is simply we should not do this,
>  instead, we should make sure dubbo all in one jar should have a 
>  transitive
>  dependency to gson library.
> 
>  I noticed it's caused by'com.google.code.gson:gson' in
>  dubbo-all/pom.xml. We should fix it.
> 
>  Thanks,
>  -Ian.
> 
> 
>  On Tue, Jan 15, 2019 at 5:16 PM jun liu  wrote:
> 
> > I noticed that a third-party source code ‘com.google  > .gson.*’
> > has been compiled into the convenient maven binary jar of 2.7.0 -
> > dubbo-2.7.0.jar :
> >
> > .
> > ├── META-INF
> > │   ├── DEPENDENCIES
> > │   ├── LICENSE
> > │   ├── MANIFEST.MF
> > │   ├── NOTICE
> > │   ├── assembly
> > │   │   └── bin
> > │   ├── compat
> > │   │   └── dubbo.xsd
> > │   ├── dubbo
> > │   │   └── internal
> > │   ├── dubbo.xsd
> > │   ├── maven
> > │   │   ├── com.alibaba
> > │   │   ├── com.google.code.gson
> > │   │   └── org.apache.dubbo
> > │   ├── spring.handlers
> > │   └── spring.schemas
> > ├── com
> > │   ├── alibaba
> > │   │   ├── com
> > │   │   └── dubbo
> > │   └── google
> > │   └── gson
> > └── org
> >   └── apache
> >   └── dubbo
> >
> >
> > Since this binary jar (dubbo-2.7.0.jar) will be included in the Apache
> > Binary Release, should we update the LICENSE or NOTICE file in the 
> > Binary
> > Release to announce the existence of these binary files?
> >
> > BTW, ‘com.google .gson’ is declared to be unde
>  Apache
> > License 2.0.
> >
> > You can directly download the latest SNAPSHOT release of 2.7.0-SNAPSHOT
>  in
> > here[1] and unzip and check the contents to better understand what I am
> > trying to describe here.
> >
> > 1.
> >
>  https://repository.apache.org/content/repositories/snapshots/org/apache/dubbo/dubbo/2.7.0-SNAPSHOT/
> >
> > Jun
> >
> >> On Jan 13, 2019, at 5:58 PM, Huxing Zhang  wrote:
> >>
> >> Hi Jun,
> >>
> >> Could you summarize the current status of the 2.7-release branch?
> >> I see there are still several enhancement on this branch.
> >>
> >> As this is the first time to prepare for a release for me, I am trying
> >> to walk through the release steps[1].
> >> I might try to deploy snapshot to maven repository.
> >>
> >> Once we feel it is ready to do the release, I will start the formal
> >> release process.
> >>
> >>
> >> [1] http://dubbo.apache.org/en-us/blog/prepare-an-apache-release.html
> >>
> >>
> >> --
> >> Best Regards！
> >> Huxing
> >>
> >> On Mon, Jan 7, 2019 at 1:48 PM jun liu  wrote:
> >>>
> >
> > Nice work!
> >
> > I think we should let the community to participate more in the
>  release
> > process, for example,
> > 1. check out a release branch called 2.7.0-release
> > 2. encourage people to check it 

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

[jun liu]

> I am seeing that all the issue has been cleaned for the 2.7.0 milestone.
> It looks like all the things have been settled, I am planning to tag
> the 2.7.0 release today.

One more issue to be solved before vote. 
Thanks to the suggestions from the Apollo[1] community, I submitted a PR[2] to 
polish the Apollo extension. Please help to review.

1. https://github.com/ctripcorp/apollo
2. https://github.com/apache/incubator-dubbo/pull/3263

Jun

> On Jan 17, 2019, at 10:41 AM, Huxing Zhang  wrote:
> 
> Hi All,
> 
> I am seeing that all the issue has been cleaned for the 2.7.0 milestone.
> It looks like all the things have been settled, I am planning to tag
> the 2.7.0 release today.
> 
> dubbo-ops and dubbo-spring-boot-project should be released after Dubbo
> 2.7.0 release.
> 
> On Wed, Jan 16, 2019 at 5:02 PM jun liu  > wrote:
>> 
>>> There is no need to shade gson into dubbo.jar, just need depency gson
>>> library.
>>> 
>>> I have fixed it . https://github.com/apache/incubator-dubbo/pull/3246 
>>>  
>>> >> >
>> Agree.
>> 
>> Well done,  merged.
>> 
>> Jun
>> 
>>> On Jan 16, 2019, at 4:15 PM, victory  wrote:
>>> 
>>> There is no need to shade gson into dubbo.jar, just need depency gson
>>> library.
>>> 
>>> I have fixed it . https://github.com/apache/incubator-dubbo/pull/3246
>>> 
>>> Ian Luo  于2019年1月16日周三 下午2:34写道：
>>> 
 We should not shade gson binaries into dubbo all in one jar file, even
 though there's no license issue. It is simply we should not do this,
 instead, we should make sure dubbo all in one jar should have a transitive
 dependency to gson library.
 
 I noticed it's caused by'com.google.code.gson:gson' in
 dubbo-all/pom.xml. We should fix it.
 
 Thanks,
 -Ian.
 
 
 On Tue, Jan 15, 2019 at 5:16 PM jun liu  wrote:
 
> I noticed that a third-party source code ‘com.google  .gson.*’
> has been compiled into the convenient maven binary jar of 2.7.0 -
> dubbo-2.7.0.jar :
> 
> .
> ├── META-INF
> │   ├── DEPENDENCIES
> │   ├── LICENSE
> │   ├── MANIFEST.MF
> │   ├── NOTICE
> │   ├── assembly
> │   │   └── bin
> │   ├── compat
> │   │   └── dubbo.xsd
> │   ├── dubbo
> │   │   └── internal
> │   ├── dubbo.xsd
> │   ├── maven
> │   │   ├── com.alibaba
> │   │   ├── com.google.code.gson
> │   │   └── org.apache.dubbo
> │   ├── spring.handlers
> │   └── spring.schemas
> ├── com
> │   ├── alibaba
> │   │   ├── com
> │   │   └── dubbo
> │   └── google
> │   └── gson
> └── org
>   └── apache
>   └── dubbo
> 
> 
> Since this binary jar (dubbo-2.7.0.jar) will be included in the Apache
> Binary Release, should we update the LICENSE or NOTICE file in the Binary
> Release to announce the existence of these binary files?
> 
> BTW, ‘com.google .gson’ is declared to be unde
 Apache
> License 2.0.
> 
> You can directly download the latest SNAPSHOT release of 2.7.0-SNAPSHOT
 in
> here[1] and unzip and check the contents to better understand what I am
> trying to describe here.
> 
> 1.
> 
 https://repository.apache.org/content/repositories/snapshots/org/apache/dubbo/dubbo/2.7.0-SNAPSHOT/
> 
> Jun
> 
>> On Jan 13, 2019, at 5:58 PM, Huxing Zhang  wrote:
>> 
>> Hi Jun,
>> 
>> Could you summarize the current status of the 2.7-release branch?
>> I see there are still several enhancement on this branch.
>> 
>> As this is the first time to prepare for a release for me, I am trying
>> to walk through the release steps[1].
>> I might try to deploy snapshot to maven repository.
>> 
>> Once we feel it is ready to do the release, I will start the formal
>> release process.
>> 
>> 
>> [1] http://dubbo.apache.org/en-us/blog/prepare-an-apache-release.html
>> 
>> 
>> --
>> Best Regards！
>> Huxing
>> 
>> On Mon, Jan 7, 2019 at 1:48 PM jun liu  wrote:
>>> 
> 
> Nice work!
> 
> I think we should let the community to participate more in the
 release
> process, for example,
> 1. check out a release branch called 2.7.0-release
> 2. encourage people to check it out, test it and report if there is
> any regressions, bugs or issues.
> 3. while we are doing the test, we can start going through the ASF
> release process locally, once we think it is ready to start a formal
> release note, it can be done very quickly.
> 
> By the way, we need decide the release manager of 2.7.0 release. Is
> there anyone who volunteer to do that?

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

[Ian Luo]

Hi Yuneng,

Sounds interesting. I am especially interested in reactive programming
support. Pls. go ahead to try implement it on 3.x branch.

Thanks,
-Ian.

On Thu, Jan 17, 2019 at 11:03 AM yuneng xie  wrote:

> Hi folks,
>
> I agreed with Ian Luo on the improvement list. I also got some idea in my
> mind.  I'd just share with you two points below in detail which i'm most
> interested in right now.
>
> 1. Upgrade  the core abstraction "Invoker", which works in sync mode, to an
> abstraction works in async mode. then we can construct
> InvocationChain/FilterChain that works in async mode.  A core abstraction
> works in async mode would simplify the sync/async logic. We  no longer need
> to repeat the logic about sync-mode/async-mode in each ProtocolInvoker.
> ProtocolInvoker could concentrate on async logic and we could handle
> sync-mode invoke all in once by wrapping the AsyncInvocationChain into a
> SyncInvocationChain.
>
> 2. Support using stream-value (Fowable, Flux...)  as param/returnType.
> really a nice feature.
>
> Please let me known your opinion on my points. I'm also glad to just give
> it a try and raise a pr.
>
>
>
> Ian Luo  于2019年1月10日周四 下午6:00写道：
>
> > Hi folks,
> >
> > Finally we managed to ramp down version 2.7.0 development, and hopefully
> we
> > can start the vote in the early of the next week. But the main purpose of
> > this email is not a release announcement. Instead, since we now have
> > bandwidth, let's consider and discuss what we should focus out from many
> > stuff we want to do. For example, we may focus more on issue and pull
> > request on GitHub, or we may plan 2.7 minor releases immediately after we
> > release 2.7.0. But today I'd like to bring up one longer term plan which
> > I'm now caring most, that is, how we define what version 3.0 is? and when
> > can we get start on it? In my opinion, we need to start it right from
> this
> > moment.
> >
> > I recalled Liujie Qin (@liujieqin) initialed the discussion on the same
> > topic [1] in July this year. I summarize his points here if you are too
> > impatient to read through the contents of his email :p:
> >
> > 1. Need to enhance the current extension mechanism
> > 2. Need to enhance the code base for better maintenance
> > 3. Need to support async
> > 4. Need to decouple registry server and config server
> > 5. Need to support Java8 and above so that we can use advanced features
> in
> > Dubbo's core
> >
> > I agree with most of his points in this good proposal.
> >
> > Here I'd like to initial a discussion on how we define Dubbo 3.0, or in
> the
> > other word, how do the community expect from Dubbo 3.0. In my opinion, I
> > think we need to answer the following questions in this major release:
> >
> > - Today the boundary between messaging and remoting call gets blur. We
> may
> > need to consider to support streaming at the protocol level.
> > - Reative programming and its fundamental FP start to get adopted. We
> > should consider to support it.
> > - Dubbo should be redesigned to support async better, and treats async as
> > the first class citizen. We do support async feature in 2.7.0 release but
> > it is not so perfect.
> > - Micro-services has been widely adopted. How Dubbo works seamlessly with
> > micro-services becomes a question mark. We need to look into the inter-op
> > between Dubbo and micro-services's registry server/config server. The
> > support on separating registry server and config server in 2.7.0 release
> is
> > a good start, but there are still lots of further works remaining with no
> > doubt.
> > - Once we conquer seamless micro-services support, we still need to take
> > one step further to think about K8S integration. After all, K8S and
> service
> > mesh built above it are now considered the best way for micro-services
> > deployment.
> > - How we define mini-dubbo, or phrase in another way, what the minimal
> > feature set we should define for Dubbo framework. The reason behind this
> > is, it is very helpful for developing more language supports from the
> > community. This also means, we need to modularize Dubbo further, to make
> it
> > a reference implementation for other languages.
> >
> > In short, I suggest we need to focus on streaming protocol, Rx/FP, native
> > async, micro-services support, refactor/modularize areas. Of course,
> there
> > are more I don't mention in this email, for examples: how we make Dubbo
> > more resilient? how we support HTTP/2? and more.
> >
> > Pls. let me know your opinion on what I and Liujie proposed, and share
> your
> > thought on what kind of features really matter to you.
> >
> > Thanks,
> > -Ian.
> >
> >
> > 1. Proposal for Dubbo 3.0 from liujie...@apache.org on
> > dev@dubbo.apache.org
> >
>

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

[yuneng xie]

Hi folks,

I agreed with Ian Luo on the improvement list. I also got some idea in my
mind.  I'd just share with you two points below in detail which i'm most
interested in right now.

1. Upgrade  the core abstraction "Invoker", which works in sync mode, to an
abstraction works in async mode. then we can construct
InvocationChain/FilterChain that works in async mode.  A core abstraction
works in async mode would simplify the sync/async logic. We  no longer need
to repeat the logic about sync-mode/async-mode in each ProtocolInvoker.
ProtocolInvoker could concentrate on async logic and we could handle
sync-mode invoke all in once by wrapping the AsyncInvocationChain into a
SyncInvocationChain.

2. Support using stream-value (Fowable, Flux...)  as param/returnType.
really a nice feature.

Please let me known your opinion on my points. I'm also glad to just give
it a try and raise a pr.



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

> Hi folks,
>
> Finally we managed to ramp down version 2.7.0 development, and hopefully we
> can start the vote in the early of the next week. But the main purpose of
> this email is not a release announcement. Instead, since we now have
> bandwidth, let's consider and discuss what we should focus out from many
> stuff we want to do. For example, we may focus more on issue and pull
> request on GitHub, or we may plan 2.7 minor releases immediately after we
> release 2.7.0. But today I'd like to bring up one longer term plan which
> I'm now caring most, that is, how we define what version 3.0 is? and when
> can we get start on it? In my opinion, we need to start it right from this
> moment.
>
> I recalled Liujie Qin (@liujieqin) initialed the discussion on the same
> topic [1] in July this year. I summarize his points here if you are too
> impatient to read through the contents of his email :p:
>
> 1. Need to enhance the current extension mechanism
> 2. Need to enhance the code base for better maintenance
> 3. Need to support async
> 4. Need to decouple registry server and config server
> 5. Need to support Java8 and above so that we can use advanced features in
> Dubbo's core
>
> I agree with most of his points in this good proposal.
>
> Here I'd like to initial a discussion on how we define Dubbo 3.0, or in the
> other word, how do the community expect from Dubbo 3.0. In my opinion, I
> think we need to answer the following questions in this major release:
>
> - Today the boundary between messaging and remoting call gets blur. We may
> need to consider to support streaming at the protocol level.
> - Reative programming and its fundamental FP start to get adopted. We
> should consider to support it.
> - Dubbo should be redesigned to support async better, and treats async as
> the first class citizen. We do support async feature in 2.7.0 release but
> it is not so perfect.
> - Micro-services has been widely adopted. How Dubbo works seamlessly with
> micro-services becomes a question mark. We need to look into the inter-op
> between Dubbo and micro-services's registry server/config server. The
> support on separating registry server and config server in 2.7.0 release is
> a good start, but there are still lots of further works remaining with no
> doubt.
> - Once we conquer seamless micro-services support, we still need to take
> one step further to think about K8S integration. After all, K8S and service
> mesh built above it are now considered the best way for micro-services
> deployment.
> - How we define mini-dubbo, or phrase in another way, what the minimal
> feature set we should define for Dubbo framework. The reason behind this
> is, it is very helpful for developing more language supports from the
> community. This also means, we need to modularize Dubbo further, to make it
> a reference implementation for other languages.
>
> In short, I suggest we need to focus on streaming protocol, Rx/FP, native
> async, micro-services support, refactor/modularize areas. Of course, there
> are more I don't mention in this email, for examples: how we make Dubbo
> more resilient? how we support HTTP/2? and more.
>
> Pls. let me know your opinion on what I and Liujie proposed, and share your
> thought on what kind of features really matter to you.
>
> Thanks,
> -Ian.
>
>
> 1. Proposal for Dubbo 3.0 from liujie...@apache.org on
> dev@dubbo.apache.org
>

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

[yuhang xiu]

awesome.
Looking forward to dubbo 2.7.
I just looked at the milestones of 2.7. It looks like there is no problem.


Huxing Zhang  于2019年1月17日周四 上午10:42写道：

> Hi All,
>
> I am seeing that all the issue has been cleaned for the 2.7.0 milestone.
> It looks like all the things have been settled, I am planning to tag
> the 2.7.0 release today.
>
> dubbo-ops and dubbo-spring-boot-project should be released after Dubbo
> 2.7.0 release.
>
> On Wed, Jan 16, 2019 at 5:02 PM jun liu  wrote:
> >
> > > There is no need to shade gson into dubbo.jar, just need depency gson
> > > library.
> > >
> > > I have fixed it . https://github.com/apache/incubator-dubbo/pull/3246
> 
> > Agree.
> >
> > Well done,  merged.
> >
> > Jun
> >
> > > On Jan 16, 2019, at 4:15 PM, victory  wrote:
> > >
> > > There is no need to shade gson into dubbo.jar, just need depency gson
> > > library.
> > >
> > > I have fixed it . https://github.com/apache/incubator-dubbo/pull/3246
> > >
> > > Ian Luo  于2019年1月16日周三 下午2:34写道：
> > >
> > >> We should not shade gson binaries into dubbo all in one jar file, even
> > >> though there's no license issue. It is simply we should not do this,
> > >> instead, we should make sure dubbo all in one jar should have a
> transitive
> > >> dependency to gson library.
> > >>
> > >> I noticed it's caused
> by'com.google.code.gson:gson' in
> > >> dubbo-all/pom.xml. We should fix it.
> > >>
> > >> Thanks,
> > >> -Ian.
> > >>
> > >>
> > >> On Tue, Jan 15, 2019 at 5:16 PM jun liu  wrote:
> > >>
> > >>> I noticed that a third-party source code ‘com.google <
> http://com.google/
> > >>> .gson.*’
> > >>> has been compiled into the convenient maven binary jar of 2.7.0 -
> > >>> dubbo-2.7.0.jar :
> > >>>
> > >>> .
> > >>> ├── META-INF
> > >>> │   ├── DEPENDENCIES
> > >>> │   ├── LICENSE
> > >>> │   ├── MANIFEST.MF
> > >>> │   ├── NOTICE
> > >>> │   ├── assembly
> > >>> │   │   └── bin
> > >>> │   ├── compat
> > >>> │   │   └── dubbo.xsd
> > >>> │   ├── dubbo
> > >>> │   │   └── internal
> > >>> │   ├── dubbo.xsd
> > >>> │   ├── maven
> > >>> │   │   ├── com.alibaba
> > >>> │   │   ├── com.google.code.gson
> > >>> │   │   └── org.apache.dubbo
> > >>> │   ├── spring.handlers
> > >>> │   └── spring.schemas
> > >>> ├── com
> > >>> │   ├── alibaba
> > >>> │   │   ├── com
> > >>> │   │   └── dubbo
> > >>> │   └── google
> > >>> │   └── gson
> > >>> └── org
> > >>>└── apache
> > >>>└── dubbo
> > >>>
> > >>>
> > >>> Since this binary jar (dubbo-2.7.0.jar) will be included in the
> Apache
> > >>> Binary Release, should we update the LICENSE or NOTICE file in the
> Binary
> > >>> Release to announce the existence of these binary files?
> > >>>
> > >>> BTW, ‘com.google .gson’ is declared to be unde
> > >> Apache
> > >>> License 2.0.
> > >>>
> > >>> You can directly download the latest SNAPSHOT release of
> 2.7.0-SNAPSHOT
> > >> in
> > >>> here[1] and unzip and check the contents to better understand what I
> am
> > >>> trying to describe here.
> > >>>
> > >>> 1.
> > >>>
> > >>
> https://repository.apache.org/content/repositories/snapshots/org/apache/dubbo/dubbo/2.7.0-SNAPSHOT/
> > >>>
> > >>> Jun
> > >>>
> >  On Jan 13, 2019, at 5:58 PM, Huxing Zhang 
> wrote:
> > 
> >  Hi Jun,
> > 
> >  Could you summarize the current status of the 2.7-release branch?
> >  I see there are still several enhancement on this branch.
> > 
> >  As this is the first time to prepare for a release for me, I am
> trying
> >  to walk through the release steps[1].
> >  I might try to deploy snapshot to maven repository.
> > 
> >  Once we feel it is ready to do the release, I will start the formal
> >  release process.
> > 
> > 
> >  [1]
> http://dubbo.apache.org/en-us/blog/prepare-an-apache-release.html
> > 
> > 
> >  --
> >  Best Regards！
> >  Huxing
> > 
> >  On Mon, Jan 7, 2019 at 1:48 PM jun liu  wrote:
> > >
> > >>>
> > >>> Nice work!
> > >>>
> > >>> I think we should let the community to participate more in the
> > >> release
> > >>> process, for example,
> > >>> 1. check out a release branch called 2.7.0-release
> > >>> 2. encourage people to check it out, test it and report if there
> is
> > >>> any regressions, bugs or issues.
> > >>> 3. while we are doing the test, we can start going through the
> ASF
> > >>> release process locally, once we think it is ready to start a
> formal
> > >>> release note, it can be done very quickly.
> > >>>
> > >>> By the way, we need decide the release manager of 2.7.0 release.
> Is
> > >>> there anyone who volunteer to do that?
> > >
> > > Sorry, I missed this mail.
> > > * 2.7.0-release has been created
> > > * we've froze the codebase, test is underway.
> > >
> > >> I'd like to be the release manager if no one is claiming it.
> > >
> > > Great, I can 

Re: Propose to add [End User Discussion] in Dubbo Guangzhou Meetup

[chenwei qi]

Hi,

I've already collect the register information, which will be sent to
priv...@dubbo.apache.org.

> BTW, would you please help to translate the registration form into
English?
Nice idea! I will translate it today.

Best,
Baike

Huxing Zhang  于2019年1月15日周二 下午3:44写道：

> Hi,
>
> Looks good to me, please send the registration data to
> priv...@dubbo.apache.org when the window is closed.
> BTW, would you please help to translate the registration form into English?
>
> On Tue, Jan 15, 2019 at 2:55 PM chenwei qi  wrote:
> >
> > Hi,
> >
> > The meetup has already had some register information and is still opening
> > to register. As the invitation needs 1-2 days, I suggest to collect the
> > register information till Jan.16(23:59 UTC+8), sending the register list
> to
> > PPMC members. And PPMC members decide the invitation list through
> > discussion.
> >
> > From the information provided by user registration[1], the following
> > information may help to select out the invitation list:
> > a) Contributor / users or not
> > b) Duration of using Apache Dubbo
> > c) The average daily invocation request of Apache Dubbo™
> >
> > [1] http://www.huodongxing.com/event/8472393517111
>
>
>
> >
> > Yours,
> > Baike
> >
> > Ian Luo  于2019年1月15日周二 上午11:36写道：
> >
> > > I like the this idea. In my opinion, the speaks in front of large
> group of
> > > audiences help Dubbo users to learn, on the other hand, we ourselves
> can
> > > learn a lots from a round table discussion among experienced users.
> > >
> > > We should include both activities in future's meetup. BTW, have we had
> a
> > > candidate list to invite?
> > >
> > > Thanks,
> > > -Ian.
> > >
> > > On Mon, Jan 14, 2019 at 2:37 PM chenwei qi 
> wrote:
> > >
> > > > Hi guys,
> > > >
> > > >
> > > > Normally there will be about 200-300 attendees at Dubbo Meetup.
> Despite
> > > the
> > > > fact that we have Q during each session, we have very limited
> two-way
> > > > communication between the attendees and the Dubbo Community.
> > > >
> > > >
> > > > Do you think we can have an [End User Discussion] at Guangzhou
> Meetup, so
> > > > we can have deeper communication and get more feedback from Dubbo
> users?
> > > >
> > > >
> > > > Yours,
> > > >
> > > > Baike
> > > >
> > >
>
>
>
> --
> Best Regards！
> Huxing
>

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

[jun liu]

> There is no need to shade gson into dubbo.jar, just need depency gson
> library.
> 
> I have fixed it . https://github.com/apache/incubator-dubbo/pull/3246 
> 
Agree.

Well done,  merged.

Jun

> On Jan 16, 2019, at 4:15 PM, victory  wrote:
> 
> There is no need to shade gson into dubbo.jar, just need depency gson
> library.
> 
> I have fixed it . https://github.com/apache/incubator-dubbo/pull/3246
> 
> Ian Luo  于2019年1月16日周三 下午2:34写道：
> 
>> We should not shade gson binaries into dubbo all in one jar file, even
>> though there's no license issue. It is simply we should not do this,
>> instead, we should make sure dubbo all in one jar should have a transitive
>> dependency to gson library.
>> 
>> I noticed it's caused by'com.google.code.gson:gson' in
>> dubbo-all/pom.xml. We should fix it.
>> 
>> Thanks,
>> -Ian.
>> 
>> 
>> On Tue, Jan 15, 2019 at 5:16 PM jun liu  wrote:
>> 
>>> I noticed that a third-party source code ‘com.google >> .gson.*’
>>> has been compiled into the convenient maven binary jar of 2.7.0 -
>>> dubbo-2.7.0.jar :
>>> 
>>> .
>>> ├── META-INF
>>> │   ├── DEPENDENCIES
>>> │   ├── LICENSE
>>> │   ├── MANIFEST.MF
>>> │   ├── NOTICE
>>> │   ├── assembly
>>> │   │   └── bin
>>> │   ├── compat
>>> │   │   └── dubbo.xsd
>>> │   ├── dubbo
>>> │   │   └── internal
>>> │   ├── dubbo.xsd
>>> │   ├── maven
>>> │   │   ├── com.alibaba
>>> │   │   ├── com.google.code.gson
>>> │   │   └── org.apache.dubbo
>>> │   ├── spring.handlers
>>> │   └── spring.schemas
>>> ├── com
>>> │   ├── alibaba
>>> │   │   ├── com
>>> │   │   └── dubbo
>>> │   └── google
>>> │   └── gson
>>> └── org
>>>└── apache
>>>└── dubbo
>>> 
>>> 
>>> Since this binary jar (dubbo-2.7.0.jar) will be included in the Apache
>>> Binary Release, should we update the LICENSE or NOTICE file in the Binary
>>> Release to announce the existence of these binary files?
>>> 
>>> BTW, ‘com.google .gson’ is declared to be unde
>> Apache
>>> License 2.0.
>>> 
>>> You can directly download the latest SNAPSHOT release of 2.7.0-SNAPSHOT
>> in
>>> here[1] and unzip and check the contents to better understand what I am
>>> trying to describe here.
>>> 
>>> 1.
>>> 
>> https://repository.apache.org/content/repositories/snapshots/org/apache/dubbo/dubbo/2.7.0-SNAPSHOT/
>>> 
>>> Jun
>>> 
 On Jan 13, 2019, at 5:58 PM, Huxing Zhang  wrote:
 
 Hi Jun,
 
 Could you summarize the current status of the 2.7-release branch?
 I see there are still several enhancement on this branch.
 
 As this is the first time to prepare for a release for me, I am trying
 to walk through the release steps[1].
 I might try to deploy snapshot to maven repository.
 
 Once we feel it is ready to do the release, I will start the formal
 release process.
 
 
 [1] http://dubbo.apache.org/en-us/blog/prepare-an-apache-release.html
 
 
 --
 Best Regards！
 Huxing
 
 On Mon, Jan 7, 2019 at 1:48 PM jun liu  wrote:
> 
>>> 
>>> Nice work!
>>> 
>>> I think we should let the community to participate more in the
>> release
>>> process, for example,
>>> 1. check out a release branch called 2.7.0-release
>>> 2. encourage people to check it out, test it and report if there is
>>> any regressions, bugs or issues.
>>> 3. while we are doing the test, we can start going through the ASF
>>> release process locally, once we think it is ready to start a formal
>>> release note, it can be done very quickly.
>>> 
>>> By the way, we need decide the release manager of 2.7.0 release. Is
>>> there anyone who volunteer to do that?
> 
> Sorry, I missed this mail.
> * 2.7.0-release has been created
> * we've froze the codebase, test is underway.
> 
>> I'd like to be the release manager if no one is claiming it.
> 
> Great, I can help you with the source/binary packaging and tagging
>>> things.
> 
> Jun
> 
>> On Jan 5, 2019, at 12:11 PM, Huxing Zhang  wrote:
>> 
>> Hi,
>> 
>> On Fri, Dec 28, 2018 at 10:45 AM Huxing Zhang 
>>> wrote:
>>> 
>>> Nice work!
>>> 
>>> I think we should let the community to participate more in the
>> release
>>> process, for example,
>>> 1. check out a release branch called 2.7.0-release
>>> 2. encourage people to check it out, test it and report if there is
>>> any regressions, bugs or issues.
>>> 3. while we are doing the test, we can start going through the ASF
>>> release process locally, once we think it is ready to start a formal
>>> release note, it can be done very quickly.
>>> 
>>> By the way, we need decide the release manager of 2.7.0 release. Is
>>> there anyone who volunteer to do that?
>> 
>> I'd like to be the release manager if no one is claiming it.
>>> 
>>> On Thu, Dec 27, 2018 at 

Re: CI failure for Java 11 - switching to openjdk?

[Mercy]

I suggest we'd better to add OpenJDK for CI,  many companies will choose 
the free OpenJDK since 2019.



Kind regards,

Mercy

在 2019/1/16 下午4:15, Minxuan Zhuang 写道:

I asked in travis ci community[1], the reason is oracle released a new
version of JDK11, and the old link is invalid,  according to the fix in
install_JDK.sh[2], the open jdk may have the same issue. I think we need to
wait until the fix is released.

[1] https://travis-ci.community/t/oracle-jdk11-build-error/1865
[2]
https://github.com/sormuras/bach/commit/b109441fbbf59f02c2fe0734d576333c6bf72c46

On Wed, Jan 16, 2019 at 4:00 PM Huxing Zhang  wrote:


Hi,

The CI for Java 11 is constantly failure from today.

I checked for an example this job[1], and found that the download link
for oracle11 is failing[2].

I tried the link manually and it says:

Sorry!

In order to download products from Oracle Technology Network you must
agree to the OTN license terms.

Currently the PR will not pass due to this.

I am thinking that should we switch from oraclejdk11 to openjdk11 to
avoid this. Travis support both oraclejdk11 and openjdk11[3].

How to you think?

[1] https://travis-ci.org/apache/incubator-dubbo/jobs/480245855
[2]
http://download.oracle.com/otn-pub/java/jdk/11.0.1+13/90cf5d8f270a4347a95050320eef3fb7/jdk-11.0.1_linux-x64_bin.tar.gz
[3] https://docs.travis-ci.com/user/languages/java/

--
Best Regards！
Huxing

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

[victory]

There is no need to shade gson into dubbo.jar, just need depency gson
library.

I have fixed it . https://github.com/apache/incubator-dubbo/pull/3246

Ian Luo  于2019年1月16日周三 下午2:34写道：

> We should not shade gson binaries into dubbo all in one jar file, even
> though there's no license issue. It is simply we should not do this,
> instead, we should make sure dubbo all in one jar should have a transitive
> dependency to gson library.
>
> I noticed it's caused by'com.google.code.gson:gson' in
> dubbo-all/pom.xml. We should fix it.
>
> Thanks,
> -Ian.
>
>
> On Tue, Jan 15, 2019 at 5:16 PM jun liu  wrote:
>
> > I noticed that a third-party source code ‘com.google  >.gson.*’
> > has been compiled into the convenient maven binary jar of 2.7.0 -
> > dubbo-2.7.0.jar :
> > 
> > .
> > ├── META-INF
> > │   ├── DEPENDENCIES
> > │   ├── LICENSE
> > │   ├── MANIFEST.MF
> > │   ├── NOTICE
> > │   ├── assembly
> > │   │   └── bin
> > │   ├── compat
> > │   │   └── dubbo.xsd
> > │   ├── dubbo
> > │   │   └── internal
> > │   ├── dubbo.xsd
> > │   ├── maven
> > │   │   ├── com.alibaba
> > │   │   ├── com.google.code.gson
> > │   │   └── org.apache.dubbo
> > │   ├── spring.handlers
> > │   └── spring.schemas
> > ├── com
> > │   ├── alibaba
> > │   │   ├── com
> > │   │   └── dubbo
> > │   └── google
> > │   └── gson
> > └── org
> > └── apache
> > └── dubbo
> >
> >
> > Since this binary jar (dubbo-2.7.0.jar) will be included in the Apache
> > Binary Release, should we update the LICENSE or NOTICE file in the Binary
> > Release to announce the existence of these binary files?
> >
> > BTW, ‘com.google .gson’ is declared to be unde
> Apache
> > License 2.0.
> >
> > You can directly download the latest SNAPSHOT release of 2.7.0-SNAPSHOT
> in
> > here[1] and unzip and check the contents to better understand what I am
> > trying to describe here.
> >
> > 1.
> >
> https://repository.apache.org/content/repositories/snapshots/org/apache/dubbo/dubbo/2.7.0-SNAPSHOT/
> >
> > Jun
> >
> > > On Jan 13, 2019, at 5:58 PM, Huxing Zhang  wrote:
> > >
> > > Hi Jun,
> > >
> > > Could you summarize the current status of the 2.7-release branch?
> > > I see there are still several enhancement on this branch.
> > >
> > > As this is the first time to prepare for a release for me, I am trying
> > > to walk through the release steps[1].
> > > I might try to deploy snapshot to maven repository.
> > >
> > > Once we feel it is ready to do the release, I will start the formal
> > > release process.
> > >
> > >
> > > [1] http://dubbo.apache.org/en-us/blog/prepare-an-apache-release.html
> > >
> > >
> > > --
> > > Best Regards！
> > > Huxing
> > >
> > > On Mon, Jan 7, 2019 at 1:48 PM jun liu  wrote:
> > >>
> > 
> >  Nice work!
> > 
> >  I think we should let the community to participate more in the
> release
> >  process, for example,
> >  1. check out a release branch called 2.7.0-release
> >  2. encourage people to check it out, test it and report if there is
> >  any regressions, bugs or issues.
> >  3. while we are doing the test, we can start going through the ASF
> >  release process locally, once we think it is ready to start a formal
> >  release note, it can be done very quickly.
> > 
> >  By the way, we need decide the release manager of 2.7.0 release. Is
> >  there anyone who volunteer to do that?
> > >>
> > >> Sorry, I missed this mail.
> > >> * 2.7.0-release has been created
> > >> * we've froze the codebase, test is underway.
> > >>
> > >>> I'd like to be the release manager if no one is claiming it.
> > >>
> > >> Great, I can help you with the source/binary packaging and tagging
> > things.
> > >>
> > >> Jun
> > >>
> > >>> On Jan 5, 2019, at 12:11 PM, Huxing Zhang  wrote:
> > >>>
> > >>> Hi,
> > >>>
> > >>> On Fri, Dec 28, 2018 at 10:45 AM Huxing Zhang 
> > wrote:
> > 
> >  Nice work!
> > 
> >  I think we should let the community to participate more in the
> release
> >  process, for example,
> >  1. check out a release branch called 2.7.0-release
> >  2. encourage people to check it out, test it and report if there is
> >  any regressions, bugs or issues.
> >  3. while we are doing the test, we can start going through the ASF
> >  release process locally, once we think it is ready to start a formal
> >  release note, it can be done very quickly.
> > 
> >  By the way, we need decide the release manager of 2.7.0 release. Is
> >  there anyone who volunteer to do that?
> > >>>
> > >>> I'd like to be the release manager if no one is claiming it.
> > 
> >  On Thu, Dec 27, 2018 at 11:53 PM jun liu 
> wrote:
> > >
> > > Hi, All
> > >
> > > I am writing this mail to
> > >
> > > * Keep you refreshed of the latest status about v2.7.0.
> > > * Call for efforts on code review and tests
> > > * Discuss possible release schedules of v2.7.0.
> > >

Re: CI failure for Java 11 - switching to openjdk?

[Minxuan Zhuang]

I asked in travis ci community[1], the reason is oracle released a new
version of JDK11, and the old link is invalid,  according to the fix in
install_JDK.sh[2], the open jdk may have the same issue. I think we need to
wait until the fix is released.

[1] https://travis-ci.community/t/oracle-jdk11-build-error/1865
[2]
https://github.com/sormuras/bach/commit/b109441fbbf59f02c2fe0734d576333c6bf72c46

On Wed, Jan 16, 2019 at 4:00 PM Huxing Zhang  wrote:

> Hi,
>
> The CI for Java 11 is constantly failure from today.
>
> I checked for an example this job[1], and found that the download link
> for oracle11 is failing[2].
>
> I tried the link manually and it says:
>
> Sorry!
>
> In order to download products from Oracle Technology Network you must
> agree to the OTN license terms.
>
> Currently the PR will not pass due to this.
>
> I am thinking that should we switch from oraclejdk11 to openjdk11 to
> avoid this. Travis support both oraclejdk11 and openjdk11[3].
>
> How to you think?
>
> [1] https://travis-ci.org/apache/incubator-dubbo/jobs/480245855
> [2]
> http://download.oracle.com/otn-pub/java/jdk/11.0.1+13/90cf5d8f270a4347a95050320eef3fb7/jdk-11.0.1_linux-x64_bin.tar.gz
> [3] https://docs.travis-ci.com/user/languages/java/
>
> --
> Best Regards！
> Huxing
>

CI failure for Java 11 - switching to openjdk?

[Huxing Zhang]

Hi,

The CI for Java 11 is constantly failure from today.

I checked for an example this job[1], and found that the download link
for oracle11 is failing[2].

I tried the link manually and it says:

Sorry!

In order to download products from Oracle Technology Network you must
agree to the OTN license terms.

Currently the PR will not pass due to this.

I am thinking that should we switch from oraclejdk11 to openjdk11 to
avoid this. Travis support both oraclejdk11 and openjdk11[3].

How to you think?

[1] https://travis-ci.org/apache/incubator-dubbo/jobs/480245855
[2] 
http://download.oracle.com/otn-pub/java/jdk/11.0.1+13/90cf5d8f270a4347a95050320eef3fb7/jdk-11.0.1_linux-x64_bin.tar.gz
[3] https://docs.travis-ci.com/user/languages/java/

-- 
Best Regards！
Huxing