potiuk commented on issue #18401: URL: https://github.com/apache/airflow/issues/18401#issuecomment-934483740
> I would recommend removing/yank 2.1.4 from the pypi or/and release a bugfix Just to explain some misconceptions @millin and maybe give you mor understanding of the process and to set the commo expectation and understanding (also for anyone reading it in the fufure). We only yank software if it has catastrophic bugs that prevent the software from running. This is not the case by any means. It's quite usual that there are bugs and they get fixed. 2.2 is doing exactly this (It has both new features and bugfixes). You might have misconception that we need extra bugfix release, but this is entirely not needed, as 2.2. will act as bugfix release as well. According to SemVer (which we are following): https://semver.org/ the minor release can contain both new features and bugfixes (not only new features) - see https://semver.org/#spec-item-7. And this is what 2.2 will have - it should be fully compatible with 2.1 (also according to SemVer). There is no way we can have 2.1.* releae faster than 2.2 since we are all busy making sure 2.2 is tested and released and contains all bug fixes. We will not throw everything down to fix that one fix of yours. Releasing new version of Airflow is a significant effort even if it contains very little changes, so we tend to do releases only when they are really needed. Unless there is a serious reason (basically critical security fix which we need to patch immediately), there will never be 2.1.5 - 2.2.0 will be the release where some bugs from 2.1.4. -- 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]
