bugraoz93 commented on PR #61822: URL: https://github.com/apache/airflow/pull/61822#issuecomment-3902565242
> > I may need to reschedule the release a week or two if I cannot make breaking changes compatible with the older version tomorrow :w( Or we can accept the breaking part since we are still in 0.1.x, which I would still be on the side of waiting a week or two to fix this, but on the other hand, features are waiting to be released. I will most prob fix it next week for sure > > Fine. > > We could - I guess utilise cadwyn for past release versions. Or - another option - we could always have `airflowctl X.Y.*` to only work with `airflow X.Y.*`. I think that might make sense, we woudl worry about compatibility far less. And we could couple the release process with airflow. > > I think that might be best pragmatic approach Thanks, Jarek! I thought about this last night on schema evolution, how to iterate, and what the process should be. I have implemented a solution entire day. Let me push it in a moment, only one thing left to handle, which command will be testable after which version, should not be complex. We discuss that solution too :D -- 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]
