Track breaking chart version changes

[mmattel]

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

[wkloucek]

I think we have this already fulfilled, right?

[mmattel]

I propose a change file or files which document the changes from one tagged version to the next
+
I think we have this already fulfilled, right?

Mind to point me to the/a changelog file?
I just maybe blind but I havn't found one.
Currently I am collecting changes I identify manually in Mention list for upgrading to the next ocis release to ease doc life, but this is not a future proof way.

[wkloucek]

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

[mmattel]

Sorry, hair-splitting, I do not agree.

• The result of breaking changes are shown in the doc link, where the source of that info is currently coming only via the tracking I make or via discussion with you. Not future proof as written.
• The changelog issue is currently an issue only, as this one.

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.