Lazy consensus has been reached. On Sun, Dec 22, 2024 at 7:10 PM Jarek Potiuk <ja...@potiuk.com> wrote:
> Correct. It's being worked on in main but we are not releasing it yet. > > BTW. I think we will need to release as pre-release version of it soon > though at the moment main version of airflow will stop supporting FAB 1.5, > because then it won't be possible to install airflow from main in > non-editable mode. > > On Sun, Dec 22, 2024 at 7:06 PM Elad Kalif <elad...@apache.org> wrote: > >> Just a small clarification. We are not voting on fab 2.0.0 >> >> Version 2.0.0 of fab will be released when the provider is ready >> (probably close to 3.0.0 alpha/beta) >> >> בתאריך יום א׳, 22 בדצמ׳ 2024, 19:56, מאת Jarek Potiuk <ja...@potiuk.com >> >: >> >>> Hello here, >>> >>> So we get to the point where we need to release a 1.5.2 version of FAB >>> provider while we are voting on 2.0.0. There is a good reason for that (I >>> can explain this in private). >>> >>> It's been possible even before, here I prepared a small PR >>> describing how this could be done: >>> >>> https://github.com/apache/airflow/pull/45159 >>> >>> I proposed that the branch created to release older providers should >>> follow naming similar to the one we keep for Airflow. >>> >>> providers-PROVIDER/vX-Y >>> >>> for example >>> >>> providers-fab/v1-5 >>> >>> No need to do test/stable in this case I think, because those will be >>> usually individual commits cherry-picked. >>> >>> I do not expect this to be controversial, so I am sending it as LAZY >>> CONSENSUS to speed things up, but of course, if someone has a problem, we >>> can discuss it and delay release of 1.5.2 - there is no big hurry with it. >>> >>> The lazy consensus will be reached on 25th of December (unless >>> someone objects that Xmas period is a bad time to run it and we can move it >>> till later). >>> >>> J. >>> >>>
