Weiwei, We are cleaning up the scheduler interface and moving things around for the API in the next release. We are also about to make major changes to the REST interface. Settling those and making sure we have that all correct is I think required before we do a 1.0 release, not as part of a 1.0 release.
We also still have a tangled build between the shim and core which we should solve before a 1.0 release. That untangling is for instance needed to, for instance, allow setting a log level dynamically and expose it via the REST interface. Same for the admission controller, we should move from scripts inside the scheduler image to code in the admission controller image. That is not even talking about some of the major changes that have been pushed to the background a bit around opentracing and or pluggability of policies. Both are major things which indicate I think we are not ready for 1.0 just yet. Wilfred On Thu, 22 Apr 2021 at 15:38, Weiwei Yang <w...@apache.org> wrote: > Hi Bowen > > Thanks for sharing your thoughts. > > There is no standard for what 1.0 release means. IMO, we can refer to > > https://en.wikipedia.org/wiki/Software_versioning#Version_1.0_as_a_milestone > . > Having 1.0 release indicates the software has the major features ready, the > public APIs are stabilized, and ready for general releases. This is what I > think where we are. 1.0 is a major milestone, that's the reason I started > the vote to gather opinions. > > Graduation from the incubator is a different discussion. We touched on that > topic in today's community call. Given the stage of the project, I think > we should start to prepare for graduation. I do not think the Apache > community has very clear criteria, but based on my experience, I think a > project must prove itself is sustainable, the community is mature, diverse, > follow the apache way to release versions, enough activities, etc. We can > ask for more info from the project mentors or other IPMC for guidance. The > plan in my mind is to gather enough info for graduation now, fix the > remaining gaps, have another release (hopefully 1.0), and then start the > process. > > On Wed, Apr 21, 2021 at 9:21 PM Bowen Li <b...@apache.org> wrote: > > > 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 > > > > > >
