Hi Weiwei, Thanks for bringing up this discussion.
That may depend on what "1.0" means, and what bumping a major version means. Usually a new major version (e.g. 0.x -> 1.x -> 2.x) contains some critical new features or breaking changes. One critical feature of the next release is integration with Spark K8S Operator, which feels can justify for a bump and catch more attention/adoption in the space. Anything else? Another consideration about bumping major versions relates to graduation. I've seen projects using a new major release as a graduation ceremony from the incubator (some also stick with minor releases). Curious - What's the plan for the graduation? Any blockers, or is it just a matter of time when YuniKorn community applies for it? Does using 1.0 indicate we are preparing for it? Thanks On Wed, Apr 21, 2021 at 10:19 AM Weiwei Yang <w...@apache.org> wrote: > Hi all > > In today's community meeting, we have started the discussion for the next > release. > About the release version, we have 2 candidates: *0.11* or *1.0*. Which one > should be our next release? > I would like to bring this up to more people's attention and hear more > thoughts from you. The project was started back in *Jan 2019*, becoming an > Apache incubator in *Jan 2020*, and now we see more and more adoption in > the community. Today, our major interface is stable (scheduler-interface), > major features such as hierarchy queue, app/node/queue sorting, placement > rule, resource fairness, resource reservation are all stable. IMO, we > should chase for the 1.0 release in the next few months. > Please help to vote for the version name in this google form: > https://forms.gle/ZhmrFvZpBdXnRmeh7, your opinion matters! > > Thanks > Weiwei >
