Looking at apache-bifromq-4.0.0-incubating-windows.zip,
it seems the changes are limited to the bin files, and since there’s no JNI
or native code involved,
I’m not sure a separate Windows binary package is necessary.

On Tue, Dec 30, 2025 at 5:24 PM Calvin Kirs <[email protected]> wrote:

>
> Thanks, Yonny.
>
> +1 (binding)
> I checked:
>  - incubating in name
>  - signatures and hashes are fine
>  - disclaimer exists
>  - file has correct ASF headers if necessary
> Just a quick note: KEYS should be linked from
> https://downloads.apache.org/.
>
> Happy New Year to everyone!
>
>
> On Tue, Dec 30, 2025 at 2:18 PM Yonny Hao <[email protected]> wrote:
>
>> Hi everyone,
>> This is a call for a vote on releasing Apache BifroMQ 4.0.0-incubating
>> RC3.
>> This RC includes fixes and improvements
>> <https://github.com/apache/bifromq/pull/215> addressing the feedback
>> raised
>> during the RC2 vote
>> <https://lists.apache.org/thread/7mf07tqgjqg4nr7syxtj76v9yvbhm5tm> on the
>> general@ list, specifically:
>>
>>    - Separated LICENSE files for bundled binary dependencies
>>    - Updated NOTICE files for binary distributions with the required
>>    contents
>>
>> Release Candidates
>>
>> https://dist.apache.org/repos/dist/dev/incubator/bifromq/4.0.0-incubating-RC3/
>>
>> Git tag & commit
>> Tag: v4.0.0-incubating-RC3
>> Commit:
>>
>> https://github.com/apache/bifromq/commit/6cb2465b6eee5f041b0214ef923a398a160f9918
>>
>> Release notes
>> https://github.com/apache/bifromq/releases/tag/v4.0.0-incubating-RC3
>>
>> PGP KEYS(Signer: popduke)
>> https://dist.apache.org/repos/dist/release/incubator/bifromq/KEYS
>>
>> Maven staging repository (plugin-development related artifacts only)
>> https://repository.apache.org/content/repositories/orgapachebifromq-1006/
>>
>> Docker
>> Docker image will be built and published via GitHub Actions
>> <
>> https://github.com/apache/bifromq/blob/main/.github/workflows/docker-publish.yml
>> >
>> under
>> the Apache organization *after the source release is approved*.
>>
>> *Build & Verification Guide*
>> 1. Download the source archive from the "dist/dev" location.
>> 2. Build and verify using Maven:
>>
>> >    ./mvnw -v
>> >    ./mvnw -U clean verify -DskipTests -Pbuild-release
>>
>>    This command performs the full release verification, including license
>> checks, compilation, and packaging.
>> 3. Optionally, the license check can be run independently:
>>
>> >    ./mvnw apache-rat:check
>>
>> 4. Check that the build completes successfully and that the expected
>> artifacts are produced.
>>
>> *Test Guide*
>> 1. Prepare test environment
>>
>> > ./mvnw clean install -DskipTests
>>
>> 2. Execute
>>
>> > ./mvnw test (Includes unit tests only)
>> > ./mvnw test -Pbuild-coverage (Includes unit and integration tests, takes
>> > much longer)
>>
>>
>> *Vote*
>> The vote will remain open for 72 hours and until three binding +1 votes
>> are
>> received.
>> [ ] +1 approve
>> [ ] +0 no opinion
>> [ ] -1 do not approve (please provide the reason)
>>
>> *Quick Reference Checklist*
>> [ ] Download links are valid
>> [ ] Checksums and signatures
>> [ ] LICENSE and NOTICE files exist
>> [ ] No unexpected binary files
>> [ ] All source files have ASF headers
>> [ ] Can compile from source
>>
>> *Reference*
>>
>> https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist
>> Additional information about Apache BifroMQ is available at:
>> https://bifromq.apache.org/
>>
>> Thanks
>> --
>> Yonny(Yu) Hao
>>
>
>
> --
> Best wishes!
> CalvinKirs
>


-- 
Best wishes!
CalvinKirs

Reply via email to