potiuk commented on pull request #14487: URL: https://github.com/apache/airflow/pull/14487#issuecomment-787076166
> We've never done it before, but Python does have a convention for "this is a doc only changes" `.post1`. I imagine most of our tooling and process works break in such a version though we could potentially do it this way, but I think there is indeed no harm and almost no cost. Also there is a benefit for release manager. Next time packages are prepared you will not see those as "potential release candidates" that saves time next time when we prepare release. If only that is a benefit - I would do it anyway. Alternative to that is mark certain commits (like this one) as "not-worthy-to-be-released" and exclude those when preparing pacakges. Which we might want to do in the future. I think that should be part of bigger change which we might consider. Right now it is release manager who splits the changes to bugs/fixes/doc changes etc. But there was a discussion about using semantic commits or labels for those. We might want to resurrect that discussion (though I think it is perfectly manageable without it for the `providers` - I've done it couple of times and it is very little work. ---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: [email protected]
