Thanks, Yicong, for volunteering to be the release manager! Given our goal of maintaining a predictable quarterly release cadence, I think we should stick to the original schedule as much as possible.
The November 16 branch cut sounds reasonable since we've already missed November 1, but I'd prefer to keep the original release target rather than delay it further. We can adjust if we encounter significant release blockers. Best, Xiao Yicong Huang via dev <[email protected]> 于2026年11月10日周二 08:15写道: > Hi all, > > I’m happy to serve as the release manager for the Apache Spark 4.4 release > line! I’d like to start a discussion on the release timeline for Apache > Spark 4.4.0. > > According to our previous release cadence, we should have cut the branch > on November 1. Since we’re already a bit behind schedule, I’d like to > propose the following timeline: > > - *Branch cut:* November 16, 2026 (Monday), giving the community about > a week to wrap up ongoing changes. > - *QA period:* After the branch cut, we’ll enter the QA period, > focusing on bug fixes, testing, stability, documentation, and release > blockers. In general, no new features should be merged into branch-4.4 > during this period. > - *Target release:* Mid-January 2027, to avoid the holiday season and > allow sufficient time for stabilization and release preparation. > > If you have any feature PRs you’d like to include in Apache Spark 4.4.0, > please try to get them merged before the branch cut. > > If there are no objections, I’ll proceed with updating the website and > sending a separate branch-cut announcement to the dev mailing list. > > Please let me know if you have any thoughts or concerns about the proposed > timeline. > > Best regards, > Yicong Huang >
