dongjoon-hyun commented on code in PR #688: URL: https://github.com/apache/spark-website/pull/688#discussion_r3239135381
########## site/versioning-policy.html: ########## @@ -305,14 +318,48 @@ <h3>Spark 4.2 release window</h3> <h2>Maintenance releases and EOL</h2> -<p>Feature release branches will, generally, be maintained with bug fix releases for a period of 18 months. -For example, branch 2.3.x is no longer considered maintained as of September 2019, 18 months after the release -of 2.3.0 in February 2018. No more 2.3.x releases should be expected after that point, even for bug fixes.</p> +<p>The following table summarizes the maintenance window for each release type:</p> + +<table> + <thead> + <tr> + <th>Release Type</th> + <th>Cadence</th> + <th>Maintenance Window</th> + </tr> + </thead> + <tbody> + <tr> + <td>Feature (x.y)</td> + <td>Every 3 months</td> + <td>6 months</td> + </tr> + <tr> + <td>LTS (final feature of a major)</td> Review Comment: Since this PR already mentions two exceptions like the following, it would be great to mention more specifically by giving examples like 5.3 or 6.3 in addition to `every x.3 release`. > As an exception from the normal versioning policy, version 3.5.x has an ... > For example, Spark 4.5 (the final 4.x feature release) would be maintained for 18 months from its release date. -- 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]
