Description

In order to implement AIP-8 we need to separate implement mechanism of auto-discovery of the package capabilities. POC is implemented already, we need to implement it if we are going to separate out provider packages into separately installable packages This is also a prerequisite to implement #10507. We also want to implement it as a pre-requisite for #10014 if we want to test this mechanism before.

This also requires the implementation of the SEMVER automated versioning. The previous implementation with CALVER was much simpler to implement but we agreed that we want to release SEMVER versioning for the packages for Airflow 2.0. This part is still missing and needs to be implemented.

Use case / motivation

We voted on AIP-8 as it has multiple benefits over the monolith release - such as easier upgradability of providers independently from the core upgrades. It is definitely the preferred method for corporate customers who will have much less trouble installing just provider packages. It also allows for optimization of the build times #10507

Related Issues

#10014 #10507