[DRAFT] Incubator PMC Board Report - May 2018

All, Below is the current draft of the Incubator report. There's some curious notes about it. - We only executed 1 release last month. I think that's the least I've seen since I've been putting together the reports. - No new podlings, and some graduations are pending. We have 2 podlings

Re: Set up Nexus staging profile for Dubbo (Incubating)

Hi, On Thu, May 3, 2018 at 8:58 AM, Justin Mclean wrote: > Hi, > >> We are preparing for the first apache incubating release for dubbo, turns >> out we lack of some nexus permissions, this blocks our process. > > The offical release area is not nexus it on the Apache

Re: Question

Hi, This is a typo, which has been fixed in [1]. The problem is that the latest documentation has not been published. I will do it soon. [1] https://github.com/apache/incubator-dubbo-docs/pull/21 On Thu, May 3, 2018 at 5:26 PM, xiaobai yu wrote: > Dear Developers， >

Re: Publishing Maven artifacts under third-party coordinates (was: Set up Nexus staging profile for Dubbo ...)

Greg has it all correct. But nothing prevents Alibaba from publishing under coordinates that they control. It needs to be clear however that it is alibaba publishing there, not Apache. On Tue, May 8, 2018, 13:56 Greg Stein wrote: > Hi all, > > I wanted to send a note that

Signing Apache ICLA to help Dubbo finish IP clearance process

(Chinese after English) Hello, I am Huxing, I am committer and PMC member of Apache Dubbo(incubating). You have contributed to Dubbo in the past, but never signed either Apache ICLA or Alibaba CLA before. Please refer to [1][2] for more details. Since Dubbo has been donated to Apache Software

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

1. Can you just use their released version? Internal version has fixed a lot of bugs, there is an incompatibility risk when using the release version in the short term. Before using the release version, we need to submit the repaired feature to owner / maintainers of hessian-lit. yiji > 在

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

Agree +1> Now we are considering that moving it to Dubbo eco-system, which is https://github/dubbo. The hessian-lit sub module is a serialize component of the same level as Thrift, and should be placed outside the core system. Xin Wang lovep...@hotmail.com 在

Re: Publishing Maven artifacts under third-party coordinates (was: Set up Nexus staging profile for Dubbo ...)

On Thu, May 10, 2018 at 6:50 PM, Julian Hyde wrote: > ...In other words, there are several ways to prove that a binary release > is WRONG but (to Greg’s point) there is no way to prove it RIGHT One useful thing that people could do with binary artifacts is to say "I use the

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

Hello Dubbo Community, This is a call for vote to release Apache Dubbo (Incubating) version 2.6.2. The release candidates: https://dist.apache.org/repos/dist/dev/incubator/dubbo/2.6.2 / Git tag for the release:

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

> Release Notes: > https://github.com/apache/incubator-dubbo/releases/tag/untagged-4775c0a22c60fca55118 Sorry, the previous link seems invisible for non-committers, please check the following link for detailed release notes: https://github.com/apache/incubator-dubbo/blob/2.6.2-release/CHANGES.md

Re: Signing Apache ICLA to help Dubbo finish IP clearance process

你好，已经按照提示发了一个CLA邮件了 2018-05-14 16:06 GMT+08:00 Huxing Zhang : > (Chinese after English) > > Hello, > > I am Huxing, I am committer and PMC member of Apache Dubbo(incubating). > > You have contributed to Dubbo in the past, but never signed either > Apache ICLA or Alibaba CLA

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

Hi, [x] +1 approve [ ] +0 no opinion [ ] -1 disapprove with the reason Details: * incubator in name * Disclaimer exists * sha512 chesum ok * signature ok * NOTICE and LICENSE exist in META-INF of jar files of binary release. * Unit test passed on Java 8 + OSX Other minor comments: * The

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

On Tue, May 15, 2018 at 2:11 PM, Jun Liu wrote: >> Release Notes: >> https://github.com/apache/incubator-dubbo/releases/tag/untagged-4775c0a22c60fca55118 > > Sorry, the previous link seems invisible for non-committers, please check the > following link for detailed release

