All the features are as follow:

1. #2303 Change consumer retries default value from 0 to 2.  After release,
need to correct the docs on website
2. #2024 Fix the problem that attachment is lost when retry
3. #2166 Add ip and application name for MonitorService
4. #2146 Support access Redis with password
5. #2137 Support char array for GenericService
6. #2402 New ASCII logo for Dubbo
7. #2451 Direct return when the server goes down abnormally
8. #2453 Fix NPE when telnet get a null param
9. #2455 Add log when qos start fail

Check here for more infos.
https://github.com/apache/incubator-dubbo/issues/2305

On Wed, Sep 5, 2018 at 2:41 PM Jerrick Zhu <jerr...@apache.org> wrote:

> I've listed all the big changes of 2.6.x since the release of 2.6.3, check
> this issue: https://github.com/apache/incubator-dubbo/issues/2305
>
> Also, there has many issues related to 2.6.4 in the milestone 19, I
> suggest the community take some time to check them, some of them need to be
> fixed in 2.6.4 and others need to be deferred to 2.6.5 or close.
>
> On Sat, Sep 1, 2018 at 4:20 PM Jun Liu <liu...@apache.org> wrote:
>
>> The missed links:
>> 1. https://github.com/apache/incubator-dubbo/tree/2.6.x
>> 2. https://github.com/apache/incubator-dubbo/milestone/19
>>
>> Best regards,
>> Jun
>>
>> > On 1 Sep 2018, at 16:18, Jun Liu <liu...@apache.org> wrote:
>> >
>> > Hi, Community,
>> >
>> > I think it’s time to start preparing for the release of the 2.6.4
>> version now. The vote of v2.6.3 has lasted for nearly a month and we can
>> expect it to be released in the next two weeks if it can pass the Apache
>> community vote later. During such a relatively long period of time, I have
>> seen some important patches being merged into branch 2.6.x[1], some issues
>> need to be fixed most of which are collected from users/developers in
>> community are included in milestone 2.6.4[2].
>> >
>> > Counting the time needed to address all these issues and the time we
>> have to wait for the voting, let's speed up the progress of v2.6.4.
>> >
>> > Best regards,
>> > Jun
>> >
>>
>>

Reply via email to