dongjoon-hyun commented on PR #59749: URL: https://github.com/apache/spark/pull/59749#issuecomment-6366461185
> Just to be on the same page, we generally do not block the release from non-regression correctness issue, do I understand correctly? Because I can even delay the release further with long standing correctness issues. (I'm looking into it now.) No, it's only for maintenance releases, @HeartSaVioR . For new releases, there is explicitly one pre-defined way. 1. File a correctness issue before a release manager starts a vote. 2. Set both `Blocker` level for `Priority` and `Target Version : 4.3.0` exactly. I didn't block other maintenance releases in this way. 3. Make a PR at the same time which a release manager can review and consume before he trigger the CIs. I'm following the standard procedure (1), (2), (3) in a legit way, @HeartSaVioR . BTW, I understand your frustration. However, I'm doing this QA activity because the release managers ask the community (including me) to test their RC artifacts. At the same time, I also have limited resources. So, as I told you, Today is the last day which I'm actively doing QA to help the community releases. From tomorrow, I'm switching back my focus to develop my new features instead of this kind of bug hunting, @HeartSaVioR . -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
