Re: [Discuss]Prepare for the next release v2.6.4
Jerrik, I would like to work closely with you for the next release. Please refer the “Prepare an Apache Release” blog[1] I’ve wrote down during the first two releases for help, the complete ASF release guide links are also posted there for your reference. Help to improve it if necessary. 1. http://dubbo.apache.org/en-us/blog/prepare-an-apache-release.html Best regards, Jun > On 13 Sep 2018, at 18:30, Jerrick Zhu wrote: > > That's cool. I'll take it for 2.6.4. > > On Thu, Sep 13, 2018 at 5:55 PM Justin Mclean > wrote: > >> Hi, >> >>> Yes, I think we need a new manager to do the next release, to get >> familiar with and improve the release process. >>> But I'm not sure if anyone has committer privilege is allowed to be the >> release manager or only PMCs are allowed. >> >> Anyone can be a release manager, but in practical term you need to be a >> committer or PMC member in order to get stuff done. >> >> Thanks, >> Justin
Re: [Discuss]Prepare for the next release v2.6.4
On Thu, Sep 13, 2018 at 6:30 PM Jerrick Zhu wrote: > > That's cool. I'll take it for 2.6.4. Great! Please go head, the PPMC will help to do the privileged stuff if needed. > > On Thu, Sep 13, 2018 at 5:55 PM Justin Mclean > wrote: > > > Hi, > > > > > Yes, I think we need a new manager to do the next release, to get > > familiar with and improve the release process. > > > But I'm not sure if anyone has committer privilege is allowed to be the > > release manager or only PMCs are allowed. > > > > Anyone can be a release manager, but in practical term you need to be a > > committer or PMC member in order to get stuff done. > > > > Thanks, > > Justin -- Best Regards！ Huxing
Re: [Discuss]Prepare for the next release v2.6.4
That's cool. I'll take it for 2.6.4. On Thu, Sep 13, 2018 at 5:55 PM Justin Mclean wrote: > Hi, > > > Yes, I think we need a new manager to do the next release, to get > familiar with and improve the release process. > > But I'm not sure if anyone has committer privilege is allowed to be the > release manager or only PMCs are allowed. > > Anyone can be a release manager, but in practical term you need to be a > committer or PMC member in order to get stuff done. > > Thanks, > Justin
Re: [Discuss]Prepare for the next release v2.6.4
Hi, > Yes, I think we need a new manager to do the next release, to get familiar > with and improve the release process. > But I'm not sure if anyone has committer privilege is allowed to be the > release manager or only PMCs are allowed. Anyone can be a release manager, but in practical term you need to be a committer or PMC member in order to get stuff done. Thanks, Justin
Re: [Discuss]Prepare for the next release v2.6.4
On Wed, Sep 12, 2018 at 9:44 AM Huxing Zhang wrote: > On Mon, Sep 10, 2018 at 10:35 AM Jun Liu wrote: > > > > > Do you think we need another one to be the release manager? In case > > > that we can make sure our release guide works perfectly. > > > > Yes, I think we need a new manager to do the next release, to get > familiar with and improve the release process. > > Is anyone who volunteers to be the release manager? > If it's allowed and no others, I'll take it. But I need Jun's help. > > > But I'm not sure if anyone has committer privilege is allowed to be the > release manager or only PMCs are allowed. > > I checked the release policy [1], it seems no requirement for non-PMC > member to be release manager. > > > If the Release Manager is not a member of the PMC, they will need to ask > a PMC member to do the actual release publication. > > > [1] http://www.apache.org/legal/release-policy.html#upload-ci > > > > > Best regards, > > Jun > > > > > On 7 Sep 2018, at 23:42, Huxing Zhang wrote: > > > > > > Hi, > > > > > > On Sat, Sep 1, 2018 at 4:18 PM Jun Liu 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. > > > > > > Do you think we need another one to be the release manager? In case > > > that we can make sure our release guide works perfectly. > > > > > >> > > >> Best regards, > > >> Jun > > >> > > > > > > > > > -- > > > Best Regards！ > > > Huxing > > > > > -- > Best Regards！ > Huxing >
Re: [Discuss]Prepare for the next release v2.6.4
On Mon, Sep 10, 2018 at 10:35 AM Jun Liu wrote: > > > Do you think we need another one to be the release manager? In case > > that we can make sure our release guide works perfectly. > > Yes, I think we need a new manager to do the next release, to get familiar > with and improve the release process. Is anyone who volunteers to be the release manager? > But I'm not sure if anyone has committer privilege is allowed to be the > release manager or only PMCs are allowed. I checked the release policy [1], it seems no requirement for non-PMC member to be release manager. > If the Release Manager is not a member of the PMC, they will need to ask a > PMC member to do the actual release publication. [1] http://www.apache.org/legal/release-policy.html#upload-ci > > Best regards, > Jun > > > On 7 Sep 2018, at 23:42, Huxing Zhang wrote: > > > > Hi, > > > > On Sat, Sep 1, 2018 at 4:18 PM Jun Liu 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. > > > > Do you think we need another one to be the release manager? In case > > that we can make sure our release guide works perfectly. > > > >> > >> Best regards, > >> Jun > >> > > > > > > -- > > Best Regards！ > > Huxing > -- Best Regards！ Huxing
Re: [Discuss]Prepare for the next release v2.6.4
> Do you think we need another one to be the release manager? In case > that we can make sure our release guide works perfectly. Yes, I think we need a new manager to do the next release, to get familiar with and improve the release process. But I'm not sure if anyone has committer privilege is allowed to be the release manager or only PMCs are allowed. Best regards, Jun > On 7 Sep 2018, at 23:42, Huxing Zhang wrote: > > Hi, > > On Sat, Sep 1, 2018 at 4:18 PM Jun Liu 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. > > Do you think we need another one to be the release manager? In case > that we can make sure our release guide works perfectly. > >> >> Best regards, >> Jun >> > > > -- > Best Regards！ > Huxing
Re: [Discuss]Prepare for the next release v2.6.4
Hi, On Sat, Sep 1, 2018 at 4:18 PM Jun Liu 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. Do you think we need another one to be the release manager? In case that we can make sure our release guide works perfectly. > > Best regards, > Jun > -- Best Regards！ Huxing
Re: [Discuss]Prepare for the next release v2.6.4
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 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 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 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 >> > >> >>
Re: [Discuss]Prepare for the next release v2.6.4
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 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 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 > > > >
Re: [Discuss]Prepare for the next release v2.6.4
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 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 >
