+1 I have checked:
+ LICENSE, DISCLAIMER, NOTICE are included in release files + All binary files related to dubbo is included in release files + I can build binary from source files On 2019/03/19 05:41:28, Minxuan Zhuang <[email protected]> wrote: > +1 > I have checked the following list: > > 1. Are release files in correct location? Yes > 2. Do release files have the word incubating in their name? Yes > 3. Are the digital signature and hashes correct? Yes > 4. Does DISCLAIMER file exist? Yes > 5. Do LICENSE and NOTICE files exists? Yes > 6. Is the LICENSE and NOTICE text correct? Yes > 7. Is the NOTICE year correct? Yes > 8. Un-included software dependencies are not mentioned in LICENSE or > NOTICE? Yes > 9. License information is not mentioned in NOTICE? Yes > 10. Is there any 3rd party code contained inside the release? If so: Yes > 11. Does the software have a compatible license? Yes > 12. Are all software licenses mentioned in LICENSE? Yes > 13. Is the full text of the licenses (or pointers to it) in LICENSE? Yes > 14. Is any of this code Apache licensed? Do they have NOTICE files? If > so: Yes > 15. Have relevant parts of those NOTICE files been added to this NOTICE > file? Yes > 16. Do all source files have ASF headers? Yes > 17. Do the contents of the release match with what's tagged in version > control? Yes > 18. Are there any unexpected binary files in the release? Yes > 19. Can you compile from source? Are the instruction clear? Yes > > > On Tue, Mar 19, 2019 at 1:29 PM Zonghai Shang <[email protected]> wrote: > > > I vote with: +1 release the software > > > > I have checked the following list: > > > > 1. Are release files in correct location? > > > > * OK* > > 2. Do release files have the word incubating in their name? > > > > * OK* > > 3. Are the digital signature and hashes correct? > > > > * OK* > > 4. Does DISCLAIMER file exist? > > > > * OK* > > 5. Do LICENSE and NOTICE files exists? > > > > * OK* > > 6. Is the LICENSE and NOTICE text correct? > > > > * OK* > > 7. Is the NOTICE year correct? > > > > * OK* > > 8. Un-included software dependencies are not mentioned in LICENSE or > > NOTICE? > > > > * OK* > > 9. License information is not mentioned in NOTICE? > > > > * OK* > > 10. Is there any 3rd party code contained inside the release? If so: > > > > * OK* > > 11. Does the software have a compatible license? > > > > * OK* > > 12. Are all software licenses mentioned in LICENSE? > > > > * OK* > > 13. Is the full text of the licenses (or pointers to it) in LICENSE? > > > > * OK* > > 14. Is any of this code Apache licensed? Do they have NOTICE files? If > > so: > > > > * OK* > > 15. Have relevant parts of those NOTICE files been added to this NOTICE > > file? > > > > * OK* > > 16. Do all source files have ASF headers? > > > > * OK* > > 17. Do the contents of the release match with what's tagged in version > > control? > > > > * OK* > > 18. Are there any unexpected binary files in the release? > > > > * OK* > > 19. Can you compile from source? Are the instruction clear? > > > > * OK* > > > > Kind regards, > > -yiji > > > > Mercy <[email protected]> 于2019年3月19日周二 下午12:38写道： > > > > > +1 > > > > > > I have checked the following list: > > > > > > 1. Are release files in correct location? *PASS* > > > 2. Do release files have the word incubating in their name? *PASS* > > > 3. Are the digital signature and hashes correct? *PASS* > > > 4. Does DISCLAIMER file exist? *PASS* > > > 5. Do LICENSE and NOTICE files exists? *PASS* > > > 6. Is the LICENSE and NOTICE text correct? *PASS* > > > 7. Is the NOTICE year correct? *PASS* > > > 8. Un-included software dependencies are not mentioned in LICENSE or > > > NOTICE? *PASS* > > > 9. License information is not mentioned in NOTICE? *PASS* > > > 10. Is there any 3rd party code contained inside the release? If so: > > > *PASS* > > > 11. Does the software have a compatible license? *PASS* > > > 12. Are all software licenses mentioned in LICENSE? *PASS* > > > 13. Is the full text of the licenses (or pointers to it) in LICENSE? > > > *PASS* > > > 14. Is any of this code Apache licensed? Do they have NOTICE files? If > > > so: *PASS* > > > 15. Have relevant parts of those NOTICE files been added to this > > NOTICE > > > file? *PASS* > > > 16. Do all source files have ASF headers? *PASS* > > > 17. Do the contents of the release match with what's tagged in version > > > control? *PASS* > > > 18. Are there any unexpected binary files in the release? *PASS* > > > 19. Can you compile from source? Are the instruction clear? *PASS* > > > > > > Kind regards, > > > Mercy Ma > > > > > > > > > 在 2019/3/19 上午11:18, Ian Luo 写道: > > > > > > Hello Dubbo Community, > > > > > > This is a call for vote to release Apache Dubbo (Incubating) version > > 2.7.1. > > > > > > The release candidates (RC1): > > https://dist.apache.org/repos/dist/dev/incubator/dubbo/2.7.1 > > > > > > Git tag for the release (RC1): > > https://github.com/apache/incubator-dubbo/tree/dubbo-2.7.1 > > > > > > Hash for the release tag: > > > a36cc7520e0150d07d30e8baa0c61d5f9f11e6ed > > > > > > Release Notes: > > https://github.com/apache/incubator-dubbo/blob/dubbo-2.7.1/CHANGES.md > > > > > > The artifacts have been signed with Key: 9C44B5A6884984DB, 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 > > > > > > > > > > > >
