Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create a single repository for all versionize-* crates #21

Open
andreeaflorescu opened this issue Sep 8, 2020 · 0 comments
Open

Create a single repository for all versionize-* crates #21

andreeaflorescu opened this issue Sep 8, 2020 · 0 comments
Labels
enhancement New feature or request

Comments

@andreeaflorescu
Copy link
Member

Having separate repositories for versionize crates is making the development of the versionize functionality cumbersome because a change in versionize-derive typically needs to be accompanied by a change in versionize. This will happen in separate PRs and requires versionize-derive to be published first.

Testing is also not easy on the versionize-derive crate (crate has 0.9% coverage score). A bug in versionize-derive will most likely be caught only after it is used in versionize.

These problems can be fixed by having both crates hosted in the same repositories using Cargo workspace. The crates can still be published independently.

The same approach is proposed for kvm related crates as well. You can take a look at this issue: rust-vmm/community#98

This is also the same approach used by serde: https://github.com/serde-rs/serde

@andreeaflorescu andreeaflorescu added the enhancement New feature or request label Sep 8, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant