Yea +1 to Liang-Chi's question as well. So, if we merge to master, will it only go to the next major release ? Whereas if we want to merge to branch-5.3 for eg - assuming that branch-5.2 is the current latest released version, we have to merge to branch-5.x and the next minor version for that branch will then include our change ? If we want to do this, this might require some CI changes on github actions than we do today ?
Thanks, Anish On Mon, Dec 8, 2025 at 5:04 PM L. C. Hsieh <[email protected]> wrote: > I see. > > In the "Code Merging Principle" section, > > For non-behavior changes, always merge to master and the latest .x > branch. This change will be released with the next minor release > > Is this .x branch meaning a branch of a major branch like branch-4.x? > > Also, looks like master and the latest .x branch basically have the > same codebase? > > On Mon, Dec 8, 2025 at 4:37 PM Hyukjin Kwon <[email protected]> wrote: > > > > I actually intentionally disabled the commenter access so the discussion > can happen here :-). Otherwise, we would end up with multiple places to > discuss this. > > > > On Tue, 9 Dec 2025 at 09:33, L. C. Hsieh <[email protected]> wrote: > >> > >> Can you open comment access to the google doc? > >> So it will be easier to ask questions directly on the SPIP doc. > >> > >> On Sun, Dec 7, 2025 at 1:53 PM Hyukjin Kwon <[email protected]> > wrote: > >> > > >> > Hi all, > >> > > >> > I would like to start a discussion on accelerating the Apache Spark > release cadence. Over the past four months, we have been running preview > releases, and the process has been smooth and effective. As mentioned in > the preview release discussion thread, I’d now like to extend this approach > to official releases. > >> > > >> > During this period, I also looked into how other large projects, such > as Kubernetes and Python, manage their release timelines. Based on that > research and our own recent experience, I’ve drafted a proposal for an > updated Apache Spark release plan. > >> > > >> > TL;DR: > >> > > >> > Introduce a predictable release schedule: annual major releases and > quarterly minor releases, so users can benefit from new features earlier. > >> > With a faster cadence for minor releases, we should take a more > conservative approach toward behavior changes in minor versions, while > still allowing new features and improvements. > >> > > >> > I’d love to hear your thoughts and feedback. > >> > > >> > More details can be found in SPIP: Accelerating Apache Spark Release > Cadence > >> > > >> > Thanks! > >> > >> --------------------------------------------------------------------- > >> To unsubscribe e-mail: [email protected] > >> > > --------------------------------------------------------------------- > To unsubscribe e-mail: [email protected] > >
