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

This is really a milestone to get all UTs pass. Since it is now officially on the master branch, I am expecting more eyes on the code quality and the design. Cheers, -Ian. On Thu, Dec 27, 2018 at 11:07 PM jun liu wrote: > Hi, All > > Good news. All UTs in master has passed the Travis CI. > The

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

Hi, All Good news. All UTs in master has passed the Travis CI. The next goal would be to push this branch to release ready, I suggest we focus on code/design review and feature test. I’ll start a new thread to summary current status, todos and discuss about possible release schedules. Jun > O

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

Hi, all I also found out that the master ci has failed. This caused some misunderstanding for me to deal with a pending pr[1]. After observing the log, I found that the issue[2] with @xin wang feedback is the same problem. Since the ci of the module of the cluster has passed and the code is well,

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

> Now the travis ci of master branch faile， I create an issue > https://github.com/apache/incubator-dubbo/issues/3052 > Please take a look at it Thanks, I noticed too, I’ll take care of it. Jun > On Dec 24, 2018, at 5:25 PM, Xin Wang wrote: > > hi, Jun > > Now the travis ci of master branch f

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

hi, Jun Now the travis ci of master branch faile， I create an issue https://github.com/apache/incubator-dubbo/issues/3052 Please take a look at it Xin Wang 于2018年12月24日周一 下午4:38写道： > >I have just merged dev-metadata branch into master, from now on, the > master branch will work as the develop a

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

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

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

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

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

> Dubbo OPS is about to release the first version, it supports service > governance features in Dubbo2.7, including tag route, application scope > rules, metadata report, etc. I've deployed a demo here: > http://47.91.207.147/#/service . Great! I have tried and enc

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

Dubbo OPS is about to release the first version, it supports service governance features in Dubbo2.7, including tag route, application scope rules, metadata report, etc. I've deployed a demo here: http://47.91.207.147/#/service. the code locates here: https://github.com/apache/incubator-dubbo-ops/t

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

Two more things to mention: 1. I am thinking of merge this dev-metadata branch back to the master. Both these two branches have the same version 2.7.0-SNAPSHOT and they together consist of v2.7’s release candidates. While they are evolving at the same time concurrently, conflicts keep happening

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

> 1. Prioritization of centralized configuration Now, the centralized configuration or externalized configuration is implemented to has the highest priority by default. For flexible concerns, a switch is designed and opened to users so that they can override the default value, for example, you

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

All of this features are the biggest concert in the community. I have some questions： 1.中心化配置的优先级 2.路由的逻辑比较复杂，和原来低版本的兼容性怎么保证 3.Tag路由改造了，和原来的兼容性怎么样？ 4.Environment这个东西是怎么明确职责的？最好能有个独立的说明。 -- 1. Prioritization of centralized configuration 2. The logic of the route is more complicated, and the

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

Hi, All I’ve just posted some blogs[4] on Github issues relating to the design principles and implementations of V2.7.0, the content are based mainly on my own understanding of the 2.7.0 codebase (hosted on branch dev-metadata[1]) and the previous discussions[2][3]. Recently, I spent plenty o