+1 I checked:
*- Download links are valid.- Checksums and signatures.- LICENSE/NOTICE files exist- No unexpected binary files- All source files have ASF headers* Zirui Sting <[email protected]> 于2022年9月5日周一 10:42写道： > Hello Apache InLong PMC and Community, > > This is a call for a vote to release Apache InLong version 1.3.0 RC1. > > The tag to be voted on is 1.3.0 RC1: > > https://github.com/apache/inlong/tree/1.3.0-RC1 > > The release tarball, signature, and checksums can be found at: > > https://dist.apache.org/repos/dist/dev/inlong/1.3.0-RC1/ > > Maven artifacts are available in a staging repository at: > > > https://repository.apache.org/content/repositories/orgapacheinlong-1096 > > Artifacts were signed with the 278B22C6496D04D4257807D6B3A12A68F1CFE8B4 > key which can be found in: > > https://downloads.apache.org/inlong/KEYS > > 1.3.0 includes 411 bug fixes and improvements done since last versions > which can be found at: > > https://github.com/apache/inlong/blob/1.3.0-RC1/CHANGES.md > > Please download, verify, and test. > > The VOTE will remain open for at least 72 hours. > > [ ] +1 Release this package as Apache InLong 1.3.0 > [ ] +0 > [ ] -1 Do not release this package because... > > To learn more about apache InLong, please see > http://inlong.apache.org/ > > Checklist for reference: > > [ ] Download links are valid. > [ ] Checksums and signatures. > [ ] LICENSE/NOTICE files exist > [ ] No unexpected binary files > [ ] All source files have ASF headers > [ ] Can compile from source > [ ] All Tests Passed > > More detailed checklist please refer to: > https://inlong.apache.org/community/how-to-verify > > Thanks, > Your InLong Release Manager >
