+1 all looks good

> On Jan 7, 2024, at 3:20 PM, Gary Gregory <garydgreg...@gmail.com> wrote:
> 
> We have fixed BCEL-370 for SpotBugs and added some enhancements since
> Apache Commons BCEL 6.8.0 was released, so I would like to release
> Apache Commons BCEL 6.8.1.
> 
> Apache Commons BCEL 6.8.1 RC1 is available for review here:
>    https://dist.apache.org/repos/dist/dev/commons/bcel/6.8.1-RC1 (svn
> revision 66459)
> 
> The Git tag commons-bcel-6.8.1-RC1 commit for this RC is
> 6785009095d66a4a2bc01e64d25de987847eb114 which you can browse here:
>    
> https://gitbox.apache.org/repos/asf?p=commons-bcel.git;a=commit;h=6785009095d66a4a2bc01e64d25de987847eb114
> You may checkout this tag using:
>    git clone https://gitbox.apache.org/repos/asf/commons-bcel.git
> --branch commons-bcel-6.8.1-RC1 commons-bcel-6.8.1-RC1
> 
> Maven artifacts are here:
>    
> https://repository.apache.org/content/repositories/orgapachecommons-1685/org/apache/bcel/bcel/6.8.1/
> 
> These are the artifacts and their hashes:
> 
> #Release SHA-512s
> #Sun Jan 07 20:05:28 UTC 2024
> bcel-6.8.1-bin.tar.gz=137eefdeb8921bd2b82f24d560fe73aeaea7af77eb2db0b84b321159cc737490fbca709402094d8f54ca4921944608b1e54cfe3caa72c96ced8d65ffa23eb10d
> bcel-6.8.1-bin.zip=418ad7bd2f1f0d7176b0f4e9d64964ed7e3d486599db55b3ffa112948ace111e1372a5d406df5746f384f54edba58df9fd1022eb522c845ab64c7eae5551b9f8
> bcel-6.8.1-bom.json=679d5be5ab9aafc51bac9ac72f86d17c39c9a62237fd3fcebc25cda40001d753dd98db2578df8c992f4a156c6ebd514bf686a5a32a6da55034f9ebbca5cccd8e
> bcel-6.8.1-bom.xml=9a6d1d5eb3debd0cd23a4d8a46885ef55f4b16ea86042a3d3c4f6d19ea83e5039a1c94a27dcb1ae23091a0bff4e5ede652b8701d4cca9d6cfa925a0073ad6c60
> bcel-6.8.1-javadoc.jar=eee243d6898d3ddd78c0edafef2d3e120886aae2b1f60bc8e825e8f39c3008f4184563349e6f354b04bd3198ada34e66bacd793f1fd2b987a880497dad7566f1
> bcel-6.8.1-sources.jar=7af00081e0180f84d70c732b6099cefe2fd3f07bd13a697e471a9d7f7af29f31580d3f1271645b8e58d583bf5c13587fcfe9f2df81334a20c90314c1bd876a35
> bcel-6.8.1-src.tar.gz=1a38f4603bfe8692e4fc71a911fbb37ddc30ee5afa270d4b36f0325879a555df2cab34e2abf38645a3c7b780e30dec516a0eac21a0d7e18ff412a5762282360e
> bcel-6.8.1-src.zip=f6d4c953cf64995fc96c7c34c08e15ad1daad410c97db5efdf7acc1e70fa00f9c7c560aa9006fb10f46975268250663534fc45e635d25f090b2f4d3531a1c2a8
> bcel-6.8.1-test-sources.jar=3114e0cbaee9ba42ba57c860a91574f3f36ceb018e71a24003443353b59763bb885160c75c886ffb2e703933b8dfa27e33a694bca39db7f51150f263964593da
> bcel-6.8.1-tests.jar=1588bb81b339bc8f645335630ab31bf8df23776fd5757e4d608477e914feff15876bf3e2446c1ae28fb62cb71249da3c667298b543619e456468682dad14c938
> org.apache.bcel_bcel-6.8.1.spdx.json=7df4647adfb7a15ca9c58ac5c852898e0513cd3b8701686e1ed29b2bf2edd1c6da44a3ee6e8f69b398861b05c2e0ad60fb6960d99e1e309cbe3fd142c922cb1b
> 
> I have tested this with:
> 
> mvn -V -Prelease -Ptest-deploy -P jacoco -P japicmp clean package site deploy
> 
> Using:
> 
> Apache Maven 3.9.6 (bc0240f3c744dd6b6ec2920b3cd08dcc295161ae)
> Maven home: /usr/local/Cellar/maven/3.9.6/libexec
> Java version: 17.0.9, vendor: Homebrew, runtime:
> /usr/local/Cellar/openjdk@17/17.0.9/libexec/openjdk.jdk/Contents/Home
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "14.2.1", arch: "x86_64", family: "mac"
> 
> Darwin **** 23.2.0 Darwin Kernel Version 23.2.0: Wed Nov 15 21:54:10
> PST 2023; root:xnu-10002.61.3~2/RELEASE_X86_64 x86_64
> 
> Details of changes since 6.8.0 are in the release notes:
>    
> https://dist.apache.org/repos/dist/dev/commons/bcel/6.8.1-RC1/RELEASE-NOTES.txt
>    
> https://dist.apache.org/repos/dist/dev/commons/bcel/6.8.1-RC1/site/changes-report.html
> 
> Site:
>    
> https://dist.apache.org/repos/dist/dev/commons/bcel/6.8.1-RC1/site/index.html
>    (note some *relative* links are broken and the 6.8.1 directories
> are not yet created - these will be OK once the site is deployed.)
> 
> JApiCmp Report (compared to 6.8.0):
>    
> https://dist.apache.org/repos/dist/dev/commons/bcel/6.8.1-RC1/site/japicmp.html
> 
> RAT Report:
>    
> https://dist.apache.org/repos/dist/dev/commons/bcel/6.8.1-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)
> 
> For following is intended as a helper and refresher for reviewers.
> 
> Validating a release candidate
> ==============================
> 
> These guidelines are NOT complete.
> 
> Requirements: Git, Java, Maven.
> 
> You can validate a release from a release candidate (RC) tag as follows.
> 
> 1a) Clone and checkout the RC tag
> 
> git clone https://gitbox.apache.org/repos/asf/commons-bcel.git
> --branch commons-bcel-6.8.1-RC1 commons-bcel-6.8.1-RC1
> cd commons-bcel-6.8.1-RC1
> 
> 1b) Download and unpack the source archive from:
> 
> https://dist.apache.org/repos/dist/dev/commons/bcel/6.8.1-RC1/source
> 
> 2) Check Apache licenses
> 
> This step is not required if the site includes a RAT report page which
> you then must check.
> 
> mvn apache-rat:check
> 
> 3) Check binary compatibility
> 
> Older components still use Apache Clirr:
> 
> This step is not required if the site includes a Clirr report page
> which you then must check.
> 
> mvn clirr:check
> 
> Newer components use JApiCmp with the japicmp Maven Profile:
> 
> This step is not required if the site includes a JApiCmp report page
> which you then must check.
> 
> mvn install -DskipTests -P japicmp japicmp:cmp
> 
> 4) Build the package
> 
> 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
> 
> 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
> 
> Note that the project reports are created for each module.
> Modules can be accessed using the 'Project Modules' link under
> the 'Project Information' menu (see <path-to-site>/modules.html).
> 
> -the end-
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Reply via email to