You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@yunikorn.apache.org by Wilfred Spiegelenburg <wi...@apache.org> on 2022/01/12 00:11:18 UTC
[DISCUSS] v0.12.2 release to allow K8s 1.22 and K8s 1.23 deployments
Over the last weeks Craig and I have been working on getting the
admission controller deployment updated. These changes were committed
yesterday as YUNIKORN-941. The main goal was to move away from old K8s
objects and API calls and remove the scripts for certificate creation.
With the changes committed deployments and e2e tests against K8s1.22
and K8s 1.23 are no longer failing.
I would like to propose that we release v0.12.2 with just the changes
for the admission controller to allow deployments on the latest
versions of K8s. Since Craig is the person that has been driving this
code change I would like to propose him as the release manager.
This is the list of changes related to YUNIKORN-941. It includes a
number of other jiras as they are all fixed by the new deployment:
* YUNIKORN-995
* YUNIKORN-938
* YUNIKORN-947
* YUNIKORN-625
* YUNIKORN-726
It has one jira it dependents on: YUNIKORN-928
Wilfred
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@yunikorn.apache.org
For additional commands, e-mail: dev-help@yunikorn.apache.org
Re: [DISCUSS] v0.12.2 release to allow K8s 1.22 and K8s 1.23 deployments
Posted by Weiwei Yang <ww...@apache.org>.
Thank you, Craig, really appreciate your help!!
On Wed, Jan 12, 2022 at 8:32 AM Craig Condit <ap...@craigcondit.com> wrote:
> Thank you all for the good discussion. I will be happy to act as release
> manager for 0.12.2 and will begin the process right away.
>
>
> Craig
>
>
> > On Jan 11, 2022, at 11:33 PM, Wilfred Spiegelenburg <wi...@apache.org>
> wrote:
> >
> > We have already run the e2e tests against k8s 1.22 and k8s 1.23. They
> > all passed.
> > Based on that result we do not expect any further work that is needed
> > to run the scheduler on the later version(s).
> >
> > In the branch-0.12 we will update the e2e test matrix to include the
> > new release(s).
> > The release process will publish new helm charts automatically. That
> > is part of what the release manager must do.
> > I have logged the release umbrella jira YUNIKORN-1010 [1]
> >
> > The upgrade is the same as it has always been. A simple helm upgrade
> > should trigger the upgrade as per normal.
> >
> > Wilfred
> >
> > [1] https://issues.apache.org/jira/browse/YUNIKORN-1010
> >
> > On Wed, 12 Jan 2022 at 15:48, Weiwei Yang <ww...@apache.org> wrote:
> >>
> >> Apart from the issues that have been fixed.
> >> Can we also make sure
> >>
> >> - Update e2e test matrix to include 1.22
> >> - Update the user doc to include guidelines of how to do upgrade
> >> - Update and publish the new helm charts in the helm chart repo
> >>
> >> can we have an umbrella JIRA to track all the remaining issues for 1.22?
> >> People can help out some of unfinished tasks.
> >>
> >> On Tue, Jan 11, 2022 at 8:44 PM Weiwei Yang <ww...@apache.org> wrote:
> >>
> >>> Fantastic, thank you, Wilfred, Craig for getting this solved!
> >>> +1 of having a 1.22 release, to unblock people who use 1.22+ K8s
> versions.
> >>>
> >>>
> >>> On Tue, Jan 11, 2022 at 8:40 PM Chaoran Yu <yu...@gmail.com>
> >>> wrote:
> >>>
> >>>> +1 because it unblocks some users.
> >>>>
> >>>> On Tue, Jan 11, 2022 at 4:35 PM Sunil Govindan <su...@apache.org>
> wrote:
> >>>>
> >>>>> I think this will help our customers who are stuck with K8s 1.22
> issue
> >>>>> before 1.0 is out.
> >>>>>
> >>>>> +1 to the proposal
> >>>>>
> >>>>> Thanks
> >>>>> Sunil
> >>>>>
> >>>>> On Tue, Jan 11, 2022 at 4:11 PM Wilfred Spiegelenburg <
> >>>> wilfreds@apache.org
> >>>>>>
> >>>>> wrote:
> >>>>>
> >>>>>> Over the last weeks Craig and I have been working on getting the
> >>>>>> admission controller deployment updated. These changes were
> committed
> >>>>>> yesterday as YUNIKORN-941. The main goal was to move away from old
> K8s
> >>>>>> objects and API calls and remove the scripts for certificate
> creation.
> >>>>>>
> >>>>>> With the changes committed deployments and e2e tests against K8s1.22
> >>>>>> and K8s 1.23 are no longer failing.
> >>>>>> I would like to propose that we release v0.12.2 with just the
> changes
> >>>>>> for the admission controller to allow deployments on the latest
> >>>>>> versions of K8s. Since Craig is the person that has been driving
> this
> >>>>>> code change I would like to propose him as the release manager.
> >>>>>>
> >>>>>> This is the list of changes related to YUNIKORN-941. It includes a
> >>>>>> number of other jiras as they are all fixed by the new deployment:
> >>>>>> * YUNIKORN-995
> >>>>>> * YUNIKORN-938
> >>>>>> * YUNIKORN-947
> >>>>>> * YUNIKORN-625
> >>>>>> * YUNIKORN-726
> >>>>>> It has one jira it dependents on: YUNIKORN-928
> >>>>>>
> >>>>>> Wilfred
> >>>>>>
> >>>>>>
> ---------------------------------------------------------------------
> >>>>>> To unsubscribe, e-mail: dev-unsubscribe@yunikorn.apache.org
> >>>>>> For additional commands, e-mail: dev-help@yunikorn.apache.org
> >>>>>>
> >>>>>>
> >>>>>
> >>>>
> >>>
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@yunikorn.apache.org
> > For additional commands, e-mail: dev-help@yunikorn.apache.org
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@yunikorn.apache.org
> For additional commands, e-mail: dev-help@yunikorn.apache.org
>
>
Re: [DISCUSS] v0.12.2 release to allow K8s 1.22 and K8s 1.23 deployments
Posted by Craig Condit <ap...@craigcondit.com>.
Thank you all for the good discussion. I will be happy to act as release manager for 0.12.2 and will begin the process right away.
Craig
> On Jan 11, 2022, at 11:33 PM, Wilfred Spiegelenburg <wi...@apache.org> wrote:
>
> We have already run the e2e tests against k8s 1.22 and k8s 1.23. They
> all passed.
> Based on that result we do not expect any further work that is needed
> to run the scheduler on the later version(s).
>
> In the branch-0.12 we will update the e2e test matrix to include the
> new release(s).
> The release process will publish new helm charts automatically. That
> is part of what the release manager must do.
> I have logged the release umbrella jira YUNIKORN-1010 [1]
>
> The upgrade is the same as it has always been. A simple helm upgrade
> should trigger the upgrade as per normal.
>
> Wilfred
>
> [1] https://issues.apache.org/jira/browse/YUNIKORN-1010
>
> On Wed, 12 Jan 2022 at 15:48, Weiwei Yang <ww...@apache.org> wrote:
>>
>> Apart from the issues that have been fixed.
>> Can we also make sure
>>
>> - Update e2e test matrix to include 1.22
>> - Update the user doc to include guidelines of how to do upgrade
>> - Update and publish the new helm charts in the helm chart repo
>>
>> can we have an umbrella JIRA to track all the remaining issues for 1.22?
>> People can help out some of unfinished tasks.
>>
>> On Tue, Jan 11, 2022 at 8:44 PM Weiwei Yang <ww...@apache.org> wrote:
>>
>>> Fantastic, thank you, Wilfred, Craig for getting this solved!
>>> +1 of having a 1.22 release, to unblock people who use 1.22+ K8s versions.
>>>
>>>
>>> On Tue, Jan 11, 2022 at 8:40 PM Chaoran Yu <yu...@gmail.com>
>>> wrote:
>>>
>>>> +1 because it unblocks some users.
>>>>
>>>> On Tue, Jan 11, 2022 at 4:35 PM Sunil Govindan <su...@apache.org> wrote:
>>>>
>>>>> I think this will help our customers who are stuck with K8s 1.22 issue
>>>>> before 1.0 is out.
>>>>>
>>>>> +1 to the proposal
>>>>>
>>>>> Thanks
>>>>> Sunil
>>>>>
>>>>> On Tue, Jan 11, 2022 at 4:11 PM Wilfred Spiegelenburg <
>>>> wilfreds@apache.org
>>>>>>
>>>>> wrote:
>>>>>
>>>>>> Over the last weeks Craig and I have been working on getting the
>>>>>> admission controller deployment updated. These changes were committed
>>>>>> yesterday as YUNIKORN-941. The main goal was to move away from old K8s
>>>>>> objects and API calls and remove the scripts for certificate creation.
>>>>>>
>>>>>> With the changes committed deployments and e2e tests against K8s1.22
>>>>>> and K8s 1.23 are no longer failing.
>>>>>> I would like to propose that we release v0.12.2 with just the changes
>>>>>> for the admission controller to allow deployments on the latest
>>>>>> versions of K8s. Since Craig is the person that has been driving this
>>>>>> code change I would like to propose him as the release manager.
>>>>>>
>>>>>> This is the list of changes related to YUNIKORN-941. It includes a
>>>>>> number of other jiras as they are all fixed by the new deployment:
>>>>>> * YUNIKORN-995
>>>>>> * YUNIKORN-938
>>>>>> * YUNIKORN-947
>>>>>> * YUNIKORN-625
>>>>>> * YUNIKORN-726
>>>>>> It has one jira it dependents on: YUNIKORN-928
>>>>>>
>>>>>> Wilfred
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: dev-unsubscribe@yunikorn.apache.org
>>>>>> For additional commands, e-mail: dev-help@yunikorn.apache.org
>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@yunikorn.apache.org
> For additional commands, e-mail: dev-help@yunikorn.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@yunikorn.apache.org
For additional commands, e-mail: dev-help@yunikorn.apache.org
Re: [DISCUSS] v0.12.2 release to allow K8s 1.22 and K8s 1.23 deployments
Posted by Wilfred Spiegelenburg <wi...@apache.org>.
We have already run the e2e tests against k8s 1.22 and k8s 1.23. They
all passed.
Based on that result we do not expect any further work that is needed
to run the scheduler on the later version(s).
In the branch-0.12 we will update the e2e test matrix to include the
new release(s).
The release process will publish new helm charts automatically. That
is part of what the release manager must do.
I have logged the release umbrella jira YUNIKORN-1010 [1]
The upgrade is the same as it has always been. A simple helm upgrade
should trigger the upgrade as per normal.
Wilfred
[1] https://issues.apache.org/jira/browse/YUNIKORN-1010
On Wed, 12 Jan 2022 at 15:48, Weiwei Yang <ww...@apache.org> wrote:
>
> Apart from the issues that have been fixed.
> Can we also make sure
>
> - Update e2e test matrix to include 1.22
> - Update the user doc to include guidelines of how to do upgrade
> - Update and publish the new helm charts in the helm chart repo
>
> can we have an umbrella JIRA to track all the remaining issues for 1.22?
> People can help out some of unfinished tasks.
>
> On Tue, Jan 11, 2022 at 8:44 PM Weiwei Yang <ww...@apache.org> wrote:
>
> > Fantastic, thank you, Wilfred, Craig for getting this solved!
> > +1 of having a 1.22 release, to unblock people who use 1.22+ K8s versions.
> >
> >
> > On Tue, Jan 11, 2022 at 8:40 PM Chaoran Yu <yu...@gmail.com>
> > wrote:
> >
> >> +1 because it unblocks some users.
> >>
> >> On Tue, Jan 11, 2022 at 4:35 PM Sunil Govindan <su...@apache.org> wrote:
> >>
> >> > I think this will help our customers who are stuck with K8s 1.22 issue
> >> > before 1.0 is out.
> >> >
> >> > +1 to the proposal
> >> >
> >> > Thanks
> >> > Sunil
> >> >
> >> > On Tue, Jan 11, 2022 at 4:11 PM Wilfred Spiegelenburg <
> >> wilfreds@apache.org
> >> > >
> >> > wrote:
> >> >
> >> > > Over the last weeks Craig and I have been working on getting the
> >> > > admission controller deployment updated. These changes were committed
> >> > > yesterday as YUNIKORN-941. The main goal was to move away from old K8s
> >> > > objects and API calls and remove the scripts for certificate creation.
> >> > >
> >> > > With the changes committed deployments and e2e tests against K8s1.22
> >> > > and K8s 1.23 are no longer failing.
> >> > > I would like to propose that we release v0.12.2 with just the changes
> >> > > for the admission controller to allow deployments on the latest
> >> > > versions of K8s. Since Craig is the person that has been driving this
> >> > > code change I would like to propose him as the release manager.
> >> > >
> >> > > This is the list of changes related to YUNIKORN-941. It includes a
> >> > > number of other jiras as they are all fixed by the new deployment:
> >> > > * YUNIKORN-995
> >> > > * YUNIKORN-938
> >> > > * YUNIKORN-947
> >> > > * YUNIKORN-625
> >> > > * YUNIKORN-726
> >> > > It has one jira it dependents on: YUNIKORN-928
> >> > >
> >> > > Wilfred
> >> > >
> >> > > ---------------------------------------------------------------------
> >> > > To unsubscribe, e-mail: dev-unsubscribe@yunikorn.apache.org
> >> > > For additional commands, e-mail: dev-help@yunikorn.apache.org
> >> > >
> >> > >
> >> >
> >>
> >
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@yunikorn.apache.org
For additional commands, e-mail: dev-help@yunikorn.apache.org
Re: [DISCUSS] v0.12.2 release to allow K8s 1.22 and K8s 1.23 deployments
Posted by Chenya Zhang <ch...@gmail.com>.
+1 thanks Wilfred and Craig for driving YUNIKORN-941! Look forward to the
release!
On Tue, Jan 11, 2022 at 8:48 PM Weiwei Yang <ww...@apache.org> wrote:
> Apart from the issues that have been fixed.
> Can we also make sure
>
> - Update e2e test matrix to include 1.22
> - Update the user doc to include guidelines of how to do upgrade
> - Update and publish the new helm charts in the helm chart repo
>
> can we have an umbrella JIRA to track all the remaining issues for 1.22?
> People can help out some of unfinished tasks.
>
> On Tue, Jan 11, 2022 at 8:44 PM Weiwei Yang <ww...@apache.org> wrote:
>
> > Fantastic, thank you, Wilfred, Craig for getting this solved!
> > +1 of having a 1.22 release, to unblock people who use 1.22+ K8s
> versions.
> >
> >
> > On Tue, Jan 11, 2022 at 8:40 PM Chaoran Yu <yu...@gmail.com>
> > wrote:
> >
> >> +1 because it unblocks some users.
> >>
> >> On Tue, Jan 11, 2022 at 4:35 PM Sunil Govindan <su...@apache.org>
> wrote:
> >>
> >> > I think this will help our customers who are stuck with K8s 1.22 issue
> >> > before 1.0 is out.
> >> >
> >> > +1 to the proposal
> >> >
> >> > Thanks
> >> > Sunil
> >> >
> >> > On Tue, Jan 11, 2022 at 4:11 PM Wilfred Spiegelenburg <
> >> wilfreds@apache.org
> >> > >
> >> > wrote:
> >> >
> >> > > Over the last weeks Craig and I have been working on getting the
> >> > > admission controller deployment updated. These changes were
> committed
> >> > > yesterday as YUNIKORN-941. The main goal was to move away from old
> K8s
> >> > > objects and API calls and remove the scripts for certificate
> creation.
> >> > >
> >> > > With the changes committed deployments and e2e tests against K8s1.22
> >> > > and K8s 1.23 are no longer failing.
> >> > > I would like to propose that we release v0.12.2 with just the
> changes
> >> > > for the admission controller to allow deployments on the latest
> >> > > versions of K8s. Since Craig is the person that has been driving
> this
> >> > > code change I would like to propose him as the release manager.
> >> > >
> >> > > This is the list of changes related to YUNIKORN-941. It includes a
> >> > > number of other jiras as they are all fixed by the new deployment:
> >> > > * YUNIKORN-995
> >> > > * YUNIKORN-938
> >> > > * YUNIKORN-947
> >> > > * YUNIKORN-625
> >> > > * YUNIKORN-726
> >> > > It has one jira it dependents on: YUNIKORN-928
> >> > >
> >> > > Wilfred
> >> > >
> >> > >
> ---------------------------------------------------------------------
> >> > > To unsubscribe, e-mail: dev-unsubscribe@yunikorn.apache.org
> >> > > For additional commands, e-mail: dev-help@yunikorn.apache.org
> >> > >
> >> > >
> >> >
> >>
> >
>
Re: [DISCUSS] v0.12.2 release to allow K8s 1.22 and K8s 1.23 deployments
Posted by Weiwei Yang <ww...@apache.org>.
Apart from the issues that have been fixed.
Can we also make sure
- Update e2e test matrix to include 1.22
- Update the user doc to include guidelines of how to do upgrade
- Update and publish the new helm charts in the helm chart repo
can we have an umbrella JIRA to track all the remaining issues for 1.22?
People can help out some of unfinished tasks.
On Tue, Jan 11, 2022 at 8:44 PM Weiwei Yang <ww...@apache.org> wrote:
> Fantastic, thank you, Wilfred, Craig for getting this solved!
> +1 of having a 1.22 release, to unblock people who use 1.22+ K8s versions.
>
>
> On Tue, Jan 11, 2022 at 8:40 PM Chaoran Yu <yu...@gmail.com>
> wrote:
>
>> +1 because it unblocks some users.
>>
>> On Tue, Jan 11, 2022 at 4:35 PM Sunil Govindan <su...@apache.org> wrote:
>>
>> > I think this will help our customers who are stuck with K8s 1.22 issue
>> > before 1.0 is out.
>> >
>> > +1 to the proposal
>> >
>> > Thanks
>> > Sunil
>> >
>> > On Tue, Jan 11, 2022 at 4:11 PM Wilfred Spiegelenburg <
>> wilfreds@apache.org
>> > >
>> > wrote:
>> >
>> > > Over the last weeks Craig and I have been working on getting the
>> > > admission controller deployment updated. These changes were committed
>> > > yesterday as YUNIKORN-941. The main goal was to move away from old K8s
>> > > objects and API calls and remove the scripts for certificate creation.
>> > >
>> > > With the changes committed deployments and e2e tests against K8s1.22
>> > > and K8s 1.23 are no longer failing.
>> > > I would like to propose that we release v0.12.2 with just the changes
>> > > for the admission controller to allow deployments on the latest
>> > > versions of K8s. Since Craig is the person that has been driving this
>> > > code change I would like to propose him as the release manager.
>> > >
>> > > This is the list of changes related to YUNIKORN-941. It includes a
>> > > number of other jiras as they are all fixed by the new deployment:
>> > > * YUNIKORN-995
>> > > * YUNIKORN-938
>> > > * YUNIKORN-947
>> > > * YUNIKORN-625
>> > > * YUNIKORN-726
>> > > It has one jira it dependents on: YUNIKORN-928
>> > >
>> > > Wilfred
>> > >
>> > > ---------------------------------------------------------------------
>> > > To unsubscribe, e-mail: dev-unsubscribe@yunikorn.apache.org
>> > > For additional commands, e-mail: dev-help@yunikorn.apache.org
>> > >
>> > >
>> >
>>
>
Re: [DISCUSS] v0.12.2 release to allow K8s 1.22 and K8s 1.23 deployments
Posted by Weiwei Yang <ww...@apache.org>.
Fantastic, thank you, Wilfred, Craig for getting this solved!
+1 of having a 1.22 release, to unblock people who use 1.22+ K8s versions.
On Tue, Jan 11, 2022 at 8:40 PM Chaoran Yu <yu...@gmail.com> wrote:
> +1 because it unblocks some users.
>
> On Tue, Jan 11, 2022 at 4:35 PM Sunil Govindan <su...@apache.org> wrote:
>
> > I think this will help our customers who are stuck with K8s 1.22 issue
> > before 1.0 is out.
> >
> > +1 to the proposal
> >
> > Thanks
> > Sunil
> >
> > On Tue, Jan 11, 2022 at 4:11 PM Wilfred Spiegelenburg <
> wilfreds@apache.org
> > >
> > wrote:
> >
> > > Over the last weeks Craig and I have been working on getting the
> > > admission controller deployment updated. These changes were committed
> > > yesterday as YUNIKORN-941. The main goal was to move away from old K8s
> > > objects and API calls and remove the scripts for certificate creation.
> > >
> > > With the changes committed deployments and e2e tests against K8s1.22
> > > and K8s 1.23 are no longer failing.
> > > I would like to propose that we release v0.12.2 with just the changes
> > > for the admission controller to allow deployments on the latest
> > > versions of K8s. Since Craig is the person that has been driving this
> > > code change I would like to propose him as the release manager.
> > >
> > > This is the list of changes related to YUNIKORN-941. It includes a
> > > number of other jiras as they are all fixed by the new deployment:
> > > * YUNIKORN-995
> > > * YUNIKORN-938
> > > * YUNIKORN-947
> > > * YUNIKORN-625
> > > * YUNIKORN-726
> > > It has one jira it dependents on: YUNIKORN-928
> > >
> > > Wilfred
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@yunikorn.apache.org
> > > For additional commands, e-mail: dev-help@yunikorn.apache.org
> > >
> > >
> >
>
Re: [DISCUSS] v0.12.2 release to allow K8s 1.22 and K8s 1.23 deployments
Posted by Chaoran Yu <yu...@gmail.com>.
+1 because it unblocks some users.
On Tue, Jan 11, 2022 at 4:35 PM Sunil Govindan <su...@apache.org> wrote:
> I think this will help our customers who are stuck with K8s 1.22 issue
> before 1.0 is out.
>
> +1 to the proposal
>
> Thanks
> Sunil
>
> On Tue, Jan 11, 2022 at 4:11 PM Wilfred Spiegelenburg <wilfreds@apache.org
> >
> wrote:
>
> > Over the last weeks Craig and I have been working on getting the
> > admission controller deployment updated. These changes were committed
> > yesterday as YUNIKORN-941. The main goal was to move away from old K8s
> > objects and API calls and remove the scripts for certificate creation.
> >
> > With the changes committed deployments and e2e tests against K8s1.22
> > and K8s 1.23 are no longer failing.
> > I would like to propose that we release v0.12.2 with just the changes
> > for the admission controller to allow deployments on the latest
> > versions of K8s. Since Craig is the person that has been driving this
> > code change I would like to propose him as the release manager.
> >
> > This is the list of changes related to YUNIKORN-941. It includes a
> > number of other jiras as they are all fixed by the new deployment:
> > * YUNIKORN-995
> > * YUNIKORN-938
> > * YUNIKORN-947
> > * YUNIKORN-625
> > * YUNIKORN-726
> > It has one jira it dependents on: YUNIKORN-928
> >
> > Wilfred
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@yunikorn.apache.org
> > For additional commands, e-mail: dev-help@yunikorn.apache.org
> >
> >
>
Re: [DISCUSS] v0.12.2 release to allow K8s 1.22 and K8s 1.23 deployments
Posted by Sunil Govindan <su...@apache.org>.
I think this will help our customers who are stuck with K8s 1.22 issue
before 1.0 is out.
+1 to the proposal
Thanks
Sunil
On Tue, Jan 11, 2022 at 4:11 PM Wilfred Spiegelenburg <wi...@apache.org>
wrote:
> Over the last weeks Craig and I have been working on getting the
> admission controller deployment updated. These changes were committed
> yesterday as YUNIKORN-941. The main goal was to move away from old K8s
> objects and API calls and remove the scripts for certificate creation.
>
> With the changes committed deployments and e2e tests against K8s1.22
> and K8s 1.23 are no longer failing.
> I would like to propose that we release v0.12.2 with just the changes
> for the admission controller to allow deployments on the latest
> versions of K8s. Since Craig is the person that has been driving this
> code change I would like to propose him as the release manager.
>
> This is the list of changes related to YUNIKORN-941. It includes a
> number of other jiras as they are all fixed by the new deployment:
> * YUNIKORN-995
> * YUNIKORN-938
> * YUNIKORN-947
> * YUNIKORN-625
> * YUNIKORN-726
> It has one jira it dependents on: YUNIKORN-928
>
> Wilfred
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@yunikorn.apache.org
> For additional commands, e-mail: dev-help@yunikorn.apache.org
>
>