Re: Set up Nexus staging profile for Dubbo (Incubating)

Hi, > Most of the dubbo users depend on the maven artifact, therefore I > think a maven artifact is mandatory from Dubbo's point of view, > although it is not mandatory according to ASF release policy. Is it something you could possibly put off until your second ASF second release? > Can we

Re: Publishing Maven artifacts under third-party coordinates (was: Set up Nexus staging profile for Dubbo ...)

Hi, >> ...The maven artifact is the most significant for most of the Dubbo >> users, so we want to include a maven artifact in the release > > Binaries are NOT part of Apache Releases, as mentioned earlier in this thread. Apache Dubbo is aware of that and it has been made clear on the dev

Re: Publishing Maven artifacts under third-party coordinates (was: Set up Nexus staging profile for Dubbo ...)

On Wed, May 9, 2018 at 3:35 PM, Bertrand Delacretaz wrote: > On Wed, May 9, 2018 at 3:44 AM, Huxing Zhang wrote: >> ...The maven artifact is the most significant for most of the Dubbo >> users, so we want to include a maven artifact in the

Re: Publishing Maven artifacts under third-party coordinates (was: Set up Nexus staging profile for Dubbo ...)

Please note: my initial message was not to question the release process. Merely that Infra was asked to enable provision of artifacts within Maven Central under a groupId that is not "org.apache". At the moment, we cannot / will-not work on making that possible. Infra doesn't involve itself in

How to package dubbo.jar correctly?

Hi there, I have a patch that needs to be applied to our organization first. So I use the normal way - 'mvn clean install -DskipTests=true' to package the dubbo.jar (based on branch 2.5.x). However, the pom file for the generated artifact is

Re: Set up Nexus staging profile for Dubbo (Incubating)

Hi, On Tue, May 8, 2018 at 6:10 AM, Justin Mclean wrote: > Hi, > >> Most of the dubbo users depend on the maven artifact, therefore I >> think a maven artifact is mandatory from Dubbo's point of view, >> although it is not mandatory according to ASF release policy. > >

Re: Set up Nexus staging profile for Dubbo (Incubating)

Hi, On Tue, May 8, 2018 at 12:12 PM, Justin Mclean wrote: > Hi, > >> I don't think so, I think each Dubbo release should contain a maven artifact. > > Projects can also release convenience binary artefacts at the same time of a > source release. It’s a good idea to vote on

Re: Publishing Maven artifacts under third-party coordinates (was: Set up Nexus staging profile for Dubbo ...)

Hi, I would like to clarify more on a wider range. Dubbo will always trying to follow the ASF release policy as much as possible. The reason why the group id remains com.alibaba is for compatibility purpose. It might take some time for Dubbo to to change the group id as well as package name,

Re: Publishing Maven artifacts under third-party coordinates (was: Set up Nexus staging profile for Dubbo ...)

Hi - Sent from my iPhone > On May 8, 2018, at 5:08 PM, Justin Mclean wrote: > > Hi, > >> But nothing prevents Alibaba from publishing under coordinates that they >> control. >> >> It needs to be clear however that it is alibaba publishing there, not >> Apache. > >

Re: Publishing Maven artifacts under third-party coordinates (was: Set up Nexus staging profile for Dubbo ...)

Hi, > But nothing prevents Alibaba from publishing under coordinates that they > control. > > It needs to be clear however that it is alibaba publishing there, not > Apache. The has been discussed on list with Dubbo and that’s the approach they are going to take with their first release. They

Re: Set up Nexus staging profile for Dubbo (Incubating)

Hi, > Was there discussion somewhere that decided to allow an Apache project to > publish coordinates using com.alibaba? The maven artefacts would not be an ASF release only the source release would be and published and named as such is my understanding. Maven artefacts are not not offical

Re: Publishing Maven artifacts under third-party coordinates (was: Set up Nexus staging profile for Dubbo ...)

