Re: [VOTE]: Release Apache Dubbo 2.7.3 [RC3]

2019-07-14 Thread YunKun Huang
+1 approve I have checked: * Can compile from source * Run with dubbo-sample, all checks pass There is one question for CHANGES file format. Usually changes information are spilt into `New Features`, `Enhancement`, `Bugfixes`, should we keep to use this format? On Sat, Jul 13, 2019 at 10:10 AM J

Re: github 上的dubbo fork之后怎么变成了dubbox

2019-07-14 Thread Huxing Zhang
Hi, This is highly impossible. Could you give the link to the forked repo? On Sun, Jul 14, 2019 at 9:58 AM 李广 wrote: > > github 上的dubbo fork之后怎么变成了dubbox > -- Best Regards! Huxing

Re: [VOTE]: Release Apache Dubbo 2.7.3 [RC3]

2019-07-14 Thread Ian Luo
+1 approve [v] Are release files in correct location? [v] Are the digital signature and hashes correct? [v] Do LICENSE and NOTICE files exists? [v] Is the LICENSE and NOTICE text correct? [v] Is the NOTICE year correct? [v] Un-included software dependencies are not mentioned in LICENSE or NOTICE?

Re: [VOTE]: Release Apache Dubbo 2.6.7 [RC1]

2019-07-14 Thread Ian Luo
Good to know, thank you, Justin. Regards, -Ian. On Thu, Jul 11, 2019 at 12:01 PM Justin Mclean wrote: > Hi, > > > I cannot find DISCLAIMER file in the source distribution. > > Dubbo is a top level project now and doesn’t need a disclaimer :-) > > Thanks, > Justin

Re: [VOTE]: Release Apache Dubbo 2.7.3 [RC3]

2019-07-14 Thread Jun Liu
https://repository.apache.org/content/repositories/orgapachedubbo-1035/ Above is the staging repo of maven binary artifacts. Jun > On Jul 15, 2019, at 10:16 AM, Ian Luo wrote: > > +1 approve > > [v] Are release files in correct location? > [v] Are the digital signature and hashes correct? >

Re: [VOTE]: Release Apache Dubbo 2.7.3 [RC3]

2019-07-14 Thread Huxing Zhang
Hi, On Sun, Jul 14, 2019 at 4:20 PM YunKun Huang wrote: > > +1 approve > > I have checked: > * Can compile from source > * Run with dubbo-sample, all checks pass > > There is one question for CHANGES file format. Usually changes information > are spilt into `New Features`, `Enhancement`, `Bugfixe

Re: [VOTE]: Release Apache Dubbo 2.7.3 [RC3]

2019-07-14 Thread Huxing Zhang
Hi I vote with: +1 release the software Minor issue: binary distribution is not release this time, as the license file has not been updated yet. Whether or not to do binary distribution remains a question to be discussed. [YES] Are release files in correct location? [YES] Are the digital signa

[VOTE]: Release Apache Dubbo 2.6.7 [RC2]

2019-07-14 Thread Mercy Ma
Hi, All This is a call for a vote to release Apache Dubbo version 2.6.7. The release candidates (there will be only source release in this version): https://dist.apache.org/repos/dist/dev/dubbo/2.6.7/ < https://dist.apache.org/repos/dist/dev/dubbo/2.6.7/> Git tag for the release: https://github.

Re: [VOTE]: Release Apache Dubbo 2.6.7 [RC2]

2019-07-14 Thread Shunyu Lei
+1 Mercy Ma 于2019年7月15日周一 下午1:50写道: > Hi, All > > This is a call for a vote to release Apache Dubbo version 2.6.7. > > The release candidates (there will be only source release in this version): > https://dist.apache.org/repos/dist/dev/dubbo/2.6.7/ < > https://dist.apache.org/repos/dist/dev/dubb

Re: [VOTE]: Release Apache Dubbo 2.7.3 [RC3]

2019-07-14 Thread Shunyu Lei
+1 Huxing Zhang 于2019年7月15日周一 下午12:44写道: > Hi, > > On Sun, Jul 14, 2019 at 4:20 PM YunKun Huang wrote: > > > > +1 approve > > > > I have checked: > > * Can compile from source > > * Run with dubbo-sample, all checks pass > > > > There is one question for CHANGES file format. Usually changes > i

Re: [VOTE]: Release Apache Dubbo 2.7.3 [RC3]

2019-07-14 Thread Jun Liu
> There is one question for CHANGES file format. Usually changes information > are spilt into `New Features`, `Enhancement`, `Bugfixes`, should we keep to > use this format? Agree. I thought there were not enough changes that need to be clarified, I will follow the format in the Release Notes aft

Re: [VOTE]: Release Apache Dubbo 2.7.3 [RC3]

2019-07-14 Thread Jun Liu
> Minor issue: binary distribution is not release this time, as the > license file has not been updated yet. Whether or not to do binary > distribution remains a question to be discussed. I noticed the license problem so I tend to not include the binary release until we fixed it. Jun > On Jul