bugraoz93 commented on PR #57714: URL: https://github.com/apache/airflow/pull/57714#issuecomment-3487206902
> @bugraoz93 I think we need to stop back porting airflowctl changes to the Airflow core release branches. If some part of the process needs this, we need to change that process. I was planning to do it after the first release due to integration test limitations. Leveraging what we have automated backports etc made it easy to use the v3-1-test branch. I assumed it should be fine since the released parts are not even running these code pieces. I wasn't only sure about branch, commit, etc limitations or things to consider which I opened a discussion in Slack in the release channel. I was planning to open as a dev discussion but thought this was a technical detail and we could decide with knowledgeable people. I am not saying everyone should catch the chat or so but just to get an idea or speak out on this backporting case to see if there is big blockers to use it for the first round. I haven't heard hard no, I moved with the backporting option. I already planned this change for sure. As an initial plan, we should definitely release airflowctl from main, that is not questionable Is it impacting anything in Airflow Core releases? I can speed up the plan if it is causing too much trouble. If we can live with this until the first release, there will be one or two more PRs not more for 0.1.0. This would be very helpful for the first release -- 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]
