Closed pankajkoti closed 6 months ago
The plan could be tentatively as below:
deprecation
branch and keep this branch in sync with mainPlease refer to https://github.com/astronomer/astronomer-providers/issues/1377
Also add the points in https://www.notion.so/astronomerio/Draft-Reduce-maintenance-effort-and-keep-backward-Compatibility-for-astronomer-providers-after-con-e16857c5ea814c71afe5009c674d0d67
The plan could be tentatively as below:
- Merge deprecation PRs to a
deprecation
branch and keep this branch in sync with main- Bump minimum versions of OSS providers to latest or the min version that contain deferrable support for all operators
- Have a single 2.0.0 release for all the deprecated providers
I just finished browsing through all the operators we have and finished this list https://github.com/astronomer/astronomer-providers/issues/1377#issuecomment-1864340191. I will update my future process on this list as well. Some of the operators have not yet contributed back. Most of the minor difference relates to checking before deferring. Regarding GKEStartPodOperatorAsync
, OSS airflow deprecates our original implementation and I think we should follow.
Current released version for astronomer-providers is 1.18.4 as on 1st Jan, 2023. We should create a v-1-18-stable branch from the current main.
Once the v-1-18-stable branch has been created, we can merge deprecation PRs to main.
The deprecation PRs should update minimum version of the depending upstream provider to the latest version of the provider or to at least a version that has the support for the deferrable param.
Release approaches for deprecation PRs:
The team prefers to go with approach a (release all in one go).
For, 1.19, increase the minimum Airflow version to 2.7 in setup.cfg. This is also the Airflow version in RT 10 and also Airflow OSS providers follow a similar fashion where they keep on bumping minimum Airflow version.
Prepare QA plan which includes testing scenarios like rollback of runtime image. Check customer usage dashboard for crucial operators and ensure good QA for these operators post deprecation.
Highlight 1.19 related notes in public documentation for astronomer-providers
Overall the approach looks fine to @abhishekbhakat . Abhishek is going to share the Notion doc with the CRE team and discuss with them the plan.
Some questions from Abhishek:
@pankajkoti Lets not share draft document to CRE. It should implement all the suggestions wrt planning, get reviewed by our team first, and post sign off we will share with CRE
okay @phanikumv
Notion docs is done, waiting for final reviews
waiting for another review of the Notion doc, suggestions till date have been incorporated. @phanikumv might be able to review by today EOD.
The review has received good comments and those are incorporated. Since the plan is ready and team discussions have taken place, I am closing this issue. We can continue following up conversation if any on the Notion doc.
cc: @phanikumv
We can add items to above action items list post our meeting.