You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@spark.apache.org by GitBox <gi...@apache.org> on 2021/04/09 15:42:15 UTC

[GitHub] [spark-website] cloud-fan opened a new pull request #331: Fix 3.2 release window

cloud-fan opened a new pull request #331:
URL: https://github.com/apache/spark-website/pull/331


   The 3.1 was released on Mar 2, so the target release day for 3.2 should be September 2 according to the 6 months release cycle.
   
   Then the RC stage should start one month before the target release day, which is August.


-- 
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:
users@infra.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@spark.apache.org
For additional commands, e-mail: commits-help@spark.apache.org


[GitHub] [spark-website] cloud-fan commented on pull request #331: Fix 3.2 release window

Posted by GitBox <gi...@apache.org>.
cloud-fan commented on pull request #331:
URL: https://github.com/apache/spark-website/pull/331#issuecomment-817508649


   I've added a reply in the 3.2 thread in the dev list. I'll merge this PR after a few days if there is no objection.


-- 
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:
users@infra.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@spark.apache.org
For additional commands, e-mail: commits-help@spark.apache.org


[GitHub] [spark-website] dongjoon-hyun commented on pull request #331: Fix 3.2 release window

Posted by GitBox <gi...@apache.org>.
dongjoon-hyun commented on pull request #331:
URL: https://github.com/apache/spark-website/pull/331#issuecomment-816800210


   It would be greatly helpful if you share it to the dev mailing list to finalize this timeline.


-- 
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:
users@infra.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@spark.apache.org
For additional commands, e-mail: commits-help@spark.apache.org


[GitHub] [spark-website] HyukjinKwon closed pull request #331: Fix 3.2 release window

Posted by GitBox <gi...@apache.org>.
HyukjinKwon closed pull request #331:
URL: https://github.com/apache/spark-website/pull/331


   


-- 
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:
users@infra.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@spark.apache.org
For additional commands, e-mail: commits-help@spark.apache.org


[GitHub] [spark-website] cloud-fan commented on pull request #331: Fix 3.2 release window

Posted by GitBox <gi...@apache.org>.
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:
users@infra.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@spark.apache.org
For additional commands, e-mail: commits-help@spark.apache.org


[GitHub] [spark-website] dongjoon-hyun commented on pull request #331: Fix 3.2 release window

Posted by GitBox <gi...@apache.org>.
dongjoon-hyun commented on pull request #331:
URL: https://github.com/apache/spark-website/pull/331#issuecomment-816784796


   Whatever we choose, just FYI, cc @dbtsai , @holdenk , @viirya , @sunchao, @attilapiros 


-- 
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:
users@infra.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@spark.apache.org
For additional commands, e-mail: commits-help@spark.apache.org


[GitHub] [spark-website] cloud-fan commented on pull request #331: Fix 3.2 release window

Posted by GitBox <gi...@apache.org>.
cloud-fan commented on pull request #331:
URL: https://github.com/apache/spark-website/pull/331#issuecomment-816774660


   cc @dongjoon-hyun @gatorsmile @srowen 


-- 
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:
users@infra.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@spark.apache.org
For additional commands, e-mail: commits-help@spark.apache.org


[GitHub] [spark-website] dongjoon-hyun commented on pull request #331: Fix 3.2 release window

Posted by GitBox <gi...@apache.org>.
dongjoon-hyun commented on pull request #331:
URL: https://github.com/apache/spark-website/pull/331#issuecomment-816783741


   Shall we discuss on the dev emailing list about this revision? As you know, I'll not be against on the dev mailing list decision. :)


-- 
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:
users@infra.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@spark.apache.org
For additional commands, e-mail: commits-help@spark.apache.org