Hi, > Maybe the first release should be Apache for the source with Alibaba making > the binary release through their current Maven release process. Which is my understanding of what they are going to do. They were also going to vote on the binary to check it’s OK but not have that as part of

Re: Set up Nexus staging profile for Dubbo (Incubating)

Hi, > So that means it is better to publish both the source and binary > artifact to the Apache mirror system and vote them there. > The only thing that block us is we can not publish to > https://repository.apache.org (since our group id not starting with > org.apache), then to nexus, we want to

Re: GSoC student - Getting started.

Hi Reghu, I have checked the schedule of GSoC. We have nearly one month to get familiar with dubbo. I am wondering if you can write down your understanding of dubbo when learning, anything you interest, a simple introduction of dubbo’s features, your experience of running dubbo from zero,

[DRAFT] Dubbo Incubator Report - May 2018

Hi Community, Below is a draft of Dubbo Incubator Report, May 2018. Please feel free to comment if you have any concern. --- Dubbo Dubbo is a high-performance, lightweight, java based RPC framework. Dubbo has been incubating since 2018-02-16. Three most important issues to address in the

Re: How to package dubbo.jar correctly?

Hi，Jun, I have recorded this question：“ What's the difference between version 2.6.x and version 2.5.x ?” in FAQ page https://github.com/apache/incubator-dubbo/wiki/FAQ You can add more details in it. Xin Wang lovep...@hotmail.com 在 2018年5月10日，上午8:07，Jun Liu

Re: How to package dubbo.jar correctly?

Hi song, > However, the pom file in official released artifact is > https://github.com/apache/incubator-dubbo/blob/2.5.x/dubbo-maven/pom.xml > These 2 pom files are quite different, especially in the dependency scope > part. You can package to generate an all-in-one dubbo jar, and the only

Re: Publishing Maven artifacts under third-party coordinates (was: Set up Nexus staging profile for Dubbo ...)

On 10 May 2018 at 11:37, Greg Stein wrote: > On Thu, May 10, 2018 at 3:31 AM, Huxing Zhang wrote: > >> Hi, >> >> On Thu, May 10, 2018 at 3:59 PM, Willem Jiang >> wrote: >> > Is there any plan for going through the vote process of

Re: Publishing Maven artifacts under third-party coordinates (was: Set up Nexus staging profile for Dubbo ...)

On Thu, May 10, 2018 at 3:31 AM, Huxing Zhang wrote: > Hi, > > On Thu, May 10, 2018 at 3:59 PM, Willem Jiang > wrote: > > Is there any plan for going through the vote process of Binary file? > > Yes, binaries will also go through the vote process.

Re: Publishing Maven artifacts under third-party coordinates (was: Set up Nexus staging profile for Dubbo ...)

Is there any plan for going through the vote process of Binary file? Normally there are lots of work on the License files of Binary durning the first release. Maybe we should need to vote the binary file as well. Willem Jiang Blog: http://willemjiang.blogspot.com (English)

Re: How to package dubbo.jar correctly?

Hi Jun, Thanks for your quick reply. So you will use the pom.xml different from the official one, and it makes no difference for end users. Actually, there are some differences. For example, if I use the artifact I packaged with 'mvn clean install’, there will be a log4j transitive

Re: Publishing Maven artifacts under third-party coordinates (was: Set up Nexus staging profile for Dubbo ...)

On 10 May 2018 at 16:56, Matt Sicker wrote: > I still minimally require proper gpg signatures on binary artifacts. The > source artifacts are what get far more scrutiny, but the binaries are > released on apache.org after all. +1 It may also be possible to verify that the

Re: Publishing Maven artifacts under third-party coordinates (was: Set up Nexus staging profile for Dubbo ...)

On Thu, May 10, 2018 at 4:17 AM, sebb wrote: > On 10 May 2018 at 11:37, Greg Stein wrote: >> On Thu, May 10, 2018 at 3:31 AM, Huxing Zhang wrote: >> >>> Hi, >>> >>> On Thu, May 10, 2018 at 3:59 PM, Willem Jiang >>>

