Hi Phil! +1 from me, I'm in favor of moving toward a 3.0.0 release.
Going through the open PRs, I'd like to see #1317 and #1318 merged before we cut the release. Once those are in, I'd suggest we cut the release branch and continue working on master, with the next version on master being 3.1.0 (as recommended). This would let us not only ship 3.0.0 — an important milestone in itself — but also make KnoxIDF available on master. Here's my +1. Cheers, Sandor On 2026/07/17 19:26:24 Phil Zampino wrote: > It seems to me about time for another Knox release. We've made a number of > changes and improvements, including things which are not > backward-compatible, hence the move to v3.0.0. > > Among the numerous improvements > <https://issues.apache.org/jira/browse/KNOX-3223?filter=-1&jql=project%20%3D%20KNOX%20AND%20status%20in%20(Resolved%2C%20Closed)%20AND%20fixVersion%20%3D%203.0.0%20order%20by%20updated%20DESC>, > we've: > > - Moved to a JDK17 build > - Upgraded the UIs > - Added RemoteAuth Provider > - Added APIKEY and CLIENTID token API extensions > - Implemented ICEBERG-REST service enhancements > - Added K8s support features > - Added Oracle database support as a TokenStateService backend > - Removed deprecated TokenStateService implementations > - Addressed numerous CVEs by way of dependency upgrades > > (Feel free to point out key improvements I've missed.) > > We have several open PRs, and we'll need to decide which of them must be > included in v3.0.0 > I'm personally on the fence about the servlet API migration PR (pull/1213 > <https://github.com/apache/knox/pull/1213>), so I am interested in what > others think about that one in particular. > > I think we should work toward a v3.0.0 release by the end of this month if > possible. > > What do you all think? > > Thanks, > Phil >
