Replies: 3 comments
-
Hi @zhangchi1 Currently the releases are on an ad-hoc basis. For example, if we fix some bugs, we will cut a new version sooner. @denimalpaca Can tell us more about version alignment with the great_expectation python library |
Beta Was this translation helpful? Give feedback.
-
Going to pass the buck to @talagluck about version alignment with the |
Beta Was this translation helpful? Give feedback.
-
Hi @kaxil - there should generally not be any major issues with version alignment, since we have a lot of notice for more major breaking changes. For bugs and regressions, we are in the process of implementing more formal testing now, which will consist of cloning the Operator repo in our CI/CD and running the tests against the latest version of Great Expectations. |
Beta Was this translation helpful? Give feedback.
-
Hi @denimalpaca @kaxil, thanks again for approving the PR and maintaining this operator. We are actively spiking and trying to onboard great_expectations airflow operator into our DQ system. And we are happy to keep contributing to this fantastic library. We are wondering do we have any rules for the new version release? For example, how often do we release a new version/tag? How are we managing the version number aligned with the great_expectation python library?
Thanks,
Beta Was this translation helpful? Give feedback.
All reactions