Re: Publishing Maven artifacts under third-party coordinates (was: Set up Nexus staging profile for Dubbo ...)

I still minimally require proper gpg signatures on binary artifacts. The source artifacts are what get far more scrutiny, but the binaries are released on apache.org after all. On 10 May 2018 at 10:20, Roman Shaposhnik wrote: > On Thu, May 10, 2018 at 4:17 AM, sebb

Re: Publishing Maven artifacts under third-party coordinates (was: Set up Nexus staging profile for Dubbo ...)

In other words, there are several ways to prove that a binary release is WRONG but (to Greg’s point) there is no way to prove it RIGHT. As a mentor, I strongly advise against podlings making binary releases, especially for the first release. It’s difficult enough to get L correct for source

Re: [Mentors] IP clearance

On 13/05/2018 06:17, Justin Mclean wrote: Hi, A lot of work has been done on the IP clearance. [1] IMO given the 4 people mention in the JIRA to be contacted has all contributed less than 10 lines of code each I don't see this as holding up the release while we wait for a reply / ICLA from

[Mentors] IP clearance

Hi, A lot of work has been done on the IP clearance. [1] IMO given the 4 people mention in the JIRA to be contacted has all contributed less than 10 lines of code each I don't see this as holding up the release while we wait for a reply / ICLA from them. Absolute worse case code can be

Re: [Mentors] IP clearance

+1 On Sun, May 13, 2018 at 6:58 PM Mark Thomas wrote: > > > On 13/05/2018 06:17, Justin Mclean wrote: > > Hi, > > > > A lot of work has been done on the IP clearance. [1] > > > > IMO given the 4 people mention in the JIRA to be contacted has all > contributed less than 10

Dubbo release candidate

Hi, I saw that a release candidate has been put up here [1] and I had a quick look at it. It looks good to me with a couple of minor issues: - The binary LICENSE fails to mention FastJSON (but as this is ALv2 it’s not required) Not this will make the connivance binary LICENSE file different to

Re: Dubbo release candidate

> - The binary LICENSE fails to mention FastJSON (but as this is ALv2 it’s not > required) Not this will make the connivance binary LICENSE file different to > the source LICENSE file FastJSON should not be part of the binary release, should be caused by a bug of filters, i will remove it. >

Re: Publishing Maven artifacts under third-party coordinates (was: Set up Nexus staging profile for Dubbo ...)

On Thu, May 10, 2018 at 3:25 PM, Roman Shaposhnik wrote: > On Thu, May 10, 2018 at 9:50 AM, Julian Hyde wrote: > > In other words, there are several ways to prove that a binary release is > WRONG but (to Greg’s point) there is no way to prove it RIGHT. >

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

Hi, > Now we are considering that moving it to Dubbo eco-system, which is > https://github/dubbo. > > How do you think about this? I don’t know the history here so the answer to these questions may be obvious to someone eon the project. What do the owner / maintainers of hessian-lite think

Re: Publishing Maven artifacts under third-party coordinates (was: Set up Nexus staging profile for Dubbo ...)

Hi, Looking at the release candidate just made both the license and notice for the source release and the connivance binary are going to be just about identical as there's only 2 3rd party jars included and none of the other jars contain 3rd party code (other than what is mentioned in

Re: Publishing Maven artifacts under third-party coordinates (was: Set up Nexus staging profile for Dubbo ...)

Hi, >> As a mentor, I strongly advise against podlings making binary releases, >> especially for the first release. >> It’s difficult enough to get L correct for source releases, and when a >> binary release is being make >> at the same time with necessarily different L, the PPMC tend to get

Moving hessian-lite from Dubbo codebase to eco-system

Hi, hessian-lite a customized version of the official hessian maintained inside Dubbo, and it's relatively stable, only upgrading for special bugfix. It's version(3.2.2) is different from Dubbo(now 2.6.2), and their release paces are also different. Now we are considering that moving it to

