You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@dubbo.apache.org by Jun Liu <li...@apache.org> on 2018/03/14 07:53:40 UTC
Prepare for release of v2.6.1
Hi, community
We are planning the release of v2.6.1, mainly includes the following changes:
1. Refactor
Stripping OPS modules such as dubbo-admin, dubbo-monitor, etc. to a separate repo.
Refactor project dependency and package structure: serialization as a standalone module, all submodules can deploy to remote repository separately.
2. Enhancements
Support build in java 9.
Avoid blocking problems of hessian serailization in high concurrency scenarios.
Change default ZK client to "curator".
Route rule match "default.key" conditions.
Avoid retry when parameter validation fails.
Remove dubbo destroy logic from spring bean destroy process.
3. Bugfixes
Fix offline problem of redis & multicast registry.
Add "oninvoke" parse.
Other small bugfixes.
This version has been prepared on github for quite a while, and is the first release after refactor of project structure.
Please feel free to reply to this email if you have any questions or suggestions.
Best regards,
Jun Liu
Re: Prepare for release of v2.6.1
Posted by Jun Liu <li...@apache.org>.
Hi, community
Release of v2.6.1 done. Happy to enjoy the new way of adding dubbo features to your project: https://github.com/alibaba/dubbo/issues/1322 <https://github.com/alibaba/dubbo/issues/1322>
Any new ideas for dubbo, please send to this mail list for discussion, and we'll finish it in the next version with a totally new apache release journey.
Best regards,
Jun
Re: Prepare for release of v2.6.1
Posted by Jun Liu <li...@apache.org>.
Actually, the release is on progress now and is expected to be done today, this release is for some planned features and problem fixes. I did not expect the repository transfer to be completed so quickly, but it’s a goods news anyway.
Best regards,
Jun
> On 16 Mar 2018, at 5:34 PM, Von Gosling <vo...@apache.org> wrote:
>
> Hi,
>
> I would like to recommend that we’d better to finish the repository transfer and some other necessary polish before the first release. Any questions for that process, my pleasure to help :-)
>
> Best Regards,
> Von Gosling
>
>> 在 2018年3月16日，17:06，Huxing Zhang <hu...@apache.org> 写道：
>>
>> Hi,
>>
>> As we are going to move the repo to Apache, will that block your release?
>>
>>
>> On Wed, Mar 14, 2018 at 4:24 PM, Justin Mclean <ju...@me.com> wrote:
>>> Hi,
>>>
>>>> I have learned in the previous mail that we can still release as usual before transfer to apache officially. An official Apache release should follow another process, right?
>>>
>>> Yep all good.
>>>
>>> Thanks,
>>> Justin
>>
>> --
>> Best Regards！
>> Huxing
>
Re: Prepare for release of v2.6.1
Posted by Von Gosling <vo...@apache.org>.
Hi,
I would like to recommend that we’d better to finish the repository transfer and some other necessary polish before the first release. Any questions for that process, my pleasure to help :-)
Best Regards,
Von Gosling
> 在 2018年3月16日，17:06，Huxing Zhang <hu...@apache.org> 写道：
>
> Hi,
>
> As we are going to move the repo to Apache, will that block your release?
>
>
> On Wed, Mar 14, 2018 at 4:24 PM, Justin Mclean <ju...@me.com> wrote:
>> Hi,
>>
>>> I have learned in the previous mail that we can still release as usual before transfer to apache officially. An official Apache release should follow another process, right?
>>
>> Yep all good.
>>
>> Thanks,
>> Justin
>
> --
> Best Regards！
> Huxing
Re: Prepare for release of v2.6.1
Posted by Justin Mclean <ju...@me.com>.
Hi,
> As we are going to move the repo to Apache, will that block your release?
I don’t believe so. As long as it not advertised as an Apache release IMO all is good.
Thanks,
Justin
Re: Prepare for release of v2.6.1
Posted by Huxing Zhang <hu...@apache.org>.
Hi,
As we are going to move the repo to Apache, will that block your release?
On Wed, Mar 14, 2018 at 4:24 PM, Justin Mclean <ju...@me.com> wrote:
> Hi,
>
>> I have learned in the previous mail that we can still release as usual before transfer to apache officially. An official Apache release should follow another process, right?
>
> Yep all good.
>
> Thanks,
> Justin
--
Best Regards！
Huxing
Re: Prepare for release of v2.6.1
Posted by Justin Mclean <ju...@me.com>.
Hi,
> I have learned in the previous mail that we can still release as usual before transfer to apache officially. An official Apache release should follow another process, right?
Yep all good.
Thanks,
Justin
Re: Prepare for release of v2.6.1
Posted by jun liu <ke...@gmail.com>.
No, it isn’t.
I have learned in the previous mail that we can still release as usual before transfer to apache officially. An official Apache release should follow another process, right?
> On 14 Mar 2018, at 4:08 PM, Justin Mclean <ju...@classsoftware.com> wrote:
>
> HI,
>
> This is not going o be an official Apache release is it?
>
> Thanks,
> Justin
Re: Prepare for release of v2.6.1
Posted by Justin Mclean <ju...@classsoftware.com>.
HI,
This is not going o be an official Apache release is it?
Thanks,
Justin