+1 from me. I checked the following items: - [√] Download links are valid.
- [√] Checksums and PGP signatures are valid. - [√] Source code artifacts have correct names matching the current release. - [√] LICENSE and NOTICE files are correct *for* the repository. - [√] All files have license headers *if* necessary. - [√] Building is OK. Verne Deng <verned...@apache.org> 于2023年12月14日周四 21:37写道： > Hello Apache InLong PMC and Community, > > This is a call for a vote to release Apache InLong version 1.10.0-RC0. > > The tag to be voted on is 1.10.0-RC0: > > https://github.com/apache/inlong/tree/1.10.0-RC0 > > The release tarball, signature, and checksums can be found at: > > https://dist.apache.org/repos/dist/dev/inlong/1.10.0-RC0/ > > Maven artifacts are available in a staging repository at: > > > https://repository.apache.org/content/repositories/orgapacheinlong-1157 > > Artifacts were signed with the > C2C89B478C5EA464467973B712A0B5FB1B815A2A key, which can be found in: > > https://downloads.apache.org/inlong/KEYS > > 1.10.0 includes ~ 207 bug fixes and improvements done since the > last versions, which can be found at: > > https://github.com/apache/inlong/blob/1.10.0-RC0/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.10.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 the following: > https://inlong.apache.org/community/how-to-verify > > Thanks, > Your InLong Release Manager >
