inovex / mqtt-stresser

Load testing tool to stress MQTT message broker

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

introduce proper (semantic) versionioning

arnisoph opened this issue · comments

introduce proper (semantic) versionioning

I think we should stick with the simple incremental versioning. I think this project does not contain any code another project wants to import. Introducing semantic versioning does not give any benefit. benchmarks are only compareable with the same software version. Even a patch might alter the benchmark result. Thus why bother with the overhead of semantic versioning?

I agree semantic version doesn't fit to our release plan at the moment. Closing for now..