dongjoon-hyun commented on code in PR #688: URL: https://github.com/apache/spark-website/pull/688#discussion_r3284263484
########## site/versioning-policy.html: ########## @@ -303,16 +318,78 @@ <h3>Spark 4.2 release window</h3> </tbody> </table> +<h3>Illustrative transition: 2026 and 2027</h3> + +<p>The calendar below is an <strong>example</strong> to show how the community expects to bootstrap the faster cadence; +exact dates stay subject to the usual release-discussion and voting process.</p> + +<ul> + <li><strong>2026</strong>: Ship <strong>Apache Spark 4.2.0</strong> on the timeline above (the last <em>large</em> feature drop before the +transition). Treat <strong>4.2.x</strong> like other non-LTS branches (6 month maintenance window). After <strong>4.2.0</strong> Review Comment: This is different from what we discussed, @HyukjinKwon . We agreed that Apache Spark 4.2.x is beyond the policy because it started before SPIP. So, it has 18 months maintenance windows. > Treat <strong>4.2.x</strong> like other non-LTS branches (6 month maintenance window). Here, in the discussion, Spark 4.2.x is not supposed to be affected. > Absolutely agreed - this SPIP does not retroactively modify any existing commitments. > Spark 4.2.x must also follow the current policy because development has already progressed under that assumption. In the vote, SPIP targets only 4.3.0+ like this. > I would like to start a vote on the SPIP: Accelerating Apache Spark Release Cadence Target timing of this is 4.3.0 so 4.2.0 would be released as it was before. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
