HyukjinKwon commented on code in PR #688:
URL: https://github.com/apache/spark-website/pull/688#discussion_r3277098867


##########
site/versioning-policy.html:
##########
@@ -164,19 +164,32 @@ <h3>Spark versions</h3>
 <p>Each Spark release will be versioned: <code class="language-plaintext 
highlighter-rouge">[MAJOR].[FEATURE].[MAINTENANCE]</code></p>
 
 <ul>
-  <li><strong>MAJOR</strong>: All releases with the same major version number 
will have API compatibility.
-Major version numbers will remain stable over long periods of time. For 
instance, 1.X.Y may last 
-1 year or more.</li>
-  <li><strong>FEATURE</strong>: Feature releases will typically contain new 
features, improvements, and bug fixes. 
-Each feature release will have a merge window where new patches can be merged, 
a QA window when 
+  <li><strong>MAJOR</strong>: Major releases occur annually (every 12 months) 
as <strong>x.0.0</strong> releases. These releases may
+include <strong>breaking changes</strong>, third-party dependency upgrades, 
and other changes that are not
+compatible within the same major line. Within a major line, all 
<strong>x.y.z</strong> releases share API compatibility
+as described in the <strong>FEATURE</strong> and <strong>MAINTENANCE</strong> 
bullets below.</li>
+  <li><strong>FEATURE</strong>: Feature releases occur quarterly (every 3 
months) and contain new features, performance 
+improvements, API additions, and bug fixes. To ensure safe and predictable 
upgrades for downstream 

Review Comment:
   deprecation is fine but deletion is not. Let me explicitly mention removals



-- 
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]

Reply via email to