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

2018-06-07 Thread 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: plan to do some transformation on dubbo admin and dubbo monitor

2018-06-07 Thread Huxing Zhang
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


plan to do some transformation on dubbo admin and dubbo monitor

2018-06-07 Thread Minxuan Zhuang
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.

* 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


Refactor Dubbo metrics

2018-06-07 Thread Huxing Zhang
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


[DISCUSS] Changing Dubbo logo and Dubbo website

2018-06-07 Thread Huxing Zhang
Hi All,

I'd like to bring a discussion about changing Dubbo logo and website.

Background:
* Dubbo's current logo[1] was designed about 5 years ago and has
served for us very well. As Dubbo has joined Apache, I think it is
time to have a new logo to embrace the new era.
* Dubbo's the current website has provide very useful information for
users to quickly learn the basic architecture and bootstrap the first
Dubbo application. However I think there is still lots of work we can
improve, for example:
   * no navigation bar/side bar, it is not easy for user to find the
link to documentation
   * no introduction to Dubbo's core features
   * the current documentation is using gitbooks, the content is not
well organized and has inconsistent style with the website
   * no official blogs
   * no introduction to the community
   * no introduction to the eco-system

Combining the thoughts, I think it is necessary to have a brand new
website and new logo.

Any comments?

[1] https://pic1.zhimg.com/v2-ef111936140375fa6adeba8b740c1d44_1200x500.jpg
-- 
Best Regards!
Huxing


Re: Planing to rename dubbo package to org.apache

2018-06-07 Thread Xin Wang
>Now, there also have 23 PRs under reviewing, we need to fix them first,
merge or close it

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


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

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


Re: Planing to rename dubbo package to org.apache

2018-06-07 Thread 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.
>
>
>
>


Re: Planing to rename dubbo package to org.apache

2018-06-07 Thread Jun Liu
> 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: Dubbo new logo and new website

2018-06-07 Thread Huxing Zhang
Hi,

On Thu, Jun 7, 2018 at 8:24 PM, Justin Mclean  wrote:
> Hi,
>
> The "Alibaba folks" should be doing the work on this list as individuals in
> the open. Doing the development off list then putting in a github repo once
> done is not how Apache works. Ideally they should be making PRs against the
> existing web site.

Since it is a complete new design, IMO it is difficult to use pull request.

>
> The community should also be involved in the development of the new site.
> Perhaps first off ask for submissions from all committers on the new logo
> and then vote on the one to use.

Designing a new logo requires skills which the committers might lack of.
So I think it is better to have professional user experience designers
to do it :)
Luckily, someone in the UED team in Alibaba would like to offer help,
therefore here comes this email.
I will talk to them about getting on the list.

>
> Thanks,
> Justin
>
> On Thu, Jun 7, 2018 at 4:16 PM, Huxing Zhang  wrote:
>
>> Hi community,
>>
>> Just want to let the community to know that I am working with some of
>> the Alibaba folks to create a new website and new logo.
>>
>> The new website/logo will have complete fresh design, including the
>> following contents:
>>
>> * home page
>> * documentation
>> * blogs
>> * community
>> * events
>>
>> All of them will have English/Chinese versions.
>>
>> The implementation is still under way, and would be available in a
>> separate Github repo once finished.
>>
>> The new repo is designed to be a combination of current
>> incubator-dubbo-docs and incubator-dubbo-website.
>>
>> I have a quick question for this, if the community have decided to
>> accept the new logo/website, can a  Software Grant or CLA cover it?
>>
>>
>> --
>> Best Regards!
>> Huxing
>>

-- 
Best Regards!
Huxing


Re: Dubbo new logo and new website

2018-06-07 Thread Huxing Zhang
Hi,

On Thu, Jun 7, 2018 at 6:17 PM, Mark Thomas  wrote:
> On 07/06/18 07:16, Huxing Zhang wrote:
>> Hi community,
>>
>> Just want to let the community to know that I am working with some of
>> the Alibaba folks to create a new website and new logo.
>
> Isn't the need (or not) for a new website something that the community
> should decide?

