Re: [Suggestion] Add maven wrapper

[修宇航]

+1
I have submit a pull request to add it:

https://github.com/apache/incubator-dubbo/pull/1887/files

Also use maven wrapper to complete travis-ci.

[ANNOUNCE] Apache Dubbo talk at June 25--26 in LC3, Beijing China

[Huxing Zhang]

Hi all,

There will be one Dubbo talk at "LinuxCon + ContainerCon +
CloudOpen2018, June 25--26, Beijing, China".

In this presentation, Liu Jun will give a brief introduction of the
core features of Dubbo and its innovation in RPC area, review the
recent events in meeting community requirements and enhancing dubbo,
the challenges it faces, and the roadmap to address those challenges
after entered apache community.

Title: Dubbo Open-Sourcing - Present and the Future
Time: Monday, June 25 • 15:50 - 16:30
Details: 
https://lc32018.sched.com/event/ERAo/dubbo-open-sourcing-present-and-the-future-liu-jun-alibaba

-- 
Best Regards！
Huxing

[DRAFT] Dubbo Incubator Report - June 2018

[Huxing Zhang]

Hi Dubbo Community,

Below is a draft of Dubbo Incubator Report, June 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 move towards graduation:

  1. First release
  2. Community building
  3. Change group id to org.apache

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
None.

How has the community developed since the last report?
  * Complete All ICLA collection for all the contributors which are
necessary to have
  * The first Apache release 2.6.2 has passed the incubator community vote
  * zonghaishang(yiji) has been voted as new committer
  * The first Dubbo meetup has been held in Beijing, with over 400+
people attended
  * 10 new companies reported their using of Dubbo since last report

How has the project developed since the last report?
  * 2.6.2 is ready to release
  * The community has decided to a new major version 2.7.x to
incorporate incompatible changes.
  * 57 Active Pull Requests, 49 pull request merged, with 21
contributors involved
  * 180 Active Issues,  127 issues closed

How would you assess the podling's maturity?
Please feel free to add your own commentary.

  [  ] Initial setup
  [ X ] Working towards first release
  [ X ] Community building
  [ ] Nearing graduation
  [ ] Other:

Date of last release:
None. (2.6.2 has passed incubator community release vote and is
expected to be release with several days)

When were the last committers or PPMC members elected?
2018-06-01.

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

[Jun Liu]

> I strongly recommend that you include the full fingerprint of the
> signing KEY in the KEYS file as well as the key ID. See [1] for an
> example where some of the keys have this. A few years ago an attack was
> demonstrated ([2], [3]) that show it was possible to create collisions
> in the key ID. Using the full fingerprint mitigates this attack.

The KEYS file I have updated with the full fingerprint added.

> No concerns with the file name used. Just a comment that the usual
> naming convention would be:
> apache-dubbo-incubating-2.6.2-src.zip

Will follow the naming convention for the next release.

> I'd suggest including the .gitignore file in the src release.

Will also add in the next release.

> I was a little surprised that the binary bundle was just the JARs rather
> than something that a user could unpack and run via dubbo.sh /
> dubbo.bat. There isn't anything wring with this, just not what I am used to.

Sure it would better be a packet for users to start Dubbo journey quickly, for 
example, packed samples or quick start guides which can be started by a 
start.sh. We are preparing for these samples and plan to replace current binary 
release in the next release.

Best regards,
Jun

