potiuk commented on issue #32928: URL: https://github.com/apache/airflow/issues/32928#issuecomment-1783797115
> Hi @potiuk and @ephraimbuddy, I see "Airflow 2.7.3" milestone added to this bug, I was under the impression that it is being fixed in next bugfix release. Is it not the case (sorry, I'm not aware about the milestone convention we follow here)? Marking something as `x.y.z` means that we think it's important enough to be targetted to be looked at when we prepare the release. If a fix is ready, and issue closed and the fix gets cherry-picked to the release branch, it finally lands in the release and release notes. But it's not guaranteed - and in this case we can move things to the follow-up release so that unsolved issues like this do not block the release - because maybe somoene will have some time to take a look at will focus on finding the problem. But since we have no idea for the reason yet, we can't fix it. It needs to be diagnosed deeply, hypotheses drawn and proven, fix implemented (and possibly tested by those who raised and observed it - usually we ask people who raise the issue to verify the hypothes we have - there are no "guarantees" such issues will be fixed - even if we think we found some reasons, it could be that it's note Since this is an open-source project - there are no guarantees that all such issue will be fixed, nor even deeply looked at. Everyone contributing here do it on voluntary basis (including maintainer, PMC members and release managers) - even if some of us (like me) got some funds to keep them doing it full time, we are not paid to solve all issues and we do not provide SLAs for bugs being fixed (especially that the software is delivered for free without any guarantees). And if they will have time and focus to fix things, they might (or might not) be able to fix those. Also anyone - including reporters and other contributors are welcome to attempt to diagnose and fix such issues. There are many issues that are solved by contributors here and it's actually one of the best way to give back to the community - by helping to diagnose and solve such issues or even pay someone to do so if they have a need to fix something to spend time on it - many of our contributors (including those fixing bugs) who are not even maintainers get paid for their contributions by somoene - their employees, companies who hire them etc. BTW. Indeed I think it would be nice idea to explain it somewhere in more detail. currently we just have very short description about this in the release process https://github.com/apache/airflow/blob/main/dev/README_RELEASE_AIRFLOW.md#close-the-milestone > Before closing the milestone on Github, make sure that all PR marked for it are either part of the release (was cherry picked) or postponed to the next release, then close the milestone. Create the next one if it hasn't been already (it probably has been). Update the new milestone in the https://github.com/apache/airflow/issues/10176 make sure to update the last updated timestamp as well. But likely we should be more clear what it means. I will propose a PR based on that answer. -- 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]