Yes, apology for that. I should have proposed it before taking any action.

>
>> The new website/logo will have complete fresh design, including the
>> following contents:
>>
>> * home page
>> * documentation
>> * blogs
>> * community
>> * events
>>
>> All of them will have English/Chinese versions.
>>
>> The implementation is still under way, and would be available in a
>> separate Github repo once finished.
>
> That sounds like a code dump. That isn't how things are meant to work at
> Apache.

I thought it is better to explain the ideas if there is something we
can try out with.
Since it is a complete new design, the best way I can think of is:

1. Propose the idea of changing the website/logo
2. The community discuss and vote for the proposal
3. Call for ideas/demos/implementations of the new website/logo
4. The community discuss and vote the for idea/demo/implementation
5. The winning one sign sufficient files to be merge into existing repos

I am wondering that whether there is some guidelines or best practices.

>
>> The new repo is designed to be a combination of current
>> incubator-dubbo-docs and incubator-dubbo-website.
>
> That sounds like a high level design decision I'd expect to see happen
> on the mailing list.
>
>> I have a quick question for this, if the community have decided to
>> accept the new logo/website, can a Software Grant or CLA cover it?
>
> It depends on the detail. I think the higher level issues I've outlined
> above need to be worked through first.
>
> Mark



-- 
Best Regards!
Huxing


Re: Planing to rename dubbo package to org.apache

2018-06-07 Thread Huxing Zhang
Hi,

On Thu, Jun 7, 2018 at 3:32 PM, Yong Zhu  wrote:
> 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?

I think it is ok if there is still remaining PRs while doing the rename work.

For the remaining PRs, we can:
1. comments on them so that they are aware of that
2. ask them to re-send the PR after package rename
3. if they don't respond,  we can do it manually, this may cause extra
work, but IMO won't be too much. If the pull request does not pass the
review, we can just close it.


Note that some of the pull request may not be affected by the package
renaming work if they are minor changes.

>
> Best regards,
> Jerrick



-- 
Best Regards!
Huxing


Re: [Call for talks]: Dubbo Shanghai meetup

2018-06-07 Thread Huxing Zhang
The concern here is that if there is more topics than expected, it
allows the PPMC to choose the best appropriate talks.
Since it is only a half-day event.

On Thu, Jun 7, 2018 at 8:11 PM, Justin Mclean  wrote:
> Hi,
>
>> Please submit your ideas before June 13rd by sending email to
>> priv...@dubbo.apache.org
>
> I don't see that this would be private. Any reason for that suggestion?
>
> Thanks,
> Justin



-- 
Best Regards!
Huxing


Re: Dubbo new logo and new website

2018-06-07 Thread Justin Mclean
Hi,

The "Alibaba folks" should be doing the work on this list as individuals in
the open. Doing the development off list then putting in a github repo once
done is not how Apache works. Ideally they should be making PRs against the
existing web site.

The community should also be involved in the development of the new site.
Perhaps first off ask for submissions from all committers on the new logo
and then vote on the one to use.

Thanks,
Justin

On Thu, Jun 7, 2018 at 4:16 PM, Huxing Zhang  wrote:

> Hi community,
>
> Just want to let the community to know that I am working with some of
> the Alibaba folks to create a new website and new logo.
>
> The new website/logo will have complete fresh design, including the
> following contents:
>
> * home page
> * documentation
> * blogs
> * community
> * events
>
> All of them will have English/Chinese versions.
>
> The implementation is still under way, and would be available in a
> separate Github repo once finished.
>
> The new repo is designed to be a combination of current
> incubator-dubbo-docs and incubator-dubbo-website.
>
> I have a quick question for this, if the community have decided to
> accept the new logo/website, can a  Software Grant or CLA cover it?
>
>
> --
> Best Regards!
> Huxing
>


Re: Planing to rename dubbo package to org.apache

2018-06-07 Thread Justin Mclean
Hi,

> I suggest that we have to freeze new comming PR after notification community.

