Good point. We should document such things every time in READMEs - and in this case it should not only be READMEs but also appropriate steps in the release process IMHO.
https://github.com/apache/airflow/blob/main/dev/README_RELEASE_AIRFLOW.md Initially it could be pretty vague - we usually perfect and upgrade the docs as we do a release and make it better every time we do the release. We are following it Literally when releasing and placing it there is the only way to make 100% sure it will happen. J. On Wed, Dec 14, 2022 at 10:45 PM Elad Kalif <elad...@apache.org> wrote: > Pierre do we have this decision documented in the README so users are > aware of the policy ? (also I guess better to be written in the release > docs procedure) > > On Thu, Dec 8, 2022 at 7:50 PM Pierre Jeambrun <pierrejb...@gmail.com> > wrote: > >> Hello all, >> >> 72h hours have passed without opposition, therefore the proposal is >> accepted and we can start working on it :) >> >> Thanks you, >> Pierre >> >> Le lun. 5 déc. 2022 à 18:44, Pierre Jeambrun <pierrejb...@gmail.com> a >> écrit : >> >>> Hi all, >>> >>> *Context:* >>> Dag author should be able to use API clients to communicate with airflow >>> for everything that is not internal and covered by future AIP-44. The goal >>> of this proposal is to update the release process of our API clients so >>> they are compatible and up to date with the latest airflow API. >>> >>> *Proposal:* >>> Update the release process for the API clients: >>> - for each minor/major release of airflow, release new versions of api >>> clients accordingly. >>> - allow patching clients independently to fix specific issues >>> (documentation, generation issues etc.). >>> - when releasing a patch for airflow, *only *if this is relevant for >>> the clients, then also release clients (patch version). >>> >>> *Clients sources:* >>> - python https://github.com/apache/airflow-client-python >>> - go https://github.com/apache/airflow-client-go >>> >>> *Discussion thread:* [DISCUSSION] Release of API clients >>> <https://lists.apache.org/thread/phbrfg2q2lnrb9d3kfz3sxv6mzvtlwvp> >>> >>> As Jarek mentioned, this could eventually lead to other improvements, >>> for instance having the latest python API client pre-installed in our >>> reference airflow docker image. DAG authors should favor the public API for >>> communicating with airflow. >>> >>> After 72 hours without objection the proposal will be adopted. >>> >>> Thanks >>> Pierre >>> >>> >>> >>
