potiuk commented on PR #28651: URL: https://github.com/apache/airflow/pull/28651#issuecomment-1368133730
> I'm not sure it matters, I think it'd make more sense to have "meaningful" releases of any given provider. > I think it is ultimately up to the release manager though. Just one comment here as well. I think it's also the matter of an agreement and general approach between the release managers when there is more than one. Because it is not only the decision impacting this single release, but it ALSO (and this is more important) impacts future releases of the same provider - i.e.. this change will have to be dealt with eventually. It could be done in the current release (by the current release manager) or in the future release (by the future one). I think any changes like that should be dealt with as soon as possible (for the reasons explained above - the more time passes, the more "accumulation" of potential problems occur, the less "blurry" the memory about the changes introduced is and the less likely the contributor of a given change will help. The bad thing is - if you think about future self or future other relase manager is that the more we dely such release, the more difficult it might get to handle and you can either "face it" now or let you (or someone else) "face it" later. There is another angle of it. When you say "we released all there is to relase" as a release manager you say "I've completed the job fully and the next release manager has to care only about future changes". Vs. "ok I let the future release manager (which might be you) handle that in the future.". -- 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]
