The KEYS file needs to be moved too. It should be in https://dist.apache.org/repos/dist/release/incubator/geaflow/ not https://dist.apache.org/repos/dist/dev/incubator/geaflow/
https://dist.apache.org/repos/dist/release/incubator/geaflow/ will be automatically synched with https://downloads.apache.org/incubator/geaflow/ Then votes should use the https://downloads.apache.org/incubator/geaflow/KEYS link. On Thu, 30 Oct 2025 at 12:15, Qiang Zhou <[email protected]> wrote: > > Hi Ed Espino, > > Thank you very much for the thorough review and valuable feedback on Apache > GeaFlow 0.7.0-incubating RC1! > > We have carefully addressed all the issues raised and completed the > necessary fixes as follows: > > > 1. Added required files > > - Added a compliant NOTICE file as required by Apache policy > > - Added the incubator-mandated DISCLAIMER file > > > 2. Corrected naming conventions > > - Source archive has been renamed to: > apache-geaflow-0.7.0-incubating-src.tar.gz > > - The extracted directory name is now: apache-geaflow-0.7.0-incubating-src/ > > - All built JAR artifacts now include the -incubating qualifier (e.g., > geaflow-assembly-0.7.0-incubating.jar) to ensure consistent naming > > > 3. Fixed license header compliance > > - Reviewed the full Apache RAT report (originally flagged 194 files) > > - For files that cannot legally or practically carry a license header, > appropriate <excludes> have been added in pom.xml > > - Verified clean pass with mvn apache-rat:check > > > All fixes have been merged into the release branch, and the artifacts have > passed full build validation and functional testing. > > > We plan to formally propose RC2 for voting shortly. > > > Once again, thank you for your rigorous review and constructive > guidance—this is invaluable in helping us adhere to Apache release > standards and improve our release process. > > > Kind regards, > loogn > > Ed Espino <[email protected]> 于2025年10月28日周二 18:26写道： > > > Apache GeaFlow 0.7.0-incubating RC1 - Vote Report > > ================================================== > > > > Vote: -1 (binding) > > > > > > CRITICAL ISSUES > > =============== > > > > 1. Missing Required Files > > -------------------------- > > - NOTICE file: MISSING (required per Apache policy) > > - DISCLAIMER file: MISSING (required for incubator releases) > > > > Reference: https://incubator.apache.org/policy/incubation.html > > > > > > 2. Incubator Naming Violations > > ------------------------------- > > Per the Incubator Release Checklist: > > > > https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist > > > > - Artifact naming: apache-geaflow-0.7.0-src.tar.gz > > MUST be: apache-geaflow-0.7.0-incubating-src.tar.gz > > > > - Directory naming: apache-geaflow-0.7.0-src/ > > MUST be: apache-geaflow-0.7.0-incubating-src/ > > > > - Built artifacts: All JARs lack "incubating" in filenames > > Example: geaflow-assembly-0.7.0.jar > > Note: JAR naming is "suggested but optional" per policy, but recommended > > for consistency > > > > > > 3. License Header Compliance > > ----------------------------- > > Apache RAT identified 194 files without Apache license headers, including: > > - Documentation files (.md, .rst) > > - Frontend assets (JavaScript, CSS) > > - Configuration files (.yaml, .proto) > > > > RAT report can be reproduced with: mvn apache-rat:check > > > > > > VERIFIED SUCCESSFULLY > > ===================== > > > > [X] GPG signatures valid (all 2 artifacts) > > [X] SHA512 checksums valid (all 2 artifacts) > > [X] LICENSE file present (Apache License 2.0) > > [X] Source builds successfully (10-20 min build time) > > [X] Functional testing passed (GQL loop detection demo) > > > > > > RECOMMENDATION > > ============== > > > > The release must be rejected due to 4 critical Apache Incubator policy > > violations. While the source code quality is verified (builds and runs > > correctly), the release artifacts do not meet incubator requirements. > > > > The Release Manager should: > > 1. Add NOTICE and DISCLAIMER files > > 2. Re-cut artifacts with "incubating" in names > > 3. Review RAT findings and add license headers or exclusions where > > appropriate > > 4. Submit RC2 for vote > > > > -- > > Ed Espino > > Apache Cloudberry (Incubating) & MADlib > > > > > > On Mon, Oct 27, 2025 at 11:44 PM Qiang Zhou <[email protected]> wrote: > > > > > * We apologize for resending this message due to the format issues. The > > > last email sent is invalid. * > > > > > > Hi everyone, > > > > > > The Apache GeaFlow community has voted and approved the release of Apache > > > GeaFlow v0.7.0-rc1 (Incubating). We are now kindly requesting the IPMC > > > members to review and vote for this release. > > > > > > Apache GeaFlow community vote thread: > > > > > > - https://lists.apache.org/thread/ryw8xwlgtc920xrk9y90gmffwmrrsq06 > > > > > > Vote result thread: > > > > > > - https://lists.apache.org/thread/b3rz8hmhtqdncjhs5m3qylg1ypmkpxr8 > > > > > > This corresponds to the tag: v0.7.0-rc1. > > > > > > - https://github.com/apache/geaflow/commits/v0.7.0-rc1 > > > - > > > > > > > > https://github.com/apache/geaflow/tree/8c1c52b307dec5d3f82481e3000c72e698b97fc7 > > > > > > The release zip package, signature, and checksum are here: > > > > > > - https://dist.apache.org/repos/dist/dev/incubator/geaflow/v0.7.0-rc1/ > > > <https://dist.apache.org/repos/dist/dev/incubator/geaflow/v0.7.0-rc1/> > > > > > > You can find the KEYS file here: > > > > > > - https://dist.apache.org/repos/dist/dev/incubator/geaflow/KEYS > > > <https://dist.apache.org/repos/dist/dev/incubator/geaflow/KEYS> > > > > > > The Maven staging repository: > > > > > > - > > > https://repository.apache.org/content/repositories/orgapachegeaflow-1007 > > > > > > Please download, verify and test. > > > > > > The vote is open for at least 72 hours. > > > > > > [ ] +1 approve > > > [ ] +0 no opinion > > > [ ] -1 disapprove with the reason > > > > > > To learn more about Apache GeaFlow, please see > > https://geaflow.apache.org/ > > > . > > > > > > Kind Regards, > > > loogn > > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
