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

2018-05-14 Thread Jun Liu
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:
https://github.com/apache/incubator-dubbo/tree/dubbo-2.6.2 


Hash for the release tag:
afab04c53edab38d52275d2a198ea1aff7a4f41e

Release Notes:
https://github.com/apache/incubator-dubbo/releases/tag/untagged-4775c0a22c60fca55118
 


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,
The Apache Dubbo (Incubating) Team

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

2018-05-14 Thread Bertrand Delacretaz
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 binary with sha256 digest XYZ and it works for me" - but
that doesn't make the Apache Releases, they are still unverifiable
binaries regardless.

-Bertrand


Signing Apache ICLA to help Dubbo finish IP clearance process

2018-05-14 Thread 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 before. Please refer to [1][2] for more
details.

Since Dubbo has been donated to Apache Software Foundation, one
required process is to ensure the intellectual property of each
contribution has been correctly transferred to ASF. To help Dubbo to finish the
process, would you please sign the ICLA for Dubbo? You can follow the
guide [3].

If you have any further questions, please drop me a message.

Thanks in advance!


===
您好,

我是来自Dubbo团队的张乎兴,您之前给Dubbo贡献过代码,但是没有签署过贡献者许可协议,您可以从[1][2]中了解更多的内容。

目前Dubbo正在Apache基金会孵化,其中一项流程是对软件的知识产权进行清理,确保您之前贡献的代码正确的转移给Apache基金会,在此烦请您协助Dubbo社区完成贡献者许可协议的签署工作,具体的步骤请参考文档[3]中提供的内容。

如果有任何问题,请通过邮件或者微信(ralf0131)联系我。

此致,
敬礼!


[1] https://issues.apache.org/jira/browse/DUBBO-3
[2] https://github.com/apache/incubator-dubbo/wiki/CLA-signing-status
[3] https://github.com/apache/incubator-dubbo/wiki/CLA-signing-guide

-- 
Best Regards!
Huxing


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

2018-05-14 Thread Wang Xin
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



在 2018年5月14日,下午2:42,shang zonghai 
> 写道:

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


在 2018年5月11日,16:02,Justin Mclean 
> 写道:

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 about that? Is there any need to fork their version? Can you just use 
their released version?

Thanks,
Justin




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

2018-05-14 Thread shang zonghai
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


> 在 2018年5月11日,16:02,Justin Mclean  写道:
> 
> 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 about that? Is there any need to fork their version? Can you just use 
> their released version?
> 
> Thanks,
> Justin