Following the discussion, agreement and lazy consensus, the last release of Qubole provider (with removal notification) was done on Nov 12.
The PR to remove Qubole is here https://github.com/apache/airflow/pull/35636 Once it is merged, Qubole Provider is no longer developed in the main repository. We will only potentially release new versions if we decide to fix a security issue reported to us, however since the service is not maintained any more, it's highly unlikely we will decide to do it. J. On Tue, Nov 7, 2023 at 1:56 PM Jarek Potiuk <ja...@potiuk.com> wrote: > The "technical" side of Qubole provider removal - according to the agreed > process is ready to review in https://github.com/apache/airflow/pull/35492 > > I updated our tooling to allow for optional "removed: true" flag to allow > for one last release to be made with warnings indicating that the provider > is not maintained any more (both in documentation an in PyPI package > description) - with link back to the removal process, this PR also prepares > Qubole for such last release and subsequent removal. We will test it for > Qubole and fix any issues we find during the process. > > Also I consolidated "technical" howtos on how to create, suspend, resume, > remove providers into a single MANAGING_PROVIDERS_LIFECYCLE document where > the technical aspects of all those are explained. > > J. > > On Mon, Nov 6, 2023 at 10:39 AM Jarek Potiuk <ja...@potiuk.com> wrote: > >> The lazy consensus has been reached. I will proceed with Qubole >> removal following the new process we have in place: >> https://github.com/apache/airflow/blob/main/PROVIDERS.rst#removing-community-providers >> >> On Mon, Oct 30, 2023 at 7:24 PM Jarek Potiuk <ja...@potiuk.com> wrote: >> >>> Hello everyone, >>> >>> As discussed in >>> https://lists.apache.org/thread/x4gt2h5hql7j04jj0v7v7kzzv1nkrzxy this >>> email clls for lazy consensus on removal of the Qubole provider. >>> >>> In short - we want to remove the Qubole provider as the company has been >>> acquired and the service and clients used to communicate with it are >>> abandoned by the maintainers. >>> >>> There is no need to respond to it, if there will be no objections, lazy >>> consensus will be reached on Monday, 6th November >>> >>> J. >>> >>
