Falcon 3.0 Roadmap
- Review/Merge the ASGI implementation - PR #1573
- Review/Merge native form parsing (WSGI only) - PR #1549
- Fix doc formatting issue (see also comment on PR #1566)
- Get tests to pass on Windows
- Add windows gate to Travis CI
- Tweak ASGI and form interfaces (if needed) based on alpha tester feedback
- Finish ASGI Docs (including Changelog snippets)
- Finish multipart form parsing docs
- Add async support for multipart form parsing
- Review/Merge PR backlog
- ASGI WebSocket impl. + docs - PR #1741
- Tweak ASGI and form interfaces (if needed) based on alpha tester feedback
- Review/Merge PR backlog
- ASGI tutorial
- Implement and merge remaining items from the 3.0 milestone in the issue tracker (delay low-priority items to 3.1/4.0 as needed)
- Semi-final performance testing and optimization
- Semi-final changelog updates
- Render changelog news fragments (so far)
- Bug fixes
- Final performance testing and optimization
- Final changelog updates
- Review/Merge PR backlog (or delay community PRs to 3.x/4.x as needed)
- Critical bug fixes and non-invasive documentation improvements ONLY
- Render changelog news fragments to changelog and remove fragment files
- Finalize "Contributors to this Release" section in the changelog
- Add release summary to changelog
Are websockets still targeted for 3.0, or are they likely to be moved back to 3.1? I've been plugging away at a personal project using the 3.0 alpha that I knew was going to need websocket support down the road, but it turns out I'll need it earlier in the process than I thought. I'm trying to figure out if I should postpone work on this section of the app on the assumption that websockets will be included in 3.0 with some patience, or if I should evaluate lesser frameworks.
Thanks for your work on 3.0! I'm really enjoying the ASGI support so far.