Up to the PMC but I think this will cause more issues than it will solve. Lets 
see what other people say in this thread.

Thanks,
Justin

Re: [Call for talks]: Dubbo Shanghai meetup

2018-06-07 Thread Justin Mclean
Hi,

> Please submit your ideas before June 13rd by sending email to
> priv...@dubbo.apache.org

I don't see that this would be private. Any reason for that suggestion?

Thanks,
Justin


Re: Release notification of Apache Dubbo (Incubating) V2.6.2.

2018-06-07 Thread Justin Mclean
HI,

> One more thing to do: we need to using the Apache download link[1] for
> download. I am going to add it to website.

Yes that required.

> The current Github release note contains a download link [2], can we
> change that?


Basically you shouldn't use github releases, but it’s not IMO a big deal, it 
just not an official release even if it contents are identical.

Thanks,
Justin

Re: Dubbo new logo and new website

2018-06-07 Thread Mark Thomas
On 07/06/18 07:16, Huxing Zhang wrote:
> Hi community,
> 
> Just want to let the community to know that I am working with some of
> the Alibaba folks to create a new website and new logo.

Isn't the need (or not) for a new website something that the community
should decide?

> The new website/logo will have complete fresh design, including the
> following contents:
> 
> * home page
> * documentation
> * blogs
> * community
> * events
> 
> All of them will have English/Chinese versions.
> 
> The implementation is still under way, and would be available in a
> separate Github repo once finished.

That sounds like a code dump. That isn't how things are meant to work at
Apache.

> The new repo is designed to be a combination of current
> incubator-dubbo-docs and incubator-dubbo-website.

That sounds like a high level design decision I'd expect to see happen
on the mailing list.

> I have a quick question for this, if the community have decided to
> accept the new logo/website, can a  Software Grant or CLA cover it?

It depends on the detail. I think the higher level issues I've outlined
above need to be worked through first.

Mark


Re: Planing to rename dubbo package to org.apache

2018-06-07 Thread 秦金卫
+1
for renaming package




| |
秦金卫
邮箱:kimmk...@163.com
|

签名由 网易邮箱大师 定制

On 06/07/2018 15:32, Yong Zhu wrote:
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: Prepare for release of Dubbo Spring Boot Project v0.1.1 & v0.2.0

2018-06-07 Thread Huxing Zhang
According to our previous experience, it might take 2 weeks ~ 1month
to get the first release.

1. Create dedicated release branch
2. Make necessary change
3. Tag the release
4. Vote on the mailing list
5. Publish the release

Step 2-5 may be repeated due to release vote comments.

On Thu, Jun 7, 2018 at 3:18 PM, Mercy  wrote:
> Hi, community
>
> We are planing the release of Dubbo Spring Boot Project v0.1.1 & 0.2.0.
>
> For now, Dubbo Spring Boot Project includes two main modules:
>
> dubbo-spring-boot-starter : auto-configure features (e.g.,
> annotation-driven, auto configuration, externalized configuration).
>
> dubbo-spring-boot-actuator : production-ready features (e.g., security,
> health checks, externalized configuration).
>
> We have to will separate two versions for once release because of Spring
> Boot 2.0 breaking changes :
>
> 0.2.x is a main stream release version for Spring Boot 2.x
>
> 0.1.x is a legacy version for maintaining Spring Boot 1.x
>
> Release Milestone
>
> Release notes
>
> 1. Enhancements
>
> Upgrading dubbo 2.6.2
>
> Compatible with Spring Boot 1.5.x and 2.0.x
>
> Full Support of resolving placeholder on Dubbo @Service and @Reference
> attributes
>
> Blocking main thread until it's shutdown so that the Non-Web Spring Boot
> application provides continuous services
>
> Remove dubbo banner
>
> 2. Bugfixs
>
> Failed reading extenerialized configuration on Yaml files
>
> Relaxed binding of extenerialized configuration issue
>
> Other minor issues
>
> We look forward to listening any ideas or questions.
>
> Kind regards,
>
> Mercy Ma

-- 
Best Regards!
Huxing


