Forwarding this here ... Von: Christofer Dutz <[email protected]> Datum: Dienstag, 27. Januar 2026 um 13:35 An: [email protected] <[email protected]> Betreff: AW: [VOTE] Release Apache BifroMQ 4.0.0-incubating RC3
+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] Compared the content of the src archive with the content of the git repo at the given git hash for the release. * Only minor GitHub related files missing and no changed files. [OK] Check the archives have „apache“ and „incubating“ in their names. - From the naming it is suggested that the linux binary distribution is the main artifact of the release. However Apache projects usually release sources and we consider binary distributions as convenience. So for me I was expecting apache-bifromq-4.0.0-incubating.tar.gz to be the source release, which I quickly noticed was not the case. [OK] Verify the existence of LICENSE, NOTICE, README, DISCLAIMER files in the extracted source bundle. [OK] Verify the content of LICENSE, NOTICE, README, DISCLAIMER files in the extracted source bundle. - Generally we would have the year of the release in the NOTICE file. So technically at the time we actually perform the release, it’s going to be 2026. Considering the RC was created on 30.12.2025, I won’t even give this a „MINOR“. Just wanted to point that out. [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. [OK] Build the project according to the information in the README.md file. Von: Visoar <[email protected]> Datum: Donnerstag, 1. Januar 2026 um 07:56 An: [email protected] <[email protected]> Betreff: Re: [VOTE] Release Apache BifroMQ 4.0.0-incubating RC3 Hi all. +1 (binding) [x] Download links are valid [x] Checksums and signatures [x] LICENSE and NOTICE files exist [x] No unexpected binary files [x] All source files have ASF headers [x] Can compile from source Visoar —————— Visoar gujiaweijoe <[email protected]>于2026年1月1日 周四10:37写道： > Hi all, > > +1 approve (binding) > > Verified the list and look fine to me. > > [x] Download links are valid > [x] Checksums and signatures > [x] LICENSE and NOTICE files exist > [x] No unexpected binary files > [x] All source files have ASF headers > [x] Can compile from source > > Best regards, > Gu Jiawei (gujiaweijoe) > > Original > From: Yonny Hao <[email protected]> > Date: 2025-12-30 14:18 > To: dev <[email protected]> > Subject: [VOTE] Release Apache BifroMQ 4.0.0-incubating RC3 > > 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 > > >
