Suggestion: Semantic Verisoning / 1.0

[callum-tait-pbx]

@mumoshu yourself and the community has done some amazing work with the project and I think over the last couple of months it has really come together. I wanted to suggest that after the docker changes are merged and working we should move to 1.0 and we start releasing based on semantic versioning to indicate breaking changes?

I mention this as the system now has a few dependencies on APIs. It would be useful if releases could indicate if it is a breaking change because we are updating the version of APIs used going forward. The 2 that immediately pop into my head are:

• cert-manager APIs. cert-manager has gone 1.0 and so you can start expecting enterprises to expect some stability and for cert-manager to gain some momentum now that it is in 1.0
• K8s APIs Update deprecated APIs #144 (this should probably be looked at soonish)

Thoughts?

[callum-tait-pbx]

We've moved to Helm which comes with it semantic verisoning in the chart.yaml, this is no longer needed