Here is the list of 16 for 2.0.0 as of now
https://issues.apache.org/jira/browse/KNOX-2839?jql=project%20%3D%20KNOX%20AND%20fixVersion%20%3D%202.0.0%20%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC

This is the list of 50-ish moved out to 2.1.0
https://issues.apache.org/jira/browse/KNOX-1299?jql=project%20%3D%20KNOX%20AND%20fixVersion%20%3D%202.1.0%20%20%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC

We will need a second pass on the first and a deep dive into the second
where we move some out to backlog or close as Won't Fix.


On Sat, Nov 12, 2022 at 4:22 PM larry mccay <lmc...@apache.org> wrote:

> I have gone through all open JIRAs for 2.0.0 and moved those out to 2.1.0
> that I felt were either unlikely or unnecessary to be resolved within the
> next week or so.
> There are 16 remaining for 2.0.0.
>
> Some of these may need to be moved out and others may have already been
> completed. We will need to make another pass to determine which fall into
> these categories.
> We should target a release candidate by the end of the next week - let's
> say the 19th.
>
> thoughts?
>
> --larry
>
> On Sat, Nov 12, 2022 at 3:49 PM larry mccay <lmc...@apache.org> wrote:
>
>> 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
>> <smol...@cloudera.com.invalid> wrote:
>>
>>> Thanks for bringing this up, Phil!
>>>
>>> +1 for Knoxgiving!
>>>
>>>
>>>
>>> On Fri, Oct 28, 2022 at 9:59 PM Phil Zampino <pzamp...@apache.org>
>>> wrote:
>>>
>>> > Sure, I'll serve as the Release Manager for 2.0
>>> >
>>> > On Fri, Oct 28, 2022 at 3:18 PM larry mccay <lmc...@apache.org> wrote:
>>> >
>>> > > I am +1 on a Knoxgiving release for 2.0.
>>> > >
>>> > > @Philip Zampino <pzamp...@gmail.com> - would you like to volunteer
>>> as
>>> > the
>>> > > Release Manager for 2.0?
>>> > >
>>> > >
>>> > > On Fri, Oct 28, 2022 at 2:55 PM Phil Zampino <pzamp...@apache.org>
>>> > 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
>>> > >>
>>> > >
>>> >
>>>
>>

Reply via email to