roadmap to v1.0.0?

[rursprung]

do you have a roadmap to releasing a v1.0.0? it would be cool if you could create the tickets for what you think is missing for v1.0.0 and assign them to a v1.0.0 milestone.

rationale: theoretically, one should only build on released software, so using 0.x pre-releases for production software isn't looked on too well. in the rust eco-system there are sadly a lot of crates which stay on 0.x for years but are heavily used. having a roadmap helps in understanding why a crate is not yet released as 1.x (or higher) and allows analysing the trade-offs (is it acceptable to use the crate in production even though these features are missing?).

furthermore, this would help with contributors: they know where work still needs to be done and they can offer their help focused on these topics.

[sfackler]

theoretically, one should only build on released software, so using 0.x pre-releases for production software isn't looked on too well.

Your theory does not appear to correspond to reality.

The API of r2d2 hasn't changed much in a while, so it's probably reasonable to make a 1.0 release. The only potential issue I'm aware of is that scheduled-thread-pool is exposed in the public API.

[rursprung]

i know that reality isn't always like this :(
but at least for larger corporations this rule often exists.

The only potential issue I'm aware of is that scheduled-thread-pool is exposed in the public API.

then maybe the same question can be posed for scheduled-thread-pool and the release of r2d2 1.0.0 depends on the release of scheduled-thread-pool 1.0.0?

[szagi3891]

Are there plans to support async/await ?