Sounds like a good idea! I'll kick start the process and file JIRAs as I encounter them!
Best, Sandeep On Mon, Jun 16, 2025 at 10:43 AM Phil Zampino <pzamp...@apache.org> wrote: > Thanks for the update. That sounds great. > > It probably won't be easy to create the JIRAs up-front since I suspect it > will probably be more of an iterative game of whack-a-mole, but let's make > sure to create JIRAs for the issues as they're encountered. > > Thanks for driving these efforts, > Phil > > On Mon, Jun 16, 2025 at 10:33 AM Sandeep Moré <moresand...@gmail.com> > wrote: > > > Hello Folks, > > Wanted to provide a quick update on where things stand. I was waiting on > > few bugs to get the release going > > 1. KNOX-3048 <https://issues.apache.org/jira/browse/KNOX-3048> > (Surrogate > > proxy user configuration for user groups) > > 2. KNOX-3084 <https://issues.apache.org/jira/browse/KNOX-3084> (Update > CM > > service discovery with the enhanced role configs endpoint) > > 3. KNOX-3094 <https://issues.apache.org/jira/browse/KNOX-3094> (Update > CM > > API swagger to 7.13.1) > > > > I fixed KNOX-3048 <https://issues.apache.org/jira/browse/KNOX-3048> last > > week so now we are down to two bugs. Once we get them committed we can > > start with the release process. > > In the meantime I will be creating a new branch to kick start work to > move > > Knox to JDK 17. > > > > Best, > > Sandeep > > > > On Sun, May 11, 2025 at 7:25 AM Sandeep Moré <moresand...@gmail.com> > > wrote: > > > > > Perfect, I'll start on it. > > > > > > On Wed, May 7, 2025 at 4:37 PM Phil Zampino <pzamp...@cloudera.com> > > wrote: > > > > > >> Thanks for volunteering Sandeep. > > >> > > >> I propose we perform a quick analysis of open issues to see if any > must > > >> be addressed for this next release. > > >> > > >> Thanks again, > > >> Phil > > >> > > >> On Fri, May 2, 2025 at 11:09 PM larry mccay <lmc...@apache.org> > wrote: > > >> > > >>> Thanks for volunteering, @Sandeep More <moresand...@gmail.com> ! > > >>> Sounds like a plan. > > >>> > > >>> I'm not sure that it is EOL'd but new development will need to go > into > > >>> the > > >>> new line. > > >>> We will need to support java 8 for security and maybe other bug fixes > > >>> for a > > >>> bit. > > >>> > > >>> On Thu, May 1, 2025 at 2:50 PM Sandeep Moré <moresand...@gmail.com> > > >>> wrote: > > >>> > > >>> > I have been thinking about this and I would like to volunteer as a > > >>> release > > >>> > manager for the last Java 8 knox release :) > > >>> > > > >>> > Once we release this we can continue with the JDK 17 development > > effort > > >>> > which might be significant, following are some of the things that > > come > > >>> to > > >>> > my mind that need to be considered: > > >>> > > > >>> > 1. Unit tests, especially Hadoop Unit tests are going to break, I > am > > >>> > anticipating that this will be a major work exploring what support > > >>> hadoop > > >>> > has for JDK 17. > > >>> > 2. Build changes, currently our builds run on JDK 8 and JDK 11, we > > will > > >>> > need to move away from them. > > >>> > 3. Dependency upgrades, like hadoop, we have libraries such as > Pac4J > > >>> that > > >>> > will need to be upgraded. This will have a significant impact and > > will > > >>> > involve some extensive testing (unit testing and functional > testing). > > >>> > 4. Notifications: We need a way to let the community know that > Java 8 > > >>> > support has been EOLd, this means sending out email communication > to > > >>> the > > >>> > committee mailing list (u...@knox.apache.org), updating docs, > > >>> updating > > >>> > knox website and wiki. > > >>> > > > >>> > Let me know if you have any questions or thoughts. > > >>> > > > >>> > Best, > > >>> > Sandeep > > >>> > > > >>> > On Mon, Apr 7, 2025 at 4:14 PM Sandeep Moré <moresand...@gmail.com > > > > >>> wrote: > > >>> > > > >>> > > Thanks for starting this thread Phil! > > >>> > > > > >>> > > We did some work to support running Knox on Java JDK. I recall a > > few > > >>> > > issues with compiling but those were mostly due to our intent of > > >>> > supporting > > >>> > > JDK 8. > > >>> > > Moving away from JDK 8 would help us a lot especially regarding > > >>> Pac4J and > > >>> > > spring upgrades. > > >>> > > > > >>> > > I think we would need a major Knox version for JDK 17 given this > > >>> would be > > >>> > > a breaking change. > > >>> > > > > >>> > > About releasing multiple versions, although I do not like the > idea > > >>> but I > > >>> > > think it would be nice/necessary if we release one last version > > with > > >>> CVE > > >>> > > fixes for folks to give them some runway to upgrade. > > >>> > > > > >>> > > Just my thoughts :) > > >>> > > > > >>> > > Best, > > >>> > > Sandeep > > >>> > > > > >>> > > On Mon, Apr 7, 2025 at 3:59 PM Phil Zampino <pzamp...@apache.org > > > > >>> wrote: > > >>> > > > > >>> > >> With Java 8 and 11 EOL approaching, and the associated > limitations > > >>> we've > > >>> > >> encountered wrt upgrading some dependencies, it seems about time > > to > > >>> move > > >>> > >> the Knox project to a more current Java version. I propose we > > begin > > >>> > >> development compiling with Java 17, and drop support for Java > > 8/11. > > >>> This > > >>> > >> will not be trivial, but will require some significant changes > to > > >>> the > > >>> > >> source. > > >>> > >> > > >>> > >> Would such a change constitute a major Knox version increment > > (e.g., > > >>> > >> 3.0.0)? > > >>> > >> > > >>> > >> Should we release one more version (e.g., 2.1.1) based on Java > > 8/11? > > >>> > >> > > >>> > >> Interested in your thoughts, > > >>> > >> Phil > > >>> > >> > > >>> > > > > >>> > > > >>> > > >> > > >> > > >> -- > > >> Phil Zampino > > >> > > >> > > >
