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]
