adds release conventions

This commit is contained in:
Raffaele Di Fazio 2021-04-06 17:40:08 +02:00 committed by GitHub
parent 103a0089a5
commit a5ddddbfb6
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

View File

@ -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