statsd_exporter
statsd_exporter copied to clipboard
1.0 release
This exporter is pretty stable, it would be nice to make it 1.0 with update stability for the mapping config file.
What will the consequences be for library users, and for maintaining library code? So far, being in 0.x, we have been playing it loose, with changelog notices for any breaking changes; I don't know if this has caused issues for someone.
With Go 1.18, we can experiment with workspaces to separate the versioning of the library from the binary. That would unlock a stable release for the both without tying them together.