This vote passes with the following +1 binding votes:

- Gary Gregory (ggregory)
- Henri Biestro (henrib)
- Rob Tompkins (chtompki)

Thank you,
Gary

On Wed, Nov 11, 2026 at 10:39 PM Rob Tompkins <[email protected]> wrote:
>
> +1, all good
>
> keep up the good work.
>
> Cheers,
> -Rob
>
> > On Nov 7, 2026, at 1:47 PM, Gary Gregory <[email protected]> wrote:
> >
> > We have fixed a few bugs, added one new feature, and made some minor
> > enhancements since the release of Apache Commons BCEL 6.13.0, so I
> > would like to release Apache Commons BCEL 6.14.0.
> >
> > Apache Commons BCEL 6.14.0 RC1 is available for review here:
> >    https://dist.apache.org/repos/dist/dev/commons/bcel/6.14.0-RC1
> > (svn revision 89128)
> >
> > The Git tag commons-bcel-6.14.0-RC1 commit for this RC is
> > bab20a1b002947ac0f2716cdb4860f60d47443a1, which you can browse here:
> >    
> > https://gitbox.apache.org/repos/asf?p=commons-bcel.git;a=commit;h=bab20a1b002947ac0f2716cdb4860f60d47443a1
> > You may checkout this tag using:
> >    git clone https://gitbox.apache.org/repos/asf/commons-bcel.git
> > --branch commons-bcel-6.14.0-RC1 commons-bcel-6.14.0-RC1
> >
> > Maven artifacts are here:
> >    
> > https://repository.apache.org/content/repositories/orgapachecommons-1972/org/apache/bcel/bcel/6.14.0/
> >
> > These are the artifacts and their hashes:
> >
> > #Release SHA-512s
> > #Sat Nov 07 18:33:34 UTC 2026
> > bcel-6.14.0-bin.tar.gz=c0c0d2d6688e8951c5a3c7279dbc06e4cc96dd7ac934c721f321fb9cad734f5122776086d03d8568d9216f46638d4c57bac5c78db8bab6b5ea5f50b353218e78
> > bcel-6.14.0-bin.zip=ca11175a6cc544dd2c228d709545d78d2a96ddb642cf79d40d471cb052a46079186ffab7b68d79a1522a0f9f656d46f72a99ab332fbd2f18d116eae1d73ad892
> > bcel-6.14.0-bom.json=7105e74ebbff4a777aa59a5da9f3f8cfc7df5bc067df93089a257102924471ab9ee30f6f8b7cfe4dce7d5d04f87c33e3bdb4f8ab8dabfa8c7767c0d8d63f9e91
> > bcel-6.14.0-bom.xml=7c252dd930d0fe74f405b0c4b0775944b751ae40fb66fffb9c332b996bfb260ad016a74051da2d3b3497cb414692149eb3de8ccfebbaded0dba9d72697e8b37a
> > bcel-6.14.0-javadoc.jar=580fb72657dddabdedd6c4a36bc62a927dcb32cbc948071d2311c56b09c92c106226278feb68329d15eb1a215b4ec3dae2c09b47396151e9e9d71f31105f6e15
> > bcel-6.14.0-sources.jar=080974bbf77f5d899edcf2535aa99aa79ec9441241c525bbf0b5beebe75faaa46e37eb881536f52f97e4d20dd52b6277680dcf44347a9f2c5766a92b5d4aa3d1
> > bcel-6.14.0-src.tar.gz=e889f95196339491798a82eb32949f3c0bfece3846e695f7b5157905ef3fade94a9621ca08661ec07f7b045575eec57c7a9bf7b457df2ea17d3604d6ab5c1e83
> > bcel-6.14.0-src.zip=1be9b532f6c66c6f075498af73f4b8669d8dc3401c6b79b2b47f0ba1014887bb87b0ff2676a80e93f69fc689a581f27373ff6c15da0303d7afa4cbf8e9f6db74
> > bcel-6.14.0-test-sources.jar=bf52a1c1f66e16a570671c7b635787c188347cfb64bb0a570d899524b86b11b844782f2eee72d9ba31ec0e5d29cef81f5a0d6e8c77274c3ad83fd0125c6ef530
> > bcel-6.14.0-tests.jar=bcf71947fd2ebaace38c90d408fb4769565e678eca13a3929e43c02b0a58bc7d40b519661562747fe766c326e803f36ea76804ebee621564f32a96338f583b60
> > org.apache.bcel_bcel-6.14.0.spdx.json=aa9381f9e7975f6795718f4c34f4397c6c6b54c95296681e8c32174c747d696bb230a4dd546b31034f1a6f5b796d1058801d956ed489eea07846fb8c9dc0d700
> >
> >
> > I have tested this with 'mvn' and 'mvn clean install site' using:
> >
> > openjdk version "27.0.1.0.3" 2026-10-24
> > OpenJDK Runtime Environment Homebrew (build 27.0.1.0.3)
> > OpenJDK 64-Bit Server VM Homebrew (build 27.0.1.0.3, mixed mode, sharing)
> >
> > Apache Maven 3.10.0 (c43a36b8d67be7e0805a411bc0898af1a51f5472)
> > Maven home: /opt/homebrew/Cellar/maven/3.10.0/libexec
> > Java version: 27.0.1.0.3, vendor: Homebrew, runtime:
> > /opt/homebrew/Cellar/openjdk/27.0.1.0.3/libexec/openjdk.jdk/Contents/Home
> > Default locale: en_US, platform encoding: UTF-8, time zone: UTC
> > OS name: "mac os x", version: "26.7.2", arch: "aarch64", family: "mac"
> >
> > Darwin ****.local 25.6.0 Darwin Kernel Version 25.6.0: Mon Oct 12
> > 00:39:48 PDT 2026; root:xnu-12377.161.15.701.48~2/RELEASE_ARM64_T6041
> > arm64
> >
> > Docker version 29.9.2, build a82e528
> >
> >
> > Details of changes since 6.13.0 are in the release notes:
> >    
> > https://dist.apache.org/repos/dist/dev/commons/bcel/6.14.0-RC1/RELEASE-NOTES.txt
> >    
> > https://dist.apache.org/repos/dist/dev/commons/bcel/6.14.0-RC1/site/changes.html
> >
> > Site:
> >    
> > https://dist.apache.org/repos/dist/dev/commons/bcel/6.14.0-RC1/site/index.html
> >    (Note some *relative* links are broken and the 6.14.0 directories
> > are not yet created - these will be OK once the site is deployed.)
> >
> > JApiCmp Report (compared to 6.13.0):
> >    
> > https://dist.apache.org/repos/dist/dev/commons/bcel/6.14.0-RC1/site/japicmp.html
> >
> > RAT Report:
> >    
> > https://dist.apache.org/repos/dist/dev/commons/bcel/6.14.0-RC1/site/rat-report.html
> >
> > KEYS:
> >  https://downloads.apache.org/commons/KEYS
> >
> > Please review the release candidate and vote.
> > This vote will close no sooner than 72 hours from now.
> >
> >  [ ] +1 Release these artifacts
> >  [ ] +0 OK, but...
> >  [ ] -0 OK, but really should fix...
> >  [ ] -1 I oppose this release because...
> >
> > Thank you,
> >
> > Gary Gregory,
> > Release Manager (using key 530AA5F25C25011F)
> >
> > The following is intended as a helper and refresher for reviewers.
> >
> > Validating a release candidate
> > ==============================
> >
> > These guidelines are NOT complete.
> >
> > Requirements: Git, Java, and Maven.
> >
> > You can validate a release from a release candidate (RC) tag as follows.
> >
> > 1a) Download and decompress the source archive from:
> >
> > https://dist.apache.org/repos/dist/dev/commons/bcel/6.14.0-RC1/source
> >
> > 1b) Check out the RC tag from git (optional)
> >
> > This is optional,  as a reviewer must at least check source distributions.
> >
> > git clone https://gitbox.apache.org/repos/asf/commons-bcel.git
> > --branch commons-bcel-6.14.0-RC1 commons-bcel-6.14.0-RC1
> > cd commons-bcel-6.14.0-RC1
> >
> > 2) Checking the build
> >
> > All components should include a default Maven goal, such that you can
> > run 'mvn' from the command line by itself.
> >
> > 2) Check Apache licenses
> >
> > This step is not required if the site includes a RAT report page,
> > which you then must check.
> > This check should be included in the default Maven build, but you can
> > check it with:
> >
> > mvn apache-rat:check
> >
> > 3) Check binary compatibility
> >
> > This step is not required if the site includes a JApiCmp report page,
> > which you then must check.
> > This check should be included in the default Maven build, but you can
> > check it with:
> >
> > mvn verify -DskipTests -P japicmp japicmp:cmp
> >
> > 4) Build the package
> >
> > This check should be included in the default Maven build, but you can
> > check it with:
> >
> > mvn -V clean package
> >
> > You can record the Maven and Java version produced by -V in your VOTE reply.
> > To gather OS information from a command line:
> > Windows: ver
> > Linux: uname -a
> >
> > 4b) Check reproducibility
> >
> > To check that a build is reproducible, run:
> >
> > mvn clean verify artifact:compare -DskipTests
> > -Dreference.repo=https://repository.apache.org/content/repositories/staging/
> > '-Dbuildinfo.ignore=*/*.spdx.json'
> >
> > Note that this excludes SPDX files from the check.
> >
> > 5) Build the site for a single module project
> >
> > Note: Some plugins require the components to be installed instead of 
> > packaged.
> >
> > mvn site
> > Check the site reports in:
> > - Windows: target\site\index.html
> > - Linux: target/site/index.html
> >
> > -the end-
> >
> > ---------------------------------------------------------------------
> > 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]

Reply via email to