> On 4 Jun 2018, at 4:05 PM, Mark Thomas  wrote:
> 
> Checks:
> 
> Source bundle:
> - Hash and signature are correct
> - Hash of tag matches the hash quoted in the release vote mail
> - Contents of git tag match src bundle except for .gitignore file
> - Maven build passes
> - LICENSE and NOTICE look correct for source bundle
> - LICENSE and NOTICE look correct for binary bundle
> 
> +1 to release
> 
> 
> 
> I have the following minor review comments (none of which warrant
> another RC):
> 
> I strongly recommend that you include the full fingerprint of the
> signing KEY in the KEYS file as well as the key ID. See [1] for an
> example where some of the keys have this. A few years ago an attack was
> demonstrated ([2], [3]) that show it was possible to create collisions
> in the key ID. Using the full fingerprint mitigates this attack.
> 
> No concerns with the file name used. Just a comment that the usual
> naming convention would be:
> apache-dubbo-incubating-2.6.2-src.zip
> 
> I'd suggest including the .gitignore file in the src release.
> 
> I was a little surprised that the binary bundle was just the JARs rather
> than something that a user could unpack and run via dubbo.sh /
> dubbo.bat. There isn't anything wring with this, just not what I am used to.
> 
> Mark
> 
> 
> [1] https://dist.apache.org/repos/dist/release/tomcat/tomcat-9/KEYS
> [2] http://pgp.mit.edu/pks/lookup?op=get=0x10C01C5A2F6059E7
> [3] http://pgp.mit.edu/pks/lookup?op=get=0xB6FB7A022F6059E7
> 
> On 29/05/18 09:47, Jun Liu wrote:
>> Hello All,
>> 
>> This is a call for vote to release Apache Dubbo (Incubating) version 2.6.2.
>> 
>> The Apache Dubbo community has voted on and approved a proposal to release 
>> Apache Dubbo (Incubating) version 2.6.2.
>> 
>> We now kindly request the Incubator PMC members review and vote on this 
>> incubator release.
>> 
>> Apache Dubbo™ (incubating) is a high-performance, java based, open source 
>> RPC framework. Dubbo offers three key functionalities, which include 
>> interface based remote call, fault tolerance & load balancing, and automatic 
>> service registration & discovery. 
>> 
>> Dubbo vote thread:
>> https://lists.apache.org/thread.html/38560cb159a5c32d0cf98485c9fe791505fbc52d18d86a37713582f0@%3Cdev.dubbo.apache.org%3E
>>  
>> 
>> 
>> Dubbo vote result thread:
>> https://lists.apache.org/thread.html/0b1e022a32e136ff0a9b42e7ef7da5ccc7d256d175394c2d5858f1cf@%3Cdev.dubbo.apache.org%3E
>>  
>> 
>> 
>> The release candidates:
>> https://dist.apache.org/repos/dist/dev/incubator/dubbo/2.6.2 
>> 
>> 
>> Git tag for the release:
>> https://github.com/apache/incubator-dubbo/tree/dubbo-2.6.2 
>>  
>> 
>> Hash for the release tag:
>> 5eeb240337ccfbc820d4bde023d8cf643f33d735
>> 
>> Release Notes:
>> https://github.com/apache/incubator-dubbo/blob/2.6.2-release/CHANGES.md 
>> 
>> 
>> The artifacts have been signed with Key : 28681CB1, which can be found in 
>> the keys file:
>> https://dist.apache.org/repos/dist/dev/incubator/dubbo/KEYS 
>> 
>> 
>> The vote will be open for at least 72 hours or until necessary number of 
>> votes are reached.
>> 
>> Please vote accordingly:
>> [ ] +1 approve 
>> [ ] +0 no opinion 
>> [ ] -1 disapprove with the reason
>> 
>> Thanks.
>> Jun Liu,
>> on behalf of The Apache Dubbo 

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

[jun liu]

Hi All,

According to the discussion, I will create a new branch 2.6.x from the master 
and update master to 2.7.0-SNAPSHOT:
* master: 2.7.x
* 2.6.x: 2.6.x
* 2.5.x: 2.5.x

Since 2.5.x is basically compatible with 2.6.x, it seems to be an unnecessary 
version differentiation. So I think we should announce the EOL deadline of 
2.5.x shortly.

Keeping two mutually incompatible versions evolve at the same time will 
inevitably bring additional workload to the Dubbo team. So we may need to 
figure out which patch goes against which branch beforehand. For example, new 
features and incompatible changes only occur in 2.7.x, while enhancements or 
bugfixes going to both versions.

Best regards,
Jun

