This PR prepares the project for an initial 0.1.0 release on crates.io, by completing READMEs, adding metadata to Cargo.toml files.
Even if we only have a few services implemented, it is already usable and can be of value to some other projects.
My thought for how we would handle versioning up to 1.0.0 is that we would:
bump the minor version (0.1.0 -> 0.2.0) if we make breaking changes to existing APIs or add a new service integration (pre-1.0.0 versions are allowed to do breaking changes over a minor bump).
bump the patch version (0.1.0 -> 0.1.1) if we do changes that are only observable internally.
This PR prepares the project for an initial
0.1.0
release on crates.io, by completing READMEs, adding metadata toCargo.toml
files.Even if we only have a few services implemented, it is already usable and can be of value to some other projects.
My thought for how we would handle versioning up to
1.0.0
is that we would:0.1.0
->0.2.0
) if we make breaking changes to existing APIs or add a new service integration (pre-1.0.0
versions are allowed to do breaking changes over a minor bump).0.1.0
->0.1.1
) if we do changes that are only observable internally.