[Call for talks]: Dubbo Shanghai meetup

2018-06-07 Thread Huxing Zhang
Hi community,

We are planning to hold a meetup in Shanghai in June 23rd (Saturday)
or June 24th (Sunday), and we are open to community talks about:

* How we use Dubbo in production system
* Dubbo best practice
* Integrate Dubbo with other open source software
* Other topics involving Dubbo

Please submit your ideas before June 13rd by sending email to
priv...@dubbo.apache.org

Thank Alibaba for sponsoring this event.

-- 
Best Regards!
Huxing


Re: Release notification of Apache Dubbo (Incubating) V2.6.2.

2018-06-07 Thread Huxing Zhang
On Thu, Jun 7, 2018 at 4:15 PM, jun liu  wrote:
>> One more thing to do: we need to using the Apache download link[1] for
>> download. I am going to add it to website.
>
> +1

It's done.

>
>> The current Github release note contains a download link [2], can we
>> change that?
>>
>> If not, can we keep it for compatibility?
>
> Seems Github downlink cannot be changed to the Apache link. I think we can 
> keep the Github downlink. Let’s see what mentors will say?
>
> Best regards,
> Jun
>
>> On 7 Jun 2018, at 2:44 PM, Huxing Zhang  wrote:
>>
>> One more thing to do: we need to using the Apache download link[1] for
>> download. I am going to add it to website.
>>
>> The current Github release note contains a download link [2], can we
>> change that?
>>
>> If not, can we keep it for compatibility?
>>
>>
>> [1] 
>> https://www.apache.org/dyn/closer.cgi?path=incubator/dubbo/2.6.2/dubbo-incubating-2.6.2-source-release.zip
>> [2] https://github.com/apache/incubator-dubbo/releases
>>
>> On Thu, Jun 7, 2018 at 2:01 PM, Jun Liu  wrote:
>>> Sorry, I forget about the transfer thing.
>>>
>>> The release content is now under: 
>>> https://dist.apache.org/repos/dist/release/incubator/dubbo/2.6.2.
>>>
>>> Best regards,
>>> Jun
>>>
 On 7 Jun 2018, at 11:48 AM, Huxing Zhang  wrote:

 Hi,

 I found the artifacts are still under
 https://dist.apache.org/repos/dist/dev/incubator/dubbo/2.6.2/

 It should be moved to https://dist.apache.org/repos/dist/release/

 See [1] for more details.

 [1] http://www.apache.org/dev/release-publishing.html#distribution

 On Thu, Jun 7, 2018 at 9:46 AM, Jun Liu  wrote:
> Hi,
>
> The Apache Dubbo (Incubating) 2.6.2 has just been released. Thanks you 
> all for your help.
>
> The Apache vote thread:
> https://lists.apache.org/thread.html/0e95ab5ed14acafdfc1d621e9b9e7621e78412eb5d611fe6f765b4ca@%3Cgeneral.incubator.apache.org%3E
>
> Best regards,
> Jun
>



 --
 Best Regards!
 Huxing
>>>
>>
>>
>>
>> --
>> Best Regards!
>> Huxing
>



-- 
Best Regards!
Huxing


Re: Release notification of Apache Dubbo (Incubating) V2.6.2.

2018-06-07 Thread jun liu
> One more thing to do: we need to using the Apache download link[1] for
> download. I am going to add it to website.

+1

> The current Github release note contains a download link [2], can we
> change that?
> 
> If not, can we keep it for compatibility?

Seems Github downlink cannot be changed to the Apache link. I think we can keep 
the Github downlink. Let’s see what mentors will say?

Best regards,
Jun

