potiuk commented on PR #40722:
URL: https://github.com/apache/airflow/pull/40722#issuecomment-2253017856

   > It won't get lost. Until 9th of August (RC1 for 2.10.0 planned this day) 
the v2-10-test branch will continue to be rebased on main. What is going to be 
merged till then is going to be 2.10.0 automatically. We are now in the "brief 
period" described in:
   > 
   > 
https://github.com/apache/airflow?tab=readme-ov-file#what-goes-into-the-next-release
   > 
   > > Most of the time in our release cycle, when the branch for next MINOR 
branch is not yet created, all PRs merged to main (unless they get reverted), 
will find their way to the next MINOR release. For example if the last release 
is 2.7.3 and v2-8-stable branch is not created yet, the next MINOR release is 
2.8.0 and all PRs merged to main will be released in 2.8.0. There is a brief 
period of time when we cut a new MINOR release branch and prepare the alpha, 
beta, RC candidates for the 2.NEXT_MINOR.0 version where PRs merged to main 
will only be released in the following MINOR release.
   
   Actually that's the quite wrong :) It's a brief-period before the brief 
period when next MINOR branch already exist but RC is not cut yet


-- 
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: commits-unsubscr...@airflow.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Reply via email to