My +1 Gary
On Fri, Oct 10, 2025 at 11:52 PM Rob Tompkins <[email protected]> wrote: > > +1 all good. Thank you Gary!!!! Keep up the good work! > > > On Oct 9, 2025, at 7:55 PM, Gary Gregory <[email protected]> wrote: > > > > We have fixed a few bugs and added enhancements since Apache Commons > > BCEL 6.10.0 was released, so I would like to release Apache Commons > > BCEL 6.11.0. > > > > Apache Commons BCEL 6.11.0 RC1 is available for review here: > > https://dist.apache.org/repos/dist/dev/commons/bcel/6.11.0-RC1 > > (svn revision 79892) > > > > The Git tag commons-bcel-6.11.0-RC1 commit for this RC is > > dc0feabe0ba6c98f6d705114edde2a949eaf1212 which you can browse here: > > > > https://gitbox.apache.org/repos/asf?p=commons-bcel.git;a=commit;h=dc0feabe0ba6c98f6d705114edde2a949eaf1212 > > You may checkout this tag using: > > git clone https://gitbox.apache.org/repos/asf/commons-bcel.git > > --branch commons-bcel-6.11.0-RC1 commons-bcel-6.11.0-RC1 > > > > Maven artifacts are here: > > > > https://repository.apache.org/content/repositories/orgapachecommons-1864/org/apache/bcel/bcel/6.11.0/ > > > > These are the artifacts and their hashes: > > > > #Release SHA-512s > > #Thu Oct 09 23:25:03 UTC 2025 > > bcel-6.11.0-bin.tar.gz=b5bc569cd79980878d20b5053946970b5bbb8b8cb9dca809cc8c8eed2df88494428c412e286dc094d5c0aa0d1858634c58606fb34c41bdf87110a7e468469e0c > > bcel-6.11.0-bin.zip=a2f66c4eec9d56359ff449ac0fcc9659fd3866e898e4b2ca784c638495f12d877ff07e43316f25e9f795f415fada12278171e7b24b2dc8aec72b874817175d3d > > bcel-6.11.0-bom.json=529a2d9d97b27df780b2b6399ad2a8f748840b4d8c3e8c22d8c36d13dfd0b83ce71d40fb9785791f5689a627aaeba692dd1be8ff93f5dd565df5b5dec5e3bc92 > > bcel-6.11.0-bom.xml=124f3509f8e4a9339604d248d998921a862104662e5e84df8bef4b8471e0a2bf756345a579514c2f4a2ad2fd1ee55fcf579562e86ee6276b752c311960dc98bf > > bcel-6.11.0-javadoc.jar=0e7ada44516403a182badb318081e5df84c35412307c565f1e2371d7a239383ce5441e7d57563c54a3fd5a2344ce73460a676075978d89bef3c837289c7bc854 > > bcel-6.11.0-sources.jar=20fbbd878e3920370e921647a7cd7e08246cd1daf74640dec823506fd766d3aaf34f5206f888b443b7a6bb835e6019e73ad999b861337b53b93901d08db48bf0 > > bcel-6.11.0-src.tar.gz=bb081b15620bd31c10c9f0c2e3b9c0c3c6cb474402fee6bb2f61a8897184e3682fa5f9d46b7e7b0e7d09e0e86f79c9926d95ee155abffd396f3168b30d505efe > > bcel-6.11.0-src.zip=65120d2b75ff1a3b9d2a2165c1d3053e2c8fea4acd54abd970786f3b81bdb90c3f66fa0f0a5cadb105ea40d53ab12b3fd21dee9c49f1d080b8c61faadf74027b > > bcel-6.11.0-test-sources.jar=2b2c46d222e06e86a894a690e377b8d7c5a430eb018be64f1a5f5d4a3a0008ed6c4a3b1433e962d8db6462f2e7fc8b180dc42d32a1ec3f1f6e21bf995ede4faa > > bcel-6.11.0-tests.jar=53910305727256e734cbdc1e48fdcb38d5217d77fb31dd130987f714abab26f68cbf5d731d8c9d76a9ea128a8c6edf0b9f615844ffd452d44b678c10f56fc8dc > > org.apache.bcel_bcel-6.11.0.spdx.json=5c6f8df5ebd569459ee227621e1c38d70bebe18df157904d20cf60e8d52f116398f3aeb4a490698a8c73e66a02106abf0b8da29c65d17cc24b04c3f502a8f32f > > > > > > I have tested this with 'mvn -Ddoclint=none' and 'mvn -Ddoclint=none > > clean install site' using: > > > > openjdk version "25" 2025-09-16 > > OpenJDK Runtime Environment Homebrew (build 25) > > OpenJDK 64-Bit Server VM Homebrew (build 25, mixed mode, sharing) > > > > Apache Maven 3.9.11 (3e54c93a704957b63ee3494413a2b544fd3d825b) > > Maven home: /opt/homebrew/Cellar/maven/3.9.11/libexec > > Java version: 25, vendor: Homebrew, runtime: > > /opt/homebrew/Cellar/openjdk/25/libexec/openjdk.jdk/Contents/Home > > Default locale: en_US, platform encoding: UTF-8 > > OS name: "mac os x", version: "15.7.1", arch: "aarch64", family: "mac" > > > > Darwin Garys-MacBook-Pro.local 24.6.0 Darwin Kernel Version 24.6.0: > > Mon Aug 11 21:15:09 PDT 2025; > > root:xnu-11417.140.69.701.11~1/RELEASE_ARM64_T6041 arm64 > > > > Docker version 28.4.0, build d8eb465 > > > > Details of changes since 6.10.0 are in the release notes: > > > > https://dist.apache.org/repos/dist/dev/commons/bcel/6.11.0-RC1/RELEASE-NOTES.txt > > > > https://dist.apache.org/repos/dist/dev/commons/bcel/6.11.0-RC1/site/changes.html > > > > Site: > > > > https://dist.apache.org/repos/dist/dev/commons/bcel/6.11.0-RC1/site/index.html > > (note some *relative* links are broken and the 6.11.0 directories > > are not yet created - these will be OK once the site is deployed.) > > > > JApiCmp Report (compared to 6.10.0): > > > > https://dist.apache.org/repos/dist/dev/commons/bcel/6.11.0-RC1/site/japicmp.html > > > > RAT Report: > > > > https://dist.apache.org/repos/dist/dev/commons/bcel/6.11.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 86fdc7e2a11262cb) > > > > 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.11.0-RC1/source > > > > 1b) Check out the RC tag from git (optional) > > > > This is optional, as a reviewer must check source distributions as a > > minimum. > > > > git clone https://gitbox.apache.org/repos/asf/commons-bcel.git > > --branch commons-bcel-6.11.0-RC1 commons-bcel-6.11.0-RC1 > > cd commons-bcel-6.11.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]