Re: Dubbo release candidate

Hi, On Fri, May 11, 2018 at 12:05 PM, Justin Mclean wrote: > Hi, > > I saw that a release candidate has been put up here [1] and I had a quick > look at it. It looks good to me with a couple of minor issues: > - The binary LICENSE fails to mention FastJSON (but as this

Re: Dubbo release candidate

Hi, >> - The binary LICENSE fails to mention FastJSON (but as this is ALv2 it’s not >> required) Not this will make the connivance binary LICENSE file different to >> the source LICENSE file > > FastJSON should not be part of the binary release, should be caused by a bug > of filters, i will

Re: Publishing Maven artifacts under third-party coordinates (was: Set up Nexus staging profile for Dubbo ...)

Hi, > There is NO WAY to verify a binary. Even compiling from source to binary on > your machine, and trying to compare against a target binary will generally > fail since timestamps are embedded. Or maybe there are different compilers > being used. As per ASF policy a connivance binary can be

Re: Dubbo release candidate

Hi, > hessian-lite-3.2.2.jar is a part of this release, both resource and binary > should include hessian-lite. So now we need add clarification of hessian-lite > in the LICENSE and NOTICE files in libs, right? It’s ALv2 and from what I can see there no notice file. Is that correct? If so it

Re: Dubbo release candidate

> What about hessian-lite-3.2.2.jar should that be there? hessian-lite-3.2.2.jar is a part of this release, both resource and binary should include hessian-lite. So now we need add clarification of hessian-lite in the LICENSE and NOTICE files in libs, right? FYI, hessian-lite a customized

Re: Dubbo release candidate

Hi, On Fri, May 11, 2018 at 2:35 PM, Justin Mclean wrote: > Hi, > >> hessian-lite-3.2.2.jar is a part of this release, both resource and binary >> should include hessian-lite. So now we need add clarification of >> hessian-lite in the LICENSE and NOTICE files in libs,

Re: Publishing Maven artifacts under third-party coordinates (was: Set up Nexus staging profile for Dubbo ...)

On Thu, May 10, 2018 at 9:50 AM, Julian Hyde wrote: > In other words, there are several ways to prove that a binary release is > WRONG but (to Greg’s point) there is no way to prove it RIGHT. That's actually a great way to put it. > As a mentor, I strongly advise against

Publishing Maven artifacts under third-party coordinates (was: Set up Nexus staging profile for Dubbo ...)

Hi all, I wanted to send a note that Infra has seen a couple requests from podlings to publish under third-party Maven groupId coordinates (com.alibaba and org.netbeans). Unless/until the Foundation owns these domains, we cannot allow publishing under those coordinates. Needless to say, we'll

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

+1 All UT passed with JDK 1.8 and JDK 9 on my mac. Some minor issues I meet: - When compile sources on JDK 10, a NPE is thrown by maven-javadoc-plugin:3.0.0, which is a known issue

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

+1 I have checked that the source release works fine: 1. All UT passed with JDK 1.7 2. All core features work fine with a certain amount of demos. 3. Review passed for changes mentioned in release notes. Best regards, Jun > On 15 May 2018, at 11:49 AM, Jun Liu wrote: > >

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

Hi, +1 I checked: - name includes incubating - signatures and hashes correct - disclaimer exists - LICENSE and NOTICE correct - No binary files in release - Can compile from source - The binary distribution (with different license and notice files) also looks good. Some minor problems could be

Re: Signing Apache ICLA to help Dubbo finish IP clearance process

邮件已发 王兵gmail 于2018年5月15日周二 下午3:34写道： > 你好，已经按照提示发了一个CLA邮件了 > > > > 2018-05-14 16:06 GMT+08:00 Huxing Zhang : > > > (Chinese after English) > > > > Hello, > > > > I am Huxing, I am committer and PMC member of Apache Dubbo(incubating). > > > > You have

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

Dear Dubbo Community, I am pleased to announce that the dubbo community has approved the release of 2.6.2. The vote has passed with: 5 binding "+1" votes, and 1 non-binding "+1" votes no "0" votes no "-1" votes The vote thread:

Re: GSoC student - Getting started.

This works Thanks. On Thu, May 17, 2018 at 2:15 AM Huxing Zhang wrote: > Is https://gitter.im/alibaba/dubbo ok for you? > > On Thu, May 17, 2018 at 2:08 PM, Raghunandana Jayarama Reddy > wrote: > > Hi Lei Wei, > > > > Thanks for all the

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

On 21/05/18 07:32, Jun Liu wrote: > we plan to solve this problem and start a new round of voting. Where did the community discuss this? I'd expect to see a discussion on a mailing list before a decision is announced. Mark

Re: [Discussion] About cancel vote for 2.6.2-RC1 and prepare RC2.

+1 On Tue, May 22, 2018 at 5:28 PM Wang Xin wrote: > +1 ， support to start the RC2 > Xin Wang > lovep...@hotmail.com > > > > 在 2018年5月22日，下午5:24，Huxing Zhang > 写道： > > +1 Looks good to me, let's do RC2. >

Re: [Discussion] About cancel vote for 2.6.2-RC1 and prepare RC2.

+1 ， support to start the RC2 Xin Wang lovep...@hotmail.com 在 2018年5月22日，下午5:24，Huxing Zhang > 写道： +1 Looks good to me, let's do RC2. On Tue, May 22, 2018 at 11:04 AM, Jun Liu

Re: [Discussion] About cancel vote for 2.6.2-RC1 and prepare RC2.

+1 Looks good to me, let's do RC2. On Tue, May 22, 2018 at 11:04 AM, Jun Liu wrote: > Hello community, > > We have asked the apache PMC members to review and vote on the 2.6.2 RC, > based on the feedbacks, especially those reported by Willem, Sebb, Ian and > Justin, we are

Donate dubbo-php-framework

Hello Dubbo community, We hava developed dubbo-php-framework which compatible with dubbo java. This framework include client , server and registry, it is a complete solution for micro-service on php platform, have running on our product environment for two years more. Now, we would like to

Re: Donate dubbo-php-framework

Hi, Welcome to the community! I think we still need to go through the ASF ip-clearance[1] process. But before that, it is better have your code available on Github. [1] http://incubator.apache.org/ip-clearance/ On Wed, May 23, 2018 at 11:03 AM, Yong Zhu wrote: > That's

Re: dubbo samples project

samples is very important especially for the beginner. I've already pinned the project. On Tue, May 22, 2018 at 2:42 PM Minxuan Zhuang wrote: > Hi all: >I'm writing to tell you that I have made a dubbo-sample project to > collect the examples of dubbo usage. At

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

> Using "I think we should ..." rather than "We plan..." (or something > along those lines) would make it clearer that it was your > idea/suggestion rather than a community decision. My apologies for the misleading and English fluency.  BTW, the discussion has started in Dubbo community:

Re: [Discussion] About cancel vote for 2.6.2-RC1 and prepare RC2.

If there’s no objections, i think we can start the new vote round 2 tomorrow. Best regards, Jun > On 22 May 2018, at 7:23 PM, Ian Luo wrote: > > +1 > > On Tue, May 22, 2018 at 5:28 PM Wang Xin wrote: > >> +1 ， support to start the RC2 >> Xin Wang >>

Re: [VOTE] Accept the "Dubbox documentation" donation

+1 On Thu, May 17, 2018 at 1:55 PM, Huxing Zhang wrote: > Hi All, > > Recently Dangdang has donated there documentation for dubbox[1], and a > software grant have been filed. > > As suggested by Justin, we need to follow the ASF ip clearance process. > > Therefore I am calling

Re: [VOTE] Accept the "Dubbox documentation" donation

Hi, The vote has passed with: * 5 binding "+1" votes * 1 non-binding "+1" votes * no "-1" votes Thanks everyone for the vote! I will proceed to general@. On Thu, May 17, 2018 at 2:29 PM, Ian Luo wrote: > +1 > > On Thu, May 17, 2018 at 1:55 PM Huxing Zhang

Re: [Discussion] About cancel vote for 2.6.2-RC1 and prepare RC2.

Hi, I think you need to send an email to cancel the vote on general@ formally before starting RC2. On Wed, May 23, 2018 at 4:08 PM, jun liu wrote: > If there’s no objections, i think we can start the new vote round 2 tomorrow. > > Best regards, > Jun > >> On 22 May 2018, at

Re: Donate dubbo-php-framework

That's great. Welcome to Dubbo community. Jerrick On Wed, May 23, 2018 at 10:49 AM, Ian Luo wrote: > Robin, > > It's awesome. We really need dubbo PHP implementation, and now it looks we > will have one soon :) You can put it in dubbo eco system which's hosted > under

