srowen commented on pull request #33196: URL: https://github.com/apache/spark/pull/33196#issuecomment-873249068
Oh hm, right. Wouldn't it be sufficient to compare against 3.2.0? if 3.2.0 has no (non-excluded) breaking changes vs 3.0.0, and 3.3.0 is OK w.r.t. 3.2.0, that would be the same? It's highly unlikely that a previous exclusion would accidentally mask a new, unintended one -- say 3.2.0 'broke' something vs 3.1.0 but that was OK, but 3.3.0 has the same break vs 3.2.0 that we don't want. We'd miss it. Not likely to be a problem in practice, just wondering if I'm even thinking of it correctly. -- 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: reviews-unsubscr...@spark.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org For additional commands, e-mail: reviews-h...@spark.apache.org
