FYI, I created YUNIKORN-908 <https://issues.apache.org/jira/browse/YUNIKORN-908> for the work to support k8s 1.21, tentatively targeted for v1.0.0 release. Also I saw that Kinga has this PR https://github.com/apache/incubator-yunikorn-k8shim/pull/271 <https://github.com/apache/incubator-yunikorn-k8shim/pull/271> that’s needed for dropping support for 1.18.
YUNIKORN-891 <https://issues.apache.org/jira/browse/YUNIKORN-891> is the umbrella JIRA for the upcoming release work that I’ll take on in about a month. > On Oct 22, 2021, at 17:10, Weiwei Yang <[email protected]> wrote: > > Hi Chaoran/Sunil > > I don't think we have the wiki sort of thing. > For in-progress releases, we can use the JIRA tag to track, like Chaoran > pointed out: > https://issues.apache.org/jira/projects/YUNIKORN/versions/12350288. > For released versions, we publish them to our website: > https://yunikorn.apache.org/community/download/. > > On Fri, Oct 22, 2021 at 4:02 PM Chaoran Yu <[email protected]> wrote: > >> I saw that we already have a JIRA filter for 1.0 >> <https://issues.apache.org/jira/projects/YUNIKORN/versions/12350288>. >> Sunil, where is the release Wiki supposed to be? I'll create one for 1.0 >> >> On Fri, Oct 22, 2021 at 12:16 PM Sunil Govindan <[email protected]> wrote: >> >>> +1 >>> >>> Yes. Lets start the planning. >>> >>> Chaoran, @Chenya, and Wilfred, >>> Could we create a release wiki and place this timeline with a Jira >> filter? >>> I think it will be a good start for this entire process. >>> >>> Thanks >>> Sunil >>> >>> >>> On Fri, Oct 22, 2021 at 11:54 AM Chenya Zhang < >> [email protected] >>>> >>> wrote: >>> >>>> Great to see that we are going to have a new 1.0.0 release! >>>> >>>> I could help Chaoran and shadow this release. Would be interested in >>>> becoming our next release manager but happy to take a fight when it >>> comes. >>>> :D >>>> >>>> Will follow up on this thread for v1.0.0. >>>> >>>> Best, >>>> Chenya >>>> >>>> On Fri, Oct 22, 2021 at 11:37 AM Weiwei Yang <[email protected]> wrote: >>>> >>>>> Hi Craig >>>>> >>>>> I think officially supporting 3 major K8s versions should be enough, >>> but >>>> we >>>>> need to update to 1.19, 1.20, and 1.21. >>>>> 1.18 is EoL per https://endoflife.date/kubernetes . If we continue >> our >>>>> release cadence, most likely we can move 1 major release at a time >> and >>>> that >>>>> aligns with the K8s releases. >>>>> >>>>> On Fri, Oct 22, 2021 at 9:29 AM Craig Condit <[email protected] >>> >>>>> wrote: >>>>> >>>>>> Looking forward to 1.0 release as well, and thanks Chaoran for >>>>>> volunteering to manage the release. >>>>>> >>>>>> Should we also update our supported version matrix to include 1.18, >>>> 1.19, >>>>>> 1.20, and 1.21? Updating the e2e test matrix should be a one-line >>>> change, >>>>>> and as part of the rebuild against 1.20, I verified that 1.21 is >>>>> functional. >>>>>> >>>>>> Craig >>>>>> >>>>>>> On Oct 22, 2021, at 2:15 AM, Weiwei Yang <[email protected]> >> wrote: >>>>>>> >>>>>>> Sounds great, thank you Chaoran! >>>>>>> >>>>>>> On Thu, Oct 21, 2021 at 11:51 PM Chaoran Yu < >>> [email protected] >>>>> >>>>>> wrote: >>>>>>> >>>>>>>> Hey guys, >>>>>>>> >>>>>>>> I volunteer to be the release manager this time, if nobody else >>> has >>>>>>>> volunteered already. >>>>>>>> >>>>>>>> The proposed timeline sounds right to be. It will allow for >> ample >>>> time >>>>>> for >>>>>>>> stabilization and verification. >>>>>>>> >>>>>>>> Chaoran >>>>>>>> >>>>>>>> >>>>>>>> On Thu, Oct 21, 2021 at 11:48 PM Weiwei Yang <[email protected]> >>>> wrote: >>>>>>>> >>>>>>>>> Hi Wilfred >>>>>>>>> >>>>>>>>> Thanks. Sounds good to me. >>>>>>>>> Does anyone want to be the release manager for 1.0? The apache >>> way >>>>>>>>> encourages more people to get involved in the release process. >>>>>>>>> >>>>>>>>> On Thu, Oct 21, 2021 at 10:45 PM Wilfred Spiegelenburg < >>>>>>>>> [email protected]> >>>>>>>>> wrote: >>>>>>>>> >>>>>>>>>> Hi, >>>>>>>>>> >>>>>>>>>> We have been making big steps since our last release. Some >> major >>>>>>>> changes >>>>>>>>>> have gone in and some are almost ready. The changes include: >>>>>>>>>> - rest API updates >>>>>>>>>> - new node storage and sorting >>>>>>>>>> - upgrade to a later K8s version as a build dependency >>>>>>>>>> - scheduler interface change >>>>>>>>>> >>>>>>>>>> Work is ongoing on generating a new set of performance >> figures. >>>> This >>>>>>>>>> includes documenting how to run our performance tests so we >> can >>>>> repeat >>>>>>>>> them >>>>>>>>>> when we want to. >>>>>>>>>> >>>>>>>>>> Based on all this work I would like to propose a 1.0.0 release >>> to >>>> be >>>>>>>>> ready >>>>>>>>>> for a vote by the incubator PMC by the start of December 2021. >>>> This >>>>>>>> will >>>>>>>>>> give us some time to get the last fixes in and stabilise the >>>>> release. >>>>>> A >>>>>>>>>> release for us is still a multistep project: >>>>>>>>>> - fork and prepare the release >>>>>>>>>> - vote in the project >>>>>>>>>> - vote in the incubator PMC >>>>>>>>>> Looking back at the last release cycles that means we should >>> have >>>> a >>>>>>>> build >>>>>>>>>> ready for voting by 22 November on the dev list. Which would >>> mean >>>>> that >>>>>>>> we >>>>>>>>>> fork the release at the latest in the second week of November. >>>>>>>>>> >>>>>>>>>> Please let me know if the timeline is too ambitious or not >>>> ambitious >>>>>>>>>> enough. >>>>>>>>>> >>>>>>>>>> Wilfred >>>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>> >>>>>> >>>>>> >> --------------------------------------------------------------------- >>>>>> To unsubscribe, e-mail: [email protected] >>>>>> For additional commands, e-mail: [email protected] >>>>>> >>>>>> >>>>> >>>> >>> >>
