+1 (binding)

- signatures and SHA-512 ok (KEYS from dist/release)
- src archives match the tag d64750f0e (minus git dotfiles)
- LICENSE/NOTICE present, no unexpected binaries, RAT passes
- built from the src archive with JDK 21 incl. tests: ok
- staged jars target Java 21, bin CLI test ok

Minor, for 3.0.1:
- opennlp.iml slipped into the src archive
- SymSpell MIT text is in NOTICE only, should go into LICENSE
- bin LICENSE morfologik section still has "Copyright (c) <YEAR> <OWNER>"

Richard

On 2026/11/12 10:07:33 Martin Wiesner via dev wrote:
> Hi all,
> 
> I have posted a first release candidate for the Apache OpenNLP 3.0.0 release 
> and it is ready for testing.
> 
> The 3.x release line of Apache OpenNLP introduces only a minimal set of 
> breaking changes while significantly modularizing the project to improve 
> library usage and future extensibility. 
> The core concepts and API remains stable and fully compatible with 2.x, so 
> existing projects can continue using the opennlp-tools artifact without 
> modifications.
> 
> ######
> The 3.0.0 release delivers 250+ resolved issues, including several epics, 
> many feature additions, and bug fixes as well. Java 21 or later is now 
> required.
> The core *ME classes can be shared across threads. The ThreadSafe*ME wrappers 
> have been deprecated.
> Please check the release notes (JIRA + GITHUB), as linked below, for further 
> details on what's included / covered with the 3.0.0 release.
> 
> Housekeeping updates include moving to Apache Parent 40, gRPC 1.85.1, ONNX 
> Runtime 1.31.1, and Apache UIMA 3.7.0. 
> Documentation improvements, esp. for the Dev Manual, have also arrived.
> ######
> 
> Thank you to everyone who contributed to this release, including all of our 
> users and the people who submitted bug reports, contributed code or 
> documentation enhancements.
> 
> The release was made using the OpenNLP release process, documented on the 
> website:
> https://opennlp.apache.org/release.html
> 
> Maven Repo:
> https://repository.apache.org/content/repositories/orgapacheopennlp-1075
> 
> <repositories>
> <repository>
> <id>opennlp-3.0.0-RC1</id>
> <name>Testing OpenNLP 3.0.0 release candidate</name>
> <url>
> https://repository.apache.org/content/repositories/orgapacheopennlp-1075
> </url>
> </repository>
> </repositories>
> 
> Binaries & Source:
> 
> https://dist.apache.org/repos/dist/dev/opennlp/opennlp-3.0.0-rc1/
> 
> Tag:
> 
> https://github.com/apache/opennlp/releases/tag/opennlp-3.0.0
> 
> Tag Hash: d64750f0e8114fd77dc98c5ea1fe6821febcebf1
> 
> Release notes:
> 
> (GITHUB) 
> https://github.com/apache/opennlp/releases/tag/untagged-7d038a2d8c4609c230f3
> (JIRA) 
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311215&version=12356725
> 
> The results of the eval tests for the aforementioned tag can be found
> here: https://ci-builds.apache.org/job/OpenNLP/job/eval-tests-releases/40/
> 
> Reminder: The up-2-date KEYS file for signature verification can be
> found here: https://dist.apache.org/repos/dist/release/opennlp/KEYS
> 
> Checklist for reference:
> 
> [ ] Both source (tar.gz/zip) and binary artifacts (tar.gz/zip) are present, 
> along with .asc and .sha512 files for each.
> [ ] PGP signatures are valid for the release artifacts using the KEYS file 
> from dist.apache.org
> [ ] SHA512 checksums are correct and verified.
> [ ] LICENSE and NOTICE files exist and are accurate.
> [ ] No unexpected binary files in the source release.
> [ ] All source files have appropriate ASF headers (excluding generated files 
> and legacy files).
> [ ] Build completes successfully from source and the instruction to do so are 
> clear.
> 
> Please vote on releasing these packages as Apache OpenNLP 3.0.0: The vote is 
> open for at least the next 72 hours.
> 
> Only votes from OpenNLP PMC are binding, but everyone is welcome to check the 
> release candidate and vote.
> The vote passes if at least three binding +1 votes are cast.
> 
> Please VOTE
> 
> [+1] go ship it
> [+0] meh, don't care
> [-1] stop, there is a ${showstopper}
> 
> Thanks!
> Martin | mawiesne

Reply via email to