Thank you so much for volunteering and revising 2026 release plan, Hyukjin, Huaxin, Jungtaek.
I also agree that new plan (considering 4.3.0 in 2026 also) sounds better because it gives us more deliverable in 2026 as a part of smooth transition to Spark 5.0 in 2027. Thank you, Dongjoon Hyun. On 2026/01/20 02:22:30 Jungtaek Lim wrote: > It might be reasonable to share the load if it's breakable. Though there is > an existing issue of time zone difference and it might make the overall > process unnecessarily complicated. I'd leave her to decide what is the > pragmatic approach for her. > > > On Tue, Jan 20, 2026 at 8:39 AM Hyukjin Kwon <[email protected]> wrote: > > > I am fine either way. Maybe Jungteak could create RCs, and Huaxin could do > > the final release + mentor him with working togehter. That might be > > realistic but I will leave it up to you guys. > > > > Could either of you create a PR to make the change of the release ETA > > please?: > > > > May 1th 2026 Code freeze. Release branch cut. > > Mid May 2026 QA period. Focus on bug fixes, tests, stability and docs. > > Generally, no new features merged. > > Late May 2026 Release candidates (RC), voting, etc. until final release > > passes > > > > On Mon, 19 Jan 2026 at 11:59, huaxin gao <[email protected]> wrote: > > > >> Thanks, Jungtaek. I’d prefer to lead 4.2 as RM since it fits my > >> availability better than 4.3. I am also happy to pair with a shadow/co-RM > >> so we broaden RM experience and share the workload. > >> > >> Huaxin > >> > >> On Sun, Jan 18, 2026 at 6:13 PM Jungtaek Lim < > >> [email protected]> wrote: > >> > >>> Thanks Huaxin for volunteering. I appreciate your willingness. > >>> > >>> I can also help volunteering to be a release manager for 4.2 - IMHO it'd > >>> be probably good to give committers a shot to gain the experience. But I > >>> respect the willingness and I can also wait for the 4.3 release manager or > >>> probably bugfix one as well if you mind. > >>> > >>> On Mon, Jan 19, 2026 at 10:59 AM huaxin gao <[email protected]> > >>> wrote: > >>> > >>>> I volunteer to be 4.2 release manager. > >>>> > >>>> Huaxin > >>>> > >>>> On Sun, Jan 18, 2026 at 5:37 PM Hyukjin Kwon <[email protected]> > >>>> wrote: > >>>> > >>>>> Just a quick headups. I was thinking that it might start this a bit > >>>>> earlier to match with quarterly cadence so that, e.g., we can start 4.3 > >>>>> Seq > >>>>> or Oct, and 4.4 Dec or Jan. Could we tentatively make it around 2 months > >>>>> earlier? e.g., > >>>>> > >>>>> May 1th 2026 Code freeze. Release branch cut. > >>>>> Mid May 2026 QA period. Focus on bug fixes, tests, stability and docs. > >>>>> Generally, no new features merged. > >>>>> Late May 2026 Release candidates (RC), voting, etc. until final > >>>>> release passes > >>>>> > >>>>> Also, I would like to decide on a release manager too because I would > >>>>> need to work closely with the release manager to prepare the future > >>>>> release > >>>>> cadence (e.g., fixing the docs and branches). > >>>>> > >>>>> Would there be any volunteer for 4.2 release manager? > >>>>> > >>>>> > >>>>> On Thu, 15 Jan 2026 at 08:49, Dongjoon Hyun <[email protected]> > >>>>> wrote: > >>>>> > >>>>>> Thank you, Kent, Yang, and Wenchen. > >>>>>> > >>>>>> - The PR is merged. > >>>>>> - Apache Spark Versioning Policy page is updated with the schedule. > >>>>>> - SPARK-54137 is updated with the schedule. > >>>>>> > >>>>>> Dongjoon. > >>>>>> > >>>>>> On 2026/01/13 04:52:47 Kent Yao wrote: > >>>>>> > +1 > >>>>>> > > >>>>>> > Kent > >>>>>> > > >>>>>> > Dongjoon Hyun <[email protected]> 于2026年1月13日周二 09:25写道： > >>>>>> > > >>>>>> > > Hi all, > >>>>>> > > > >>>>>> > > As recently agreed under "SPIP: Accelerating Apache Spark Release > >>>>>> > > Cadence", Apache Spark 4.2.0 will be the final release following > >>>>>> the > >>>>>> > > existing release cadence. However, the current Apache Spark > >>>>>> Versioning > >>>>>> > > Policy page has not yet been updated and still reflects only the > >>>>>> delivered > >>>>>> > > Spark 4.1 release window. > >>>>>> > > > >>>>>> > > https://spark.apache.org/versioning-policy.html > >>>>>> > > > >>>>>> > > I would therefore like to propose updating the Versioning Policy > >>>>>> page to > >>>>>> > > include the planned release window for Apache Spark 4.2.0, as > >>>>>> outlined in > >>>>>> > > the following pull request: > >>>>>> > > > >>>>>> > > https://github.com/apache/spark-website/pull/661 > >>>>>> > > > >>>>>> > > The proposed timeline for Apache Spark 4.2.0 is as follows: > >>>>>> > > > >>>>>> > > - July 15, 2026: Code freeze and release branch cut > >>>>>> > > - Late July 2026: QA period > >>>>>> > > - August 2026: Release candidates (RCs) > >>>>>> > > > >>>>>> > > For tracking the overall progress of Apache Spark 4.2.0, please > >>>>>> refer to > >>>>>> > > the umbrella JIRA and its associated subtasks. Ongoing or > >>>>>> upcoming JIRA > >>>>>> > > issues related to the 4.2.0 release can also be added there. > >>>>>> > > > >>>>>> > > https://issues.apache.org/jira/browse/SPARK-54137 > >>>>>> > > (SPARK-54137: Prepare Apache Spark 4.2.0) > >>>>>> > > > >>>>>> > > Feedback and comments would be very welcome. > >>>>>> > > > >>>>>> > > Thanks, > >>>>>> > > Dongjoon > >>>>>> > > > >>>>>> > > >>>>>> > >>>>>> --------------------------------------------------------------------- > >>>>>> To unsubscribe e-mail: [email protected] > >>>>>> > >>>>>> > --------------------------------------------------------------------- To unsubscribe e-mail: [email protected]