Re: Donate dubbo-php-framework

Robin, It's awesome. We really need dubbo PHP implementation, and now it looks we will have one soon :) You can put it in dubbo eco system which's hosted under github.com/dubbo. Welcome to community. Cheers, -Ian. On Tue, May 22, 2018 at 8:49 PM robinkang(康彬)

Re: [Discuss] "develop" branch for incompatible or long-term developing features

I am generally agree with creating a new branch for incompatible changes. 1. But the naming of the branch looks inconsistent to me: * develop: 2.7.x * master: 2.6.x * 2.5.x: 2.5.x What about next major version, is there a branch called 2.8.x or 3.0.x? 2. should every pull request sent against

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

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

[Discuss] "develop" branch for incompatible or long-term developing features

I think we should create a new branch, for example “develop”, for the development of those upcoming incompatible or long-term features. By doing that, master branch and develop branch can evolve independently, and when develop branch is ready, it can be released with version 2.7.0, identifying

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

+1, this release looks better than RC1 -Ian. On Fri, May 25, 2018 at 11:02 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): >

Re: [Discuss] "develop" branch for incompatible or long-term developing features

good suggestion, it looks like we have to maintain two trunks. +1 On Fri, May 25, 2018 at 9:45 AM Jun Liu wrote: > I think we should create a new branch, for example “develop”, for the > development of those upcoming incompatible or long-term features. By doing > that, master