> On 28 May 2018, at 10:15 PM, Huxing Zhang  wrote:
> 
> Hi,
> 
> On Mon, May 28, 2018 at 9:08 PM, Jun Liu  > wrote:
>>> 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?
>> 
>> Or how about separate 2.6.x from master, and start 2.7.x directly on master? 
>>  The branches would look like:
>> 
>> * master: 2.7.x
>> * 2.6.x: 2.6.x
>> * 2.5.x: 2.5.x
> 
> This looks better, master will always be the latest version.
> 
>> 
>>> 2. should every pull request sent against 2.7.x and be back ported to 2.6.x?
>> 
>> I think it will be up to us to decide which commit should be merged into the 
>> other branches and need to be done manually.
> 
> There should be a rule to guide contributors that which branch their
> pull request should be sent against.
> 
> For example, if a pull request is a general fix/enhancement, it should
> be sent against 2.7.x. On the other hand, if the fix/enhancement is
> specific to some branch, it should be sent against that specific
> branch.
> 
> Maybe we should also update the new contributor guide after the
> decision is made.
> 
>> 
>> Best regards,
>> Jun
>> 
>>> On 25 May 2018, at 5:19 PM, Huxing Zhang  wrote:
>>> 
>>> 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 2.7.x and be back ported to 2.6.x?
>>> 
>>> On Fri, May 25, 2018 at 2:41 PM, Ian Luo  wrote:
 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 branch and develop branch can evolve independently, and when
> develop branch is ready, it can be released with version 2.7.0, 
> identifying
> the incompatibility with 2.6.x.
> 
> Here’s some works i think need to start on a new branch:
> - Support for java 8 or higher.
> - Package renaming required in Apache IP Clearance.
> - Transfer some extensions to Dubbo eco-system[1][2].
> - Some in compatible or long-term developing features: async api, metadata
> refactor, modularization…[3][4]
> 
> 1. https://github.com/dubbo 
> 2.
> https://lists.apache.org/thread.html/a5e5e1a09cb15b1d508cf22ce2bd674ddc915ffbfe16dda55dbc90ac@%3Cdev.dubbo.apache.org%3E
> <
> https://lists.apache.org/thread.html/a5e5e1a09cb15b1d508cf22ce2bd674ddc915ffbfe16dda55dbc90ac@%3Cdev.dubbo.apache.org%3E
>> 
> 3. https://issues.apache.org/jira/browse/DUBBO-22 <
> https://issues.apache.org/jira/browse/DUBBO-22>
> 4. https://issues.apache.org/jira/browse/DUBBO-24 <
> https://issues.apache.org/jira/browse/DUBBO-24>
> 
> Best regards,
> Jun
>>> 
>>> --
>>> Best Regards！
>>> Huxing
>> 
> 
> 
> 
> -- 
> Best Regards！
> Huxing

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

[Mark Thomas]

On 04/06/18 08:14, Huxing Zhang wrote:
> Dear Dubbo Mentors,
> 
> We still need 1 more binding vote to pass the incubator community vote.
> 
> It will be great if we can pass it before the June's podling report.
> 
> Would you please help to vote for it?

I'm reviewing the release now.

Mark


