I hope to have the RC release for the November wave of providers todays (pending https://github.com/apache/airflow/pull/27613 approval) and unless someone has a problem with treating the min-version bump approach as problematic, I would proceed assuming tha the lazy consensus passed.
On Fri, Nov 11, 2022 at 2:28 PM Jarek Potiuk <[email protected]> wrote: > > Hey everyone, > > Following the explanation in > https://lists.apache.org/thread/xpngxsdxmk1vw2wk34py8sdsqfmjdw9g I would > like to call for a lazy consensus on the change proposed in the PR > https://github.com/apache/airflow/pull/27613 for the November wave of > providers. > > When we bumped "min airflow version" to 2.2+ we bumped all provider's MAJOR > versions signalling a breaking change. But I realized since this is not > really needed - because the change is not really breaking the user's > workflows (explanation in the linked discussion) > > I would like to call for a lazy consensus on that - in parallel to releasing > the providers - we can always cancel RCs if we release them so hopefully the > consensus will be reached before we actually release the providers. > > Of course, if there are objections and some reasons why this is not a good > approach, we can always revisit this, cancel the release candidates and re-do > the release with all MAJOR versions. > > J. >
