This is an automated email from the ASF dual-hosted git repository.
srowen pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/spark-website.git
The following commit(s) were added to refs/heads/asf-site by this push:
new 020caa52dc Update branch-cut dates in the release cadence
020caa52dc is described below
commit 020caa52dc372dd9aa087b01c3d10b62fc5c83ab
Author: Hyukjin Kwon <[email protected]>
AuthorDate: Fri Feb 17 10:41:19 2023 -0600
Update branch-cut dates in the release cadence
This PR updates branch-cut dates as every January and July in the release
cadence.
See also https://lists.apache.org/thread/l6tprb580lrq1118c83kt9fst30jp8n3
Author: Hyukjin Kwon <[email protected]>
Closes #438 from HyukjinKwon/release-cadence.
---
site/versioning-policy.html | 4 ++--
versioning-policy.md | 4 ++--
2 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/site/versioning-policy.html b/site/versioning-policy.html
index e9e860615e..80e5121e36 100644
--- a/site/versioning-policy.html
+++ b/site/versioning-policy.html
@@ -246,8 +246,8 @@ available APIs.</p>
<h2>Release cadence</h2>
-<p>In general, feature (“minor”) releases occur about every 6
months. Hence, Spark 2.3.0 would
-generally be released about 6 months after 2.2.0. Maintenance releases happen
as needed
+<p>The branch is cut every January and July, so feature (“minor”)
releases occur about every 6 months in general.
+Hence, Spark 2.3.0 would generally be released about 6 months after 2.2.0.
Maintenance releases happen as needed
in between feature releases. Major releases do not happen according to a fixed
schedule.</p>
<h3>Spark 3.4 release window</h3>
diff --git a/versioning-policy.md b/versioning-policy.md
index c5fbe1196b..153085259f 100644
--- a/versioning-policy.md
+++ b/versioning-policy.md
@@ -99,8 +99,8 @@ In cases where there is a "Bad API", but where the cost of
removal is also high,
<h2>Release cadence</h2>
-In general, feature ("minor") releases occur about every 6 months. Hence,
Spark 2.3.0 would
-generally be released about 6 months after 2.2.0. Maintenance releases happen
as needed
+The branch is cut every January and July, so feature ("minor") releases occur
about every 6 months in general.
+Hence, Spark 2.3.0 would generally be released about 6 months after 2.2.0.
Maintenance releases happen as needed
in between feature releases. Major releases do not happen according to a fixed
schedule.
<h3>Spark 3.4 release window</h3>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