> On 7 Jun 2018, at 2:44 PM, Huxing Zhang  wrote:
> 
> One more thing to do: we need to using the Apache download link[1] for
> download. I am going to add it to website.
> 
> The current Github release note contains a download link [2], can we
> change that?
> 
> If not, can we keep it for compatibility?
> 
> 
> [1] 
> https://www.apache.org/dyn/closer.cgi?path=incubator/dubbo/2.6.2/dubbo-incubating-2.6.2-source-release.zip
> [2] https://github.com/apache/incubator-dubbo/releases
> 
> On Thu, Jun 7, 2018 at 2:01 PM, Jun Liu  wrote:
>> Sorry, I forget about the transfer thing.
>> 
>> The release content is now under: 
>> https://dist.apache.org/repos/dist/release/incubator/dubbo/2.6.2.
>> 
>> Best regards,
>> Jun
>> 
>>> On 7 Jun 2018, at 11:48 AM, Huxing Zhang  wrote:
>>> 
>>> Hi,
>>> 
>>> I found the artifacts are still under
>>> https://dist.apache.org/repos/dist/dev/incubator/dubbo/2.6.2/
>>> 
>>> It should be moved to https://dist.apache.org/repos/dist/release/
>>> 
>>> See [1] for more details.
>>> 
>>> [1] http://www.apache.org/dev/release-publishing.html#distribution
>>> 
>>> On Thu, Jun 7, 2018 at 9:46 AM, Jun Liu  wrote:
 Hi,
 
 The Apache Dubbo (Incubating) 2.6.2 has just been released. Thanks you all 
 for your help.
 
 The Apache vote thread:
 https://lists.apache.org/thread.html/0e95ab5ed14acafdfc1d621e9b9e7621e78412eb5d611fe6f765b4ca@%3Cgeneral.incubator.apache.org%3E
 
 Best regards,
 Jun
 
>>> 
>>> 
>>> 
>>> --
>>> Best Regards!
>>> Huxing
>> 
> 
> 
> 
> -- 
> Best Regards!
> Huxing



Re: dubbo支持kryo序列化协议吗?

2018-06-07 Thread Huxing Zhang
Hello,

Would you please ask in English? Dubbo is a global community and we
would like every topic to be understandable by people all over the
world.

If you prefer to communicate in Chinese, please try using the gitter
channel: https://gitter.im/alibaba/dubbo

Regarding your question, I have relied in the your issue.

2018-06-07 16:02 GMT+08:00 liulixue120 :
> 你好,能帮忙看下面这个问题吗,谢谢!
> https://github.com/apache/incubator-dubbo/issues/1897
>
>
>
>
>
>
>
>
>



-- 
Best Regards!
Huxing


dubbo支持kryo序列化协议吗?

2018-06-07 Thread liulixue120
你好,能帮忙看下面这个问题吗,谢谢!
https://github.com/apache/incubator-dubbo/issues/1897











Re: Planing to rename dubbo package to org.apache

2018-06-07 Thread Mercy
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

2018-06-07 Thread 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


Prepare for release of Dubbo Spring Boot Project v0.1.1 & v0.2.0

2018-06-07 Thread Mercy

Hi, community

We are planing the release of Dubbo Spring Boot Project v0.1.1 & 0.2.0.

For now, Dubbo Spring Boot Project includes two main modules:

 *

   |dubbo-spring-boot-starter|: auto-configure features
   
(e.g.,
   annotation-driven, auto configuration, externalized configuration).

 *

   |dubbo-spring-boot-actuator|: production-ready features
   
(e.g.,
   security, health checks, externalized configuration).

We have to will separate two versions for once release because of Spring 
Boot 2.0 breaking changes :


 *

   |0.2.x|
   is a
   main stream release version for Spring Boot 2.x

 *

   |0.1.x|
   is
   a legacy version for maintaining Spring Boot 1.x


   Release Milestone
   



   Release notes


 1. Enhancements

 *

   Upgrading dubbo |2.6.2|

 *

   Compatible with Spring Boot |1.5.x|and |2.0.x|

 *

   Full Support of resolving placeholder on Dubbo |@Service|and
   |@Reference|attributes

 *

   Blocking main thread until it's shutdown so that the Non-Web Spring
   Boot application provides continuous services

 *

   Remove dubbo banner


 2. Bugfixs

 *

   Failed reading extenerialized configuration on Yaml files

 *

   Relaxed binding of extenerialized configuration issue

 *

   Other minor issues

