https://github.com/semver/semver/blob/master/semver.md.
Nothing says when you have to make breeding changes of course. But it's a sign to the users that something has broken. If you want to wait six months feel free. But I don't think that should be our policy. I the policy to be "we release under SemVer so can delete code that was deprecated under the previous major version". No time requirement. On 21 May 2022 19:12:32 BST, Jarek Potiuk <[email protected]> wrote: >> Will min Airflow version aside: we agreed we're going to follow SemVer, so I >> say we stick to that. X+1.0.0 (when ever we choose to release it) is when we >> remove the deprecated code. > >That's not entirely correct. Unfortunately semver.org is down now so I >cannot check my authoritative source :). But - from what I know, >SemVer does not really mandate removal of deprecations. > It says that (from memory) MAJOR version MAY contain breaking >changes, but it never (unless I am mistaken) states that you MUST make >braking changes for all deprecations.