Re: GSoC student - Getting started.

Hi, Raghu Hope you are processing well on learning Dubbo. The Dubbo official documents and what I share to you should be helpful for you. According to the timeline of GSoC, we can go to the Coding step. Are you ready :) In order to have a good start, could you please provide a plan of your

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

Hi, +1 (binding) I checked: - Incubating in name - Signatures and hashes good - DISCLAIMER exists - LICENSE and NOTICE good - A number of pom.xml and log4j.xml files haven’t had their headers changed to the standard ASF one and are still copyright Alibaba (about 14 files) e.g [4][5] - A couple

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

Hi Justin, > Hash for the release tag: > afab04c53edab38d52275d2a198ea1aff7a4f41e It’s included in the initial vote email. > On 16 May 2018, at 10:44 AM, Justin Mclean wrote: > > HI, > >> I don’t think we need to change the release tag hash. Tag ‘dubbo-2.6.2’ has

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

> What do the owner / maintainers of hessian-lite think about that? Is there > any need to fork their version? Actually, the dubbo team is the official maintainer of hessian-lite, it’s always been published along side with dubbo. There are mainly 2 reasons for maintaining an additional

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

> Now we are considering that moving it to Dubbo eco-system, which is > https://github/dubbo. > > How do you think about this? I agree with moving hessian-lite to the dubbo eco-system. If we do that, we may need to upgrade the core dubbo version to 2.7.x to identify incompatible usage of

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

HI, > I don’t think we need to change the release tag hash. Tag ‘dubbo-2.6.2’ has > never changed, so the source release, binary release and the release tag are > still in consistent to each other. Be aware that CHANGES.md only exists in > the ‘2.6.2-release’ branch, a branch we used for

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

