We have fixed quite a few bugs and added some significant enhancements since
Apache Commons JCS 3.1 was released, so I would like to release Apache Commons
JCS 3.2.
Apache Commons JCS 3.2 rc1 is available for review here:
https://dist.apache.org/repos/dist/dev/commons/jcs/3.2-rc1 (svn revisi
> Am 22.08.2023 um 15:14 schrieb Thomas Vandahl :
>
> We have fixed quite a few bugs and added some significant enhancements since
> Apache Commons JCS 3.1 was released, so I would like to release Apache
> Commons JCS 3.2.
...
> [X] +1 Release these artifacts
> [ ] +0 OK, but...
> [ ] -0 OK
Something went wrong somewhere because the tag in this email points to a
3.3-SNAPSHOT version instead of 3.2:
> The Git tag commons-jcs-3.2-rc1 commit for this RC is
eb9c5b36b48f2b6f45fba7986d46c7006cfb5c4c which you can browse here:
https://gitbox.apache.org/repos/asf?p=commons-jcs.git;a=commit;
Greetings!
JDK 21 is now in the Release Candidate Phase so everything is on track for the
Java 21 GA release on September 19th! If you haven't done so, please start
testing your project(s) using JDK 22 Early-Access builds and let us know the
results.
In other news, the JVM Language Summit took
Hi Gary,
> Am 22.08.2023 um 15:58 schrieb Gary Gregory :
>
> Something went wrong somewhere because the tag in this email points to a
> 3.3-SNAPSHOT version instead of 3.2:
>
>> The Git tag commons-jcs-3.2-rc1 commit for this RC is
> eb9c5b36b48f2b6f45fba7986d46c7006cfb5c4c which you can browse
That commit looks good.
Gary
On Tue, Aug 22, 2023, 11:33 AM Thomas Vandahl wrote:
> Hi Gary,
>
> > Am 22.08.2023 um 15:58 schrieb Gary Gregory :
> >
> > Something went wrong somewhere because the tag in this email points to a
> > 3.3-SNAPSHOT version instead of 3.2:
> >
> >> The Git tag commons
