+1 (binding) cdutz
[OK] Download all staged artifacts under the url specified in the release vote email. [OK] Verify the signature is correct. [OK] Check if the signature references an Apache email address. [OK] Verify the SHA512 hashes. [OK] Unzip the archive. [OK] Verify the existence of LICENSE, NOTICE, README files in the extracted source bundle. [OK] Verify the content of LICENSE, NOTICE, README files in the extracted source bundle. [OK] Run RAT externally to ensure there are no surprises. [OK] Search for SNAPSHOT references [OK] Search for Copyright references, and if they are in headers, make sure these files containing them are mentioned in the LICENSE file. [SKIPPED] Build the project according to the information in the README.md file. I did notice in apache-answer-1.7.1-src/docs/release/licenses there is a huge list of License files. What is this for? Usually we list the licenses of things included in our software. As the central LICENSE file doesn’t contain us embedding any outside components in our source repo, we should not require any. Is this for the binary releases? Von: mingcheng <[email protected]> Datum: Freitag, 19. Dezember 2025 um 09:00 An: [email protected] <[email protected]> Betreff: Re: [VOTE] Release Apache Answer v1.7.1-RC2 +1 APPROVE Binding On Fri, Dec 19, 2025 at 3:00 PM Kumfo Yang <[email protected]> wrote: > > +1 approve > > Checkd: > > [x] Download links are valid. > [x] Checksums and PGP signatures are valid. > [x] Source code distributions have correct names matching the current > release. > [x] LICENSE and NOTICE files are correct for each Answer repo. > [x] All files have license headers if necessary. > [x] No unlicensed compiled archives are bundled in the source archive. > > > Best Regards, > Kumfo > > Yubin Ren <[email protected]> 于2025年12月17日周三 15:00写道： > > > > +1 approve > > > > Check below: > > > > [x] Download links are valid. > > [x] Checksums and PGP signatures are valid. > > [x] Source code distributions have correct names matching the current > > release. > > [x] LICENSE and NOTICE files are correct for each Answer repo. > > [x] All files have license headers if necessary. > > [x] No unlicensed compiled archives are bundled in the source archive. > > > > > > Best Regards, > > Robin > > > > On 2025/12/16 03:05:56 LinkinStar wrote: > > > Hello Apache Answer Community, > > > > > > This is a call for vote to release Apache Answer version v1.7.1-RC2. > > > > > > The release candidates: > > > https://dist.apache.org/repos/dist/dev/answer/1.7.1-RC2 > > > > > > Release notes: > > > https://github.com/apache/answer/releases/tag/v1.7.1-RC2 > > > > > > Git tag for the release: > > > https://github.com/apache/answer/releases/tag/v1.7.1-RC2 > > > > > > Git commit id for the release: > > > https://github.com/apache/answer/commit/3000e3aec0814b710d90bc853115ac36078cfe23 > > > > > > Keys to verify the Release Candidate: > > > https://downloads.apache.org/answer/KEYS > > > > > > Keys to verify the Release Candidate: > > > The artifacts signed with PGP key [380DCBD5C34934CC], corresponding to [ > > > [email protected]], that can be found in keys file: > > > https://dist.apache.org/repos/dist/release/answer/KEYS > > > > > > The vote will be open for at least 72 hours or until the necessary number > > > of votes are reached. > > > > > > Please vote accordingly: > > > > > > [ ] +1 approve > > > [ ] +0 no opinion > > > [ ] -1 disapprove with the reason > > > > > > Checklist for reference: > > > > > > [ ] Download links are valid. > > > [ ] Checksums and PGP signatures are valid. > > > [ ] Source code distributions have correct names matching the current > > > release. > > > [ ] LICENSE and NOTICE files are correct for each Answer repo. > > > [ ] All files have license headers if necessary. > > > [ ] No unlicensed compiled archives bundled in source archive. > > > > > > To compile from the source, please refer to: > > > > > > https://github.com/apache/answer#building-from-source > > > > > > Best regards, > > > LinkinStar > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
