+1 (non-binding) for Apache Wayang (incubating) 1.1.0 RC2

I have performed a review of the Apache Wayang (incubating) 1.1.0 RC2
release candidate and found it to be compliant with Apache Incubator
release requirements.

Release Review Actions Performed:

Release Artifact Validation
- Verified download links are valid and accessible
- Confirmed PGP signature is valid for the release artifact using the KEYS
file
- Verified SHA512 checksums are correct and match provided hashes
- Confirmed source release artifact filename includes "incubating"

Apache Incubator Legal Requirements
- Verified LICENSE file contains proper Apache License 2.0
- Confirmed NOTICE file includes copyright and attributions
- Confirmed DISCLAIMER file present with proper incubating language
- Executed Apache RAT 0.13 check - PASSED with 16 approved licenses, 0
violations
- Verified README contains Apache Incubator project information

Incubating Project Compliance
- Project name consistently includes "(incubating)" designation in
documentation
- All binary files properly named with incubating version scheme (examples):
  * apache-wayang-core-1.1.0-incubating.jar
  * apache-wayang-spark-1.1.0-incubating.jar
  * apache-wayang-flink-1.1.0-incubating.jar
  * apache-wayang-tensorflow-1.1.0-incubating.jar
- Build system applies incubating branding to all generated JARs, sources,
  and javadoc packages across all modules
- Maven configuration includes proper "incubating" suffix in artifact names

Build and Test Validation
- Successfully built project with ./mvnw clean install -DskipTests using
Java 17
- Executed complete test suite with ./mvnw test - 420 tests passed, 0
failures, 0 errors
- All 30 modules compiled successfully without errors
- Maven build completed with exit code 0
- No compilation or dependency resolution issues observed

Build System Configuration
- Maven build system functions correctly with Java 17
- All dependencies resolved successfully during build process
- Apache RAT plugin configured and executed successfully
- Build generates main, sources, and javadoc JARs for each module

Summary
The release demonstrates compliance with Apache Incubator standards.
Legal requirements are satisfied, the project uses proper incubating
branding throughout generated artifacts, and the build system functions
correctly with comprehensive test coverage.

+1 (non-binding)

Review performed using Apache RAT 0.13, Maven wrapper, Java 17, and
analysis of the apache-wayang-incubating-1.1.0 source distribution.

-- 
Ed Espino
Apache Cloudberry (Incubating) & MADlib


On Wed, Aug 13, 2025 at 1:23 AM Mads Sejer Pedersen <s...@itu.dk.invalid>
wrote:

> Dear all,
>
> Apache Wayang (Incubating) 1.1.0 has been staged under [2] and it’s time
> to vote
> on accepting it for release. All Maven artifacts are available under [1].
> Voting will be open for at least 72hr.
>
> A minimum of 3 binding +1 votes and more binding +1 than binding -1 are
> required to pass.
>
> Release tag: v1.1.0-rc2
> Hash for the release tag (commit 9e35c45):
> https://github.com/apache/incubator-wayang/releases/tag/v1.1.0-rc2
>
> Per [3] "Before voting +1 PMC members are required to download
> the signed source code package, compile it as provided, and test
> the resulting executable on their own platform, along with also
> verifying that the package meets the requirements of the ASF policy
> on releases."
>
> You can achieve the above by following [4].
>
> [ ] +1 accept (indicate what you validated - e.g. performed the non-RM
> items in [4])
> [ ] -1 reject (explanation required)
>
> [1]
> https://repository.apache.org/content/repositories/orgapachewayang-1027
> [2] https://dist.apache.org/repos/dist/dev/incubator/wayang/1.1.0/rc2/
> [3] https://www.apache.org/dev/release.html#approving-a-release
> [4]
> https://cwiki.apache.org/confluence/display/PLC4X/Validating+a+staged+Release
>
> The vote results can be viewed here:
> https://lists.apache.org/thread/1yzts9hqc8nw6t8jxgqlmbo8pnmptdl4
>
> Keys can be viewed here:
> https://dist.apache.org/repos/dist/release/incubator/wayang/KEYS
>

Reply via email to