Unverified Commit a5ddddbf authored by Raffaele Di Fazio's avatar Raffaele Di Fazio Committed by GitHub
Browse files

adds release conventions

Showing with 10 additions and 0 deletions
+10 -0
......@@ -4,6 +4,16 @@
Currently we don't release regularly. Whenever we think it makes sense to release a new version we do it, but we aim to do a new release every month. You might want to ask in our Slack channel [external-dns](https://kubernetes.slack.com/archives/C771MKDKQ) when the next release will come out.
## Versioning convention
Those are the conventions that we will be using for releases following `0.7.6`:
- **Patch** version should be updated if we need to merge bugfixes, e.g. provider a does need a fix in order make updates working again. I would see updating or improving documentation here.
- **Minor** version should be updated if new features are implemented in existing providers or new provider get introduced.
- **Major** version should be upgraded if we introduce breaking changes.
## How to release a new image
### Prerequisite
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment