Closed wadehunk closed 1 year ago
Agree, this is a good idea. We use semantic versioning on open-dis-java. Perhaps once we get #74 merged we'll tag a 1.0.0 release and then iterate releases from then onwards.
Actually perhaps we do #18 as well because it's potentially a breaking change right away.
I've got a draft for #18 and can submit a PR for it once #74 is completed.
Would be nice to have a versioned release of open-dis-cpp to support configuration management use cases for users of the library. Would recommend using semantic versioning to capture API breakages.