-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Track breaking chart version changes #78
Comments
I think we have this already fulfilled, right? |
Mind to point me to the/a changelog file? |
This ticket is about breaking changes and we have that: https://doc.owncloud.com/ocis/next/deployment/container/orchestration/tab-pages/breaking-changes.html A general changelog is tracked by #325 |
Sorry, hair-splitting, I do not agree.
We can combine both issues and the result is that there is a changelog file here in ocis-charts that contains both normal and breaking changes. As long there is no physical changelog file present containing both normal and breaking changes, both issues are valid and open. |
We have a note in the documentation that a major (breaking) chart change needs manual intervention, but there is nothing described about how to identify the relevant change.
When we will introduce tagging, I propose a change file or files which document the changes from one tagged version to the next which we can include into the documentation. This will help readers to quickly identify those items to take a closer look on.
The HowTo needs to be discussed, but I guess it can be achieved via script.
@wkloucek @dragonchaser
The text was updated successfully, but these errors were encountered: