Great! - Thanks Niko! We will look into releasing the Amazon ad-hoc provider before Airflow 3.2 is out.
J. On Tue, Mar 31, 2026 at 4:37 AM Oliveira, Niko <[email protected]> wrote: > It is passed Sunday, so this has technically passed, but the Redshift team > has completed the changes and pushed a release that is compatible with > Python 3.14. > > Release notes: > https://github.com/aws/amazon-redshift-python-driver/commit/f034099eea1620e499641db071f81ec1866f698c > > The release: https://pypi.org/project/redshift-connector/2.1.13/#history > > So for what it is worth I vote -1 to this lazy consensus now :) > > Cheers, > Niko > ________________________________ > From: Jarek Potiuk <[email protected]> > Sent: Thursday, March 26, 2026 5:05 AM > To: [email protected] <[email protected]> > Subject: RE: [EXT] [LAZY CONSENSUS] Suspending Amazon provider for Python > 3.14 (temporary) > > CAUTION: This email originated from outside of the organization. Do not > click links or open attachments unless you can confirm the sender and know > the content is safe. > > > > AVERTISSEMENT: Ce courrier électronique provient d’un expéditeur externe. > Ne cliquez sur aucun lien et n’ouvrez aucune pièce jointe si vous ne pouvez > pas confirmer l’identité de l’expéditeur et si vous n’êtes pas certain que > le contenu ne présente aucun risque. > > > > Sunday of course. Sorry been copying it on the phone and somehow I lost a > day this week and thought it's Wednesday :) > > On Thu, Mar 26, 2026, 12:52 Jarek Potiuk <[email protected]> wrote: > > > Hello here, > > > > I would like to call for a lazy consensus on suspensding Amazon provider > > (despite it being by default included in the reference images) for Python > > 3.14 - which Ilya relentlessly worked on. > > > > > > Ths is the last blocker from releasing the image. Including snowflake > > releasing 3.14 provider literally today. > > > > Our separated Governance process did not include the part about > suspension > > (as de-facto it is not a separate lifecycle stage - provider can be > > suspended in any lifecycle stage). But I added a paragraph describing it > > and stating that steward is responsible for solving problems leading to > > suspension and bringing it back (we already had that rule before adding > > stewards - the party responsible was simply unnamed). > > > > PR for the governance process here: > > > > https://github.com/apache/airflow/pull/64252 > > > > The consensus will run till Satirday, 29 March, 1 pm CET (72 hours from > > now). > > > > J. > > >