We look forward to listening any ideas or questions.

Kind regards,

Mercy Ma



Re: Release notification of Apache Dubbo (Incubating) V2.6.2.

2018-06-07 Thread Huxing Zhang
One more thing to do: we need to using the Apache download link[1] for
download. I am going to add it to website.

The current Github release note contains a download link [2], can we
change that?

If not, can we keep it for compatibility?


[1] 
https://www.apache.org/dyn/closer.cgi?path=incubator/dubbo/2.6.2/dubbo-incubating-2.6.2-source-release.zip
[2] https://github.com/apache/incubator-dubbo/releases

On Thu, Jun 7, 2018 at 2:01 PM, Jun Liu  wrote:
> Sorry, I forget about the transfer thing.
>
> The release content is now under: 
> https://dist.apache.org/repos/dist/release/incubator/dubbo/2.6.2.
>
> Best regards,
> Jun
>
>> On 7 Jun 2018, at 11:48 AM, Huxing Zhang  wrote:
>>
>> Hi,
>>
>> I found the artifacts are still under
>> https://dist.apache.org/repos/dist/dev/incubator/dubbo/2.6.2/
>>
>> It should be moved to https://dist.apache.org/repos/dist/release/
>>
>> See [1] for more details.
>>
>> [1] http://www.apache.org/dev/release-publishing.html#distribution
>>
>> On Thu, Jun 7, 2018 at 9:46 AM, Jun Liu  wrote:
>>> Hi,
>>>
>>> The Apache Dubbo (Incubating) 2.6.2 has just been released. Thanks you all 
>>> for your help.
>>>
>>> The Apache vote thread:
>>> https://lists.apache.org/thread.html/0e95ab5ed14acafdfc1d621e9b9e7621e78412eb5d611fe6f765b4ca@%3Cgeneral.incubator.apache.org%3E
>>>
>>> Best regards,
>>> Jun
>>>
>>
>>
>>
>> --
>> Best Regards!
>> Huxing
>



-- 
Best Regards!
Huxing


Dubbo new logo and new website

2018-06-07 Thread Huxing Zhang
Hi community,

Just want to let the community to know that I am working with some of
the Alibaba folks to create a new website and new logo.

The new website/logo will have complete fresh design, including the
following contents:

* home page
* documentation
* blogs
* community
* events

All of them will have English/Chinese versions.

The implementation is still under way, and would be available in a
separate Github repo once finished.

The new repo is designed to be a combination of current
incubator-dubbo-docs and incubator-dubbo-website.

I have a quick question for this, if the community have decided to
accept the new logo/website, can a  Software Grant or CLA cover it?


-- 
Best Regards!
Huxing


Re: Release notification of Apache Dubbo (Incubating) V2.6.2.

2018-06-07 Thread Jun Liu
Sorry, I forget about the transfer thing.

The release content is now under: 
https://dist.apache.org/repos/dist/release/incubator/dubbo/2.6.2.

Best regards,
Jun

> On 7 Jun 2018, at 11:48 AM, Huxing Zhang  wrote:
> 
> Hi,
> 
> I found the artifacts are still under
> https://dist.apache.org/repos/dist/dev/incubator/dubbo/2.6.2/
> 
> It should be moved to https://dist.apache.org/repos/dist/release/
> 
> See [1] for more details.
> 
> [1] http://www.apache.org/dev/release-publishing.html#distribution
> 
> On Thu, Jun 7, 2018 at 9:46 AM, Jun Liu  wrote:
>> Hi,
>> 
>> The Apache Dubbo (Incubating) 2.6.2 has just been released. Thanks you all 
>> for your help.
>> 
>> The Apache vote thread:
>> https://lists.apache.org/thread.html/0e95ab5ed14acafdfc1d621e9b9e7621e78412eb5d611fe6f765b4ca@%3Cgeneral.incubator.apache.org%3E
>> 
>> Best regards,
>> Jun
>> 
> 
> 
> 
> -- 
> Best Regards!
> Huxing