3.1 branch divergence and future release plans #2212
Replies: 5 comments
-
As an aside, I'm working around this right now with my fork, which is just 3.1.3 with edd9352 cherry picked in, and works great. https://github.com/JEFuller/falcon/tree/3.1.3-multiple_segments I thought about making a PR, but there isn't a sensible target for it (since |
Beta Was this translation helpful? Give feedback.
-
Hi,
the main branch is the development version of the next version of falcon
Yes, that was a new feature that's planned for v4. Things are not progressing as fast as we would like toward a new release though. |
Beta Was this translation helpful? Give feedback.
-
Yes @davetapley , we're just stretched on resources (as many open source projects... 👿)... The plan was to follow up 3.1 directly with 4.0. However, new CPython versions came out, requiring our immediate attention (IIRC the framework was completely broken under 3.11, 3.12 was not that critical, but we lacked binary wheels). So we just added patches atop the stable version (3.1). The next version will finally be 4.0. We can maybe push some issues in favour of a timely release, but some we really need to address. The roadmap for the 4.x series is outlined here: #2073. |
Beta Was this translation helpful? Give feedback.
-
And thanks for your kind words about the project @davetapley! |
Beta Was this translation helpful? Give feedback.
-
Thanks for your patience @davetapley, I just wanted to let you known that the wait was over, and the divergence is no more. Falcon 4.0 was released last Friday. 😅 |
Beta Was this translation helpful? Give feedback.
-
I just wanted to call out that the 3.1.x branches diverged way back on Fri Mar 25 2022 at 33c8450, and so all the features since then aren't available 😑
For me that's awkward because I really need:
But it was merged June 1 2022 at edd9352, missing the cutoff 😞
Is this intentional, if so is there a release plan?
Thanks for a great project 🙏🏻
Beta Was this translation helpful? Give feedback.
All reactions