My +1 Gary
On Sun, Sep 6, 2026 at 2:49 PM Gary Gregory <[email protected]> wrote: > > [This release is b y request from SpotBugs] > > We have fixed a few bugs and added enhancements since the release of > Apache Commons BCEL 6.12.0, so I would like to release Apache Commons > BCEL 6.13.0. > > Apache Commons BCEL 6.13.0 RC1 is available for review here: > https://dist.apache.org/repos/dist/dev/commons/bcel/6.13.0-RC1 > (svn revision 87299) > > The Git tag commons-bcel-6.13.0-RC1 commit for this RC is > be4bc45e5ee623b4d074a0b0888da828822dd9b3, which you can browse here: > > https://gitbox.apache.org/repos/asf?p=commons-bcel.git;a=commit;h=be4bc45e5ee623b4d074a0b0888da828822dd9b3 > You may checkout this tag using: > git clone https://gitbox.apache.org/repos/asf/commons-bcel.git > --branch commons-bcel-6.13.0-RC1 commons-bcel-6.13.0-RC1 > > Maven artifacts are here: > > https://repository.apache.org/content/repositories/orgapachecommons-1964/org/apache/bcel/bcel/6.13.0/ > > These are the artifacts and their hashes: > > #Release SHA-512s > #Sun Sep 06 18:31:27 UTC 2026 > bcel-6.13.0-bin.tar.gz=6ac6ac7ef5a8d463fa85c7f76560dba520ca94f50545b39dbea3bae6f8c4de60f4c7d147af79bc86b2082156fb0059cae4e4783f191658ca967f9283dff56ee3 > bcel-6.13.0-bin.zip=b2faa1e7b48cf44534088c564119f0d5e14db04697a8b2a0604361af75770261b050292e23a2111c493138b8197a24e9e62879983d344ee17f0c53e1d070eed5 > bcel-6.13.0-bom.json=03360318d16487fe4c05d830db5491f65a3a750e3336cab8683992d49a56f8bf1e2eb188fc49b6c1f760627131fe6c667d838988b9fe4ef3165d6bc1799abec3 > bcel-6.13.0-bom.xml=a0ae7c8a5e9c76c25d2c1f410c8b0d0f2fc30f93d1c9c21caa1dc2addb358b788fce301b85eb5a3de07fbc93b507476f96f98967c8d22068e1b34c8459c21a78 > bcel-6.13.0-javadoc.jar=3fdeb13f02fa180f213e53e1e39735cb71a6099dd6243ba6a4cd2c253c4aa3c2d281705360b292020058ffcd3b85c789561860ea42385defb5bee8aaee3a4261 > bcel-6.13.0-sources.jar=fa82325c71ab3116017b7d3c1bd3ea7b2b445c602f5a125b4754dd0d2ce55ba912c2482bfe9adce4435801159272d3f89e4d89f349c831392a123ddced3c2ddc > bcel-6.13.0-src.tar.gz=b35b931af9b46f5c7fb467d8ff734419c139686283c8b072533af8322ef2514dfe866c145823ade3e24deb2beb1ed4ed3d30ee2390788c74ccb64b20574d88c4 > bcel-6.13.0-src.zip=9130263571c3d23b6cf2580e7c0f4b05af96e390e208c6aa4a90885ff0e9752260bf9184c8cdb434fc578bdc0a210b63cb2c459e5f21e842d257f8dfefc40e1d > bcel-6.13.0-test-sources.jar=7dbbc1c5c378368c1a6a36ccc4309876465d431f7d34663b6df585914c587fdb3c89177004cd2aec8b60a582644a5e8db885e493a1676b9509fc855fb5dcc6bf > bcel-6.13.0-tests.jar=f0eda935a59c14fbff4f182af1b776be84a656b38ec6faea944ae9cf787b7a20694cb056589e244e78f9e56d6872eef8c25709fb0e9492debb43c4e3f15afeb1 > org.apache.bcel_bcel-6.13.0.spdx.json=062f97ea906a6433ebc38be3957b3089ef81035f2ea1181ad843c96cb952e6615ea21c43b79151d71b4d588036b9c3dd6b0f5a66fc2035e661a00134fa0729fd > > > I have tested this with 'mvn' and 'mvn clean install site' using: > > openjdk version "25.0.4.1" 2026-08-18 > OpenJDK Runtime Environment Homebrew (build 25.0.4.1) > OpenJDK 64-Bit Server VM Homebrew (build 25.0.4.1, mixed mode, sharing) > > Apache Maven 3.9.16 (2bdd9fddda4b155ebf8000e807eb73fd829a51d5) > Maven home: /opt/homebrew/Cellar/maven/3.9.16/libexec > Java version: 25.0.4.1, vendor: Homebrew, runtime: > /opt/homebrew/Cellar/openjdk@25/25.0.4.1/libexec/openjdk.jdk/Contents/Home > Default locale: en_US, platform encoding: UTF-8 > OS name: "mac os x", version: "26.6.2", arch: "aarch64", family: "mac" > > Darwin ****.local 25.6.0 Darwin Kernel Version 25.6.0: Fri Jul 31 > 19:17:26 PDT 2026; root:xnu-12377.161.14~5/RELEASE_ARM64_T6041 arm64 > > Docker version 29.7.2, build a7dcaa6 > > > Details of changes since 6.12.0 are in the release notes: > > https://dist.apache.org/repos/dist/dev/commons/bcel/6.13.0-RC1/RELEASE-NOTES.txt > > https://dist.apache.org/repos/dist/dev/commons/bcel/6.13.0-RC1/site/changes.html > > Site: > > https://dist.apache.org/repos/dist/dev/commons/bcel/6.13.0-RC1/site/index.html > (Note some *relative* links are broken and the 6.13.0 directories > are not yet created - these will be OK once the site is deployed.) > > *** JApiCmp Report (compared to 6.12.0): > > https://dist.apache.org/repos/dist/dev/commons/bcel/6.13.0-RC1/site/japicmp.html > > *** > Note that the above report notes several errors. > These are considered OK for the reasons stated below. > These exceptions are also noted in the Changes and Release Notes. > > Errors reported: > - methods added to interface: OK because that does not affect > binary compatibility. > - etc. > *** > > RAT Report: > > https://dist.apache.org/repos/dist/dev/commons/bcel/6.13.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.13.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.13.0-RC1 commons-bcel-6.13.0-RC1 > cd commons-bcel-6.13.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]
