cloud-fan commented on pull request #331:
URL: https://github.com/apache/spark-website/pull/331#issuecomment-816794424
I'm just following the existing document
```
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.
```
I don't see any place mentioning that the 6 months is counted after the
scheduled release date, or the branch cut date.
> The master branch has been prepared for Apache Spark 3.2 without being
blocked by Apache Spark 3.1.
Before 3.1 was released, I think it was still the QA period and part of the
community was not working on 3.2 development. I think we should have a full 6
months of community development for the new release.
Looking at the history, 2.2.0 was released 7 months after 2.1.0, 2.3.0 was
released 7 months after 2.2.0. We don't have the tradition to shorten the
release window of the next release if the previous release was delayed.
--
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.
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
