All - I'd like to start the close down on this 2.0.0 release.
I am going to go through the 2.0.0 open JIRAs and start moving them out to 2.0.1. If you feel that you can close down on any given JIRA within the next week or so and want to get it into 2.0.0 feel free to justify on the JIRA and pull back into 2.0.0. thanks! --larry On Fri, Oct 28, 2022 at 5:25 PM Sandor Molnar <[email protected]> wrote: > Thanks for bringing this up, Phil! > > +1 for Knoxgiving! > > > > On Fri, Oct 28, 2022 at 9:59 PM Phil Zampino <[email protected]> wrote: > > > Sure, I'll serve as the Release Manager for 2.0 > > > > On Fri, Oct 28, 2022 at 3:18 PM larry mccay <[email protected]> wrote: > > > > > I am +1 on a Knoxgiving release for 2.0. > > > > > > @Philip Zampino <[email protected]> - would you like to volunteer as > > the > > > Release Manager for 2.0? > > > > > > > > > On Fri, Oct 28, 2022 at 2:55 PM Phil Zampino <[email protected]> > > wrote: > > > > > >> Knox 1.6.1 was released in January of this year. > > >> > > >> > > >> With the major (backward-incompatible) Log4j upgrade (KNOX-1462 > > >> <https://issues.apache.org/jira/browse/KNOX-1462>), and numerous > > >> resolved/closed issues > > >> < > > >> > > > https://issues.apache.org/jira/browse/KNOX-2831?filter=-1&jql=project%20%3D%20KNOX%20AND%20status%20in%20(Resolved%2C%20Closed)%20AND%20fixVersion%20%3D%202.0.0%20order%20by%20updated%20DESC > > >> > > > >> since, it seems an appropriate time to plan for a 2.0.0 release. > > >> > > >> > > >> I propose that we also address the Knox Token service impersonation ( > > >> KNOX-2714 <https://issues.apache.org/jira/browse/KNOX-2714>) and > > recently > > >> added DoS provider (KNOX-2806 > > >> <https://issues.apache.org/jira/browse/KNOX-2806>) implementations as > > >> part > > >> of this release. > > >> > > >> > > >> What do you think? Perhaps, it could be a "Knoxgiving" release? > > >> > > >> > > >> Thanks, > > >> > > >> Phil > > >> > > > > > >
