potiuk commented on PR #58393: URL: https://github.com/apache/airflow/pull/58393#issuecomment-3542134754
> The more I think about it, the more questions/thoughts I have, but maybe they are all related to each other (I'll use common.compat as example): > 1. When this `use next version` comment is encountered, we use the value from provider.yml of specific provider, make a replacement and we remove this comment. Is there any mechanism that forces the release manager to first bump the versions in provider.yml Yes. Release process sequence > 2. What is the incentive for contributors to use this method over explicitly bumping this version in the provider.yml of the dependent provider (e.g. common.compat)? I for sure would like to be certain, that this change is made and not merely left as a comment that may or may not be implemented to avoid potential problem with releasing provider with broken features (see above). 2. They currently can't do it > 3. I guess it's related to the above, but does this mean that contributors have two ways of bumping this? 3. no. currently Contributors CAN'T and SHOULD NoT BUMP versions at all. Only RM can looks t the comment at the top of project.toml -- 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]
