Thank you, Gang.

BTW, there was a community report for Java 25 + G1GC environment.

- JDK-8377811 [25u] G1: Optional Evacuations may evacuate pinned objects

I filed the corresponding ORC-2116 in order to mark as a known issue of Apache 
ORC 2.3.0 release note.

- ORC-2116 Java 25 G1GC: Optional Evacuations may evacuate pinned objects

Dongjoon.

On 2026/02/26 02:42:17 Gang Wu wrote:
> +1 (binding)
> 
> I verified the following:
> - Downloaded the source tarball, verified the signature and checksum.
> - Checked the git tag and commit hash.
> - Built successfully from the source tarball using Java 17.
> 
> Thanks for driving the release, Dongjoon!
> 
> On Thu, Feb 26, 2026 at 12:28 AM Dongjoon Hyun <[email protected]> wrote:
> 
> > +1
> >
> > I verified the sig and checksum values of RC0 artifacts.
> >
> > This is tested with
> > - Java 17/21/25
> > - Debian 12 and 13
> > - Ubuntu 24.04 and 26.04
> > - OracleLinux 9 and 10
> > - Amazon Linux 2023
> > - MacOS 15 and 26
> > - Apache Spark 4.2.0-SNAPSHOT
> >
> > Please see the release manage task list for the detail
> > - https://github.com/apache/orc/issues/2558
> >
> > Dongjoon.
> >
> > On 2026/02/25 11:58:51 Dongjoon Hyun wrote:
> > > Please vote on releasing the following candidate as Apache ORC version
> > > 2.3.0. This vote is open for the next 72 hours and passes if a majority
> > +1
> > > PMC votes are cast, with a minimum of 3 +1 votes.
> > >
> > > [ ] +1 Release this package as Apache ORC 2.3.0
> > > [ ] -1 Do not release this package because ...
> > >
> > > TAG:
> > > https://github.com/apache/orc/releases/tag/v2.3.0-rc0
> > > (commit: 970565f2aea99420c7fefcfa3e5853ce3103a91c)
> > >
> > > RELEASE FILES:
> > > https://dist.apache.org/repos/dist/dev/orc/v2.3.0-rc0
> > >
> > > STAGING REPOSITORY:
> > > https://repository.apache.org/content/repositories/orgapacheorc-1110
> > >
> > > LIST OF ISSUES:
> > > https://issues.apache.org/jira/projects/ORC/versions/12356052
> > > https://github.com/apache/orc/milestone/50?closed=1
> > >
> > > Thanks,
> > > Dongjoon.
> > >
> >
> 

Reply via email to