potiuk commented on PR #27642: URL: https://github.com/apache/airflow/pull/27642#issuecomment-1314477843
> To be clear: Does this mean that no new API features/endpoints/params until the next minor airflow release? (and i guess then no client support until after that next minor release?)... i mean that makes sense per semver. It means that when we release 2.4.0 Airlfow -> we should also release 2.4.0 of API. Then, when we release 2.4.1 Airflow - we might NOT release 2.4.1, depending if there are changes in the API. Theorethically there shouldn't be any "substantial" changes - but there might be some documentation changes, or fixing bugs we have not noticed that will impact API specification. > How does it work for the time period between initial push to airflow and the new minor rev of airflow being released? I am not sure if I understand, but API 2.4.0 should contain all the 2.4 API's and they should not change in any of the 2.4.* versions. If there are any missing things in API 2.4.0 that were there in Airflow 2.4.0, they are really bugs that should be fixed in 2.4.* of the APIs. and there should never be any new features in API 2.4. -- 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]