> 
> On Tue, May 29, 2018 at 4:47 PM, Jun Liu  wrote:
>> Hello All,
>>
>> This is a call for vote to release Apache Dubbo (Incubating) version 2.6.2.
>>
>> The Apache Dubbo community has voted on and approved a proposal to release 
>> Apache Dubbo (Incubating) version 2.6.2.
>>
>> We now kindly request the Incubator PMC members review and vote on this 
>> incubator release.
>>
>> Apache Dubbo™ (incubating) is a high-performance, java based, open source 
>> RPC framework. Dubbo offers three key functionalities, which include 
>> interface based remote call, fault tolerance & load balancing, and automatic 
>> service registration & discovery.
>>
>> Dubbo vote thread:
>> https://lists.apache.org/thread.html/38560cb159a5c32d0cf98485c9fe791505fbc52d18d86a37713582f0@%3Cdev.dubbo.apache.org%3E
>>  
>> 
>>
>> Dubbo vote result thread:
>> https://lists.apache.org/thread.html/0b1e022a32e136ff0a9b42e7ef7da5ccc7d256d175394c2d5858f1cf@%3Cdev.dubbo.apache.org%3E
>>  
>> 
>>
>> The release candidates:
>> https://dist.apache.org/repos/dist/dev/incubator/dubbo/2.6.2 
>> 
>>
>> Git tag for the release:
>> https://github.com/apache/incubator-dubbo/tree/dubbo-2.6.2 
>> 
>>
>> Hash for the release tag:
>> 5eeb240337ccfbc820d4bde023d8cf643f33d735
>>
>> Release Notes:
>> https://github.com/apache/incubator-dubbo/blob/2.6.2-release/CHANGES.md 
>> 
>>
>> The artifacts have been signed with Key : 28681CB1, which can be found in 
>> the keys file:
>> https://dist.apache.org/repos/dist/dev/incubator/dubbo/KEYS 
>> 
>>
>> The vote will be open for at least 72 hours or until necessary number of 
>> votes are reached.
>>
>> Please vote accordingly:
>> [ ] +1 approve
>> [ ] +0 no opinion
>> [ ] -1 disapprove with the reason
>>
>> Thanks.
>> Jun Liu,
>> on behalf of The Apache Dubbo (Incubating) Team
> 

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

[Yong Zhu]

After discussing, we are about to do this in next major version, which is
2.7.x.

The corresponding issue has also been created on github:
https://github.com/apache/incubator-dubbo/issues/1778

On Thu, May 17, 2018 at 2:29 PM, Mercy  wrote:

> 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 version to 2.7.x to identify
>> incompatible usage of dependencies.
>>
>> On 11 May 2018, at 3:57 PM, Yong Zhu  wrote:
>>>
>>> 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 Dubbo eco-system, which is
>>> https://github/dubbo.
>>>
>>> How do you think about this?
>>>
>>> Thanks.
>>> Jerrick
>>>
>>
>

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

[Huxing Zhang]

Dear Dubbo Mentors,

We still need 1 more binding vote to pass the incubator community vote.

It will be great if we can pass it before the June's podling report.

Would you please help to vote for it?

On Tue, May 29, 2018 at 4:47 PM, Jun Liu  wrote:
> Hello All,
>
> This is a call for vote to release Apache Dubbo (Incubating) version 2.6.2.
>
> The Apache Dubbo community has voted on and approved a proposal to release 
> Apache Dubbo (Incubating) version 2.6.2.
>
> We now kindly request the Incubator PMC members review and vote on this 
> incubator release.
>
> Apache Dubbo™ (incubating) is a high-performance, java based, open source RPC 
> framework. Dubbo offers three key functionalities, which include interface 
> based remote call, fault tolerance & load balancing, and automatic service 
> registration & discovery.
>
> Dubbo vote thread:
> https://lists.apache.org/thread.html/38560cb159a5c32d0cf98485c9fe791505fbc52d18d86a37713582f0@%3Cdev.dubbo.apache.org%3E
>  
> 
>
> Dubbo vote result thread:
> https://lists.apache.org/thread.html/0b1e022a32e136ff0a9b42e7ef7da5ccc7d256d175394c2d5858f1cf@%3Cdev.dubbo.apache.org%3E
>  
> 
>
> The release candidates:
> https://dist.apache.org/repos/dist/dev/incubator/dubbo/2.6.2 
> 
>
> Git tag for the release:
> https://github.com/apache/incubator-dubbo/tree/dubbo-2.6.2 
> 
>
> Hash for the release tag:
> 5eeb240337ccfbc820d4bde023d8cf643f33d735
>
> Release Notes:
> https://github.com/apache/incubator-dubbo/blob/2.6.2-release/CHANGES.md 
> 
>
> The artifacts have been signed with Key : 28681CB1, which can be found in the 
> keys file:
> https://dist.apache.org/repos/dist/dev/incubator/dubbo/KEYS 
> 
>
> The vote will be open for at least 72 hours or until necessary number of 
> votes are reached.
>
> Please vote accordingly:
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove with the reason
>
> Thanks.
> Jun Liu,
> on behalf of The Apache Dubbo (Incubating) Team

-- 
Best Regards！
Huxing