search

VoltDB / voltdb-client-go

VoltDB Golang Client Library
MIT License
32 stars 19 forks source link

Semantic versioning #46

Closed igungor closed 6 years ago

igungor commented 6 years ago

Hello,

Would you consider tagging the package so that projects can depend on a specific versions?

benjaminballard commented 6 years ago

Sure, this is possible. What sort of versioning would you recommend?

We don't make major changes to client libraries very often, so it could remain on a version for a while, but it may be beneficial for users to get the latest incremental fixes / improvements typically submitted by contributors. Today we may just merge these minor changes to master and anyone building the latest will get them, but I don't know if it makes sense to update the version for these small changes, or just use numbers like 1.0.1, 1.0.2, etc for small changes. I'd appreciate your advice.

igungor commented 6 years ago

I think following the VoltDB versions would be too strict for the client maintainers. An independent versioning, especially following the https://semver.org/ is very common and considered best practice.

If the project activity is low (especially commit frequency), even a single commit could worth a new release, which makes sense to me. I think it's better than relying on master (without pinning to a specific commit hash) since HEAD could break the API (I guess that won't happen for the connector but still).

abradley201 commented 6 years ago

Thanks for the suggestion. I just tagged the current version as v1.0.0, and we are currently working on v1.1.0.