Hi Thomas,

Thank you for preparing a release candidate.

Something looks confusing in the source tree:

In git master marked as version 3.2.2-SNAPSHOT, all of the Maven
modules follow the normal naming convention where directory names are
artifact IDs, for example, "commons-jcs3-core":
https://github.com/apache/commons-jcs/tree/master/commons-jcs3-core

But at the release tag commons-jcs3-3.2.1-rc1, all of the folders are
missing the "3" postfix:
https://github.com/apache/commons-jcs/tree/commons-jcs3-3.2.1-rc1 ?

TY,
Gary

On Thu, Apr 4, 2024 at 10:52 AM Thomas Vandahl <t...@apache.org> wrote:
>
> Hi folks,
>
> We have fixed a few bugs since Apache Commons JCS 3.2 was released, so I 
> would like to release Apache Commons JCS 3.2.1.
>
> Apache Commons JCS 3.2.1 rc1 is available for review here:
>     https://dist.apache.org/repos/dist/dev/commons/jcs/3.2.1-rc1 (svn 
> revision 68312)
>
> The Git tag commons-jcs3-3.2.1-rc1 commit for this RC is 
> 0b20664b6c60b025cfe0e95c33e86f3239822a12 which you can browse here:
>     
> https://gitbox.apache.org/repos/asf?p=commons-jcs.git;a=commit;h=0b20664b6c60b025cfe0e95c33e86f3239822a12
> You may checkout this tag using:
>     git clone https://gitbox.apache.org/repos/asf/commons-jcs.git --branch 
> commons-jcs3-3.2.1-rc1 commons-jcs3-3.2.1-rc1
>
> Maven artifacts are here:
>     
> https://repository.apache.org/content/repositories/orgapachecommons-1712/org/apache/commons/commons-jcs3/3.2.1/
>
> These are the artifacts and their hashes:
>
> 5ea0cfd1ea5d17689ce35fd4a26ad104028b2b0d3209cf8c3d58d1a8e62c77442de95d51af278ad810a28117d0297725ded41b18553e05212dfc9e9db1dd185c
>   commons-jcs3-dist-3.2.1-bin.tar.gz
> ce7151767ebcf5ce08c9e91689ef1b240344b874963edc3042c0a6958e02deb95551aa9de1a8f63fd6e87198f179ad90501a0b76f96cf6c2c10cd546e867c8bf
>   commons-jcs3-dist-3.2.1-bin.zip
> 8abc08f18edf6fcd86d9fcb8834ef4584d6932a6a7dca8936b199b6aec3622e634c20f639fdb5cd1077d2492e1a8fd3dafb0ceb9a259127c3dfc3ec54d6cea1b
>   commons-jcs3-dist-3.2.1-src.tar.gz
> e7a2796bc07b9da4d8e5db0423baa758e0e139e8cdc35aa6d50e32cdfa9163b874eeedfd52e90c599049faa1963546109389fb967e60df8a0198a025a3d75869
>   commons-jcs3-dist-3.2.1-src.zip
>
> I have tested this with ***'mvn clean install site'*** using:
>
> Apache Maven 3.8.4 (9b656c72d54e5bacbed989b64718c159fe39b537)
> Java version: 1.8.0_311, vendor: Oracle Corporation, runtime: 
> /Library/Java/JavaVirtualMachines/jdk1.8.0_311.jdk/Contents/Home/jre
> Default locale: de_DE, platform encoding: UTF-8
> OS name: "mac os x", version: "10.16", arch: "x86_64", family: "mac"
>
> Details of changes since 3.2 are in the release notes:
>     
> https://dist.apache.org/repos/dist/dev/commons/jcs/3.2.1-rc1/RELEASE-NOTES.txt
>     
> https://dist.apache.org/repos/dist/dev/commons/jcs/3.2.1-rc1/site/changes-report.html
>
> Site:
>     
> https://dist.apache.org/repos/dist/dev/commons/jcs/3.2.1-rc1/site/index.html
>     (note some *relative* links are broken and the 3.2.1 directories are not 
> yet created - these will be OK once the site is deployed.)
>
> JApiCmp Report (compared to 3.2):
>     
> https://dist.apache.org/repos/dist/dev/commons/jcs/3.2.1-rc1/site/commons-jcs3-core/japicmp.html
> RAT Report:
>     
> https://dist.apache.org/repos/dist/dev/commons/jcs/3.2.1-rc1/site/commons-jcs3-core/rat-report.html
>
> KEYS:
>     https://www.apache.org/dist/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,
>
> Bye, Thomas
> Release Manager (using key 88817402)
>
>
>
>
> ---------------------------------------------------------------------
> 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