>>> Release Notes: >>> https://github.com/apache/incubator-dubbo/releases/tag/untagged-4775c0a22c60fca55118 >>> >>> >> >> Sorry, the previous link seems invisible for non-committers, please check >> the

Re: [VOTE] Accept the "Dubbox documentation" donation

+1 Xin Wang lovep...@hotmail.com 在 2018年5月17日，下午1:55，Huxing Zhang > 写道： Hi All, Recently Dangdang has donated there documentation for dubbox[1], and a software grant have been filed. As suggested by Justin, we need to

Re: GSoC student - Getting started.

Hi Lei Wei, Thanks for all the inputs. I was little busy finishing the semester which will end today. Can we have a slack channel/Hangouts chat window for instant messaging and updates. Thanks Raghu On Tue, May 15, 2018 at 10:55 PM Lei Wei wrote: > Hi, Raghu > > Hope you

Re: GSoC student - Getting started.

Is https://gitter.im/alibaba/dubbo ok for you? On Thu, May 17, 2018 at 2:08 PM, Raghunandana Jayarama Reddy wrote: > Hi Lei Wei, > > Thanks for all the inputs. > I was little busy finishing the semester which will end today. > Can we have a slack channel/Hangouts

Re: [VOTE] Accept the "Dubbox documentation" donation

+1 to accept the documentation. Except for the ip clearance, we may need to reorganize the doc to fit current official doc styles. Best regards, Jun > On 17 May 2018, at 1:55 PM, Huxing Zhang wrote: > > Hi All, > > Recently Dangdang has donated there documentation for

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

+1 This release looks good. We could follow up the minor issues Justin and others point out in the next release. Cheers, -Ian. On Tue, May 15, 2018 at 11:49 AM Jun Liu wrote: > Hello Dubbo Community, > > This is a call for vote to release Apache Dubbo (Incubating) version

Re: [VOTE] Accept the "Dubbox documentation" donation

+1 On Thu, May 17, 2018 at 1:55 PM Huxing Zhang wrote: > Hi All, > > Recently Dangdang has donated there documentation for dubbox[1], and a > software grant have been filed. > > As suggested by Justin, we need to follow the ASF ip clearance process. > > Therefore I am calling

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

Please do it since 2.7.x! 在 2018/5/16 上午11:11, Jun Liu 写道: Now we are considering that moving it to Dubbo eco-system, which is https://github/dubbo. How do you think about this? I agree with moving hessian-lite to the dubbo eco-system. If we do that, we may need to upgrade the core dubbo

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

Hi, I did some check on the source zip and binary zip, the License and Notice files looks good. But I also found some issues here. As I cannot build the binary without doing some changes on the pom file, I had to vote -1 (binding) here. Here are the issues that I found: 1. there is bunch of

[Discussion] About cancel vote for 2.6.2-RC1 and prepare RC2.

Hello community, We have asked the apache PMC members to review and vote on the 2.6.2 RC, based on the feedbacks, especially those reported by Willem, Sebb, Ian and Justin, we are planning to prepare RC2 and start a new round of vote. Compared to RC1, RC2 plans to fix the following issues: -

dubbo samples project

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

Re: dubbo samples project

Here should be with applause. On Tue, May 22, 2018 at 2:42 PM, Minxuan Zhuang wrote: > Hi all: >I'm writing to tell you that I have made a dubbo-sample project to > collect the examples of dubbo usage. At present, there are 19 samples, the > github address is

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

> 1. there is bunch of dubbo-2.6.2-SNAPSHOT in the pom.xml file, I guess the > maven release plugin doesn't take all of them. > .//bom/pom.xml: dubbo-2.6.2-SNAPSHOT > .//dependencies-bom/pom.xml: dubbo-2.6.2-SNAPSHOT > .//distribution/pom.xml:2.6.2-SNAPSHOT-SNAPSHOT >

  1   2   3   4   5   6   7   8   9   10   >