My vote is for remove it as soon after the major ver of the provider is
released, or as soon as anyone remembers anyway :)
On Fri, May 20 2022 at 22:58:54 +0300, Elad Kalif <[email protected]>
wrote:
Providers follow semver just like airflow core.
If you upgrade to a major release it means that there are breaking
changes and you should read the release notes to know what they are.
Breaking changes can happen regardless of removing deprecated
features.
Google provider for example had several breaking changes releases
(2.0.0, 3.0.0 etc..) only in 7.0.0 we removed deprecated features.
בתאריך יום ו׳, 20 במאי 2022, 22:50, מאת Mateusz
Henc <[email protected]>:
Hello,
Right, nobody forces you to upgrade, but sometimes you wait for an
important bug fix/new feature that is coming in the new version and
you are surprised by the breaking change there.
Isn't the problem with deprecations more about their visibility? How
can users learn today that they use a deprecated feature? I think
it's only from logs.
But if dags are running fine, there is no need to check logs.
Shouldn't information about new deprecations be included in release
notes for the package?
Best regards,
Mateusz Henc
On Fri, May 20, 2022 at 5:39 PM Daniel Standish
<[email protected]> wrote:
> It means, in a 3 months period, a developer needs to [do lots of
things...]
When removal is released (say after a min of 3 months since
deprecation), as a user nothing forces you to upgrade to the latest
major /immediately/.
