List view
This is very aspirational, not real roadmap here. If all goes well, v0.3 and v0.4 have focused on improving flexibility of respectively the version scheme and the dependency constraints scheme. After all this, there should be a time dedicated to improve error reporting and general usability of the crate. Well either this, or we need another step first dedicated to handling async well ...
No due date•0/5 issues closedv0.3 was focused on the support of more flexible versioning. For v0.4 we might want to focus on the flexibility of user-generated dependency constraints.
No due date•0/8 issues closedThe main driver for v0.3 is replacing the `Version` trait with the `VersionSet` trait, making it a more flexible adaptation of our current `Range`. This change moves some of the implementation burden for set operations outside of the pubgrub library. So it is important that we provide better tools for helping users testing their implementations. This is especially true for the ordering of versions, which can generate hard to solve bugs. We can probably delay test helper tooling to version 0.3.1 though to avoid blocking release for an infinite duration. Considering v0.3 is a breaking change, we might want to revise our error handling story. Might be especially interesting to look at recent changes mentioned by Josh Triplett in its latest keynote at RustConf 2022 https://youtu.be/37yASSgrdGE However, just like for better testing tools, this reflection can be postponed for later, say v0.4 since it's not critical to the main feature we want to introduce in v0.3. Finally, we want to decide if we get rid of interior mutability in the API, for the sake of simpler reasoning and implementations.
No due date•10/11 issues closed