What are the remaining requirements for a stable v3 release?

[kirby81]

Hi! First of all, thank you for all the work you’ve been putting into rnet — it’s been great to follow the progress of v3 so far.

I noticed that the project is currently at v3.0.0-rc20, and I was wondering what criteria or remaining milestones you consider necessary to move toward a stable v3 release.

Are there specific features, fixes, performance goals, or real-world testing requirements that still need to be completed before cutting a stable version? Any guidance or high-level roadmap would be very helpful for users who are considering adopting v3 in production or contributing to its finalization.

Thanks again for your work, and for taking the time to share your thoughts!

[0x676e67]

The API has stabilized and we don't expect any more big updates. Right now, we’re waiting for an upstream refactor of the connection pool to optimize granular connection management. A stable release will follow shortly after.

[0x676e67]

https://github.com/0x676e67/wreq-python/releases/tag/v0.10.0