kaxil commented on PR #71725: URL: https://github.com/apache/airflow/pull/71725#issuecomment-6047747390
@AnicetNgrt the account offer helps with billing, thanks. By maintenance commitment I meant who does the work on this backend inside the Airflow repo after it merges. From then on Airflow committers release it, and users file issues against `apache-airflow-providers-common-ai`. If your API changes underneath it, our users' DAGs break and our maintainers get the bug report. So we need named people (GitHub handles, at least two, the same bar as provider stewards in [the stewardship model](https://github.com/apache/airflow/blob/main/providers/PROVIDER_GOVERNANCE.rst#stewardship-model)) who will: 1. Keep the backend in step with your API and `boat-sdk`. This PR already has an example: the old `ascii.dev/api/box/v1` base sunsets on 31 Oct 2026, and the PR for a change like that should come from your team before the date. 2. Triage and fix issues, and review PRs that touch the Boat backend, within a reasonable time. 3. Run the system test regularly against `main` and publish the results, like other vendors do on the [system test dashboards](https://airflow.apache.org/ecosystem/#airflow-provider-system-test-dashboards). The gifted account avoids the billing failure we hit on #71672; someone on your side still needs to run the test and act when it goes red. 4. Accept that if this lapses, the backend gets deprecated and removed under the [suspension and removal policy](https://github.com/apache/airflow/blob/main/providers/SUSPENDING_AND_REMOVING_PROVIDERS.rst). -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
