shubham22 commented on PR #30727: URL: https://github.com/apache/airflow/pull/30727#issuecomment-1535659528
Adding in my 2 cents as well: > I have always assumed that the rationale for including only bugfixes in patch releases is because ideally patch releases should always make the thing more reliable, i.e. should fix things, and that things which aren't fixes and have some potential to cause breakage should be deferred. I completely agree with this idea. The patch releases should exclusively include _bug fixes_ and nothing more than that. Therefore, I do think it is the right decision to not ship this PR with v2.6.x. We should wait until v2.7 in oder to release this PR. > Maybe a good solution (@o-nikolas maybe that is a good idea ???) will be to PARK this one, leave it open in DRAFT stage and come back to it say, in 2 months when we get close to cutting the 2.7 branch That being said, I disagree with this approach. I am not saying this because I work directly with Niko, but I strongly believe that we should not ask contributors to wait for their PRs to be merged until we are ready for the next minor release. While I understand that this may not apply to all PRs, only selected ones, we currently have no policy defined, and setting this precedent could have severe repercussions. We cannot predict what cherry-picking changes might come and cannot hold other things for those future PRs. Contributors should not have to wait for two months and then come back and check every day to see if it is a good time for their PRs to be merged. In my opinion, we should proceed and merge this PR to main. If it results in issues while cherry-picking changes, we can ask the involved contributors for help in navigating those. Does it add more responsibility to the _Release managers_? Yes, it does. Nonetheless, I believe it is the lesser of the two evils because we should expect only a few changes to be cherry-picked in patch releases. Conversely, in the other scenario, the contributor will need to keep an eye on ALL the changes. -- 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]
