Discuss: guidelines for a package with breaking changes

[mtojek]

Hi,

This is rather a discuss issue. Let's say that we can't introduce compatibility pipelines as there are too many changes in the package, data streams, etc. - it was deeply refactored.

What is the recommendation in this case? Should we create a new package, e.g. kubernetesv2 or just modify the existing one, or add extra data stream and deprecate legacy ones?

cc @mostlyjason @akshay-saraswat

[ruflin]

This also relates to package deprecation as at some point, deprecated packages need to be removed: #227 Same commend as I made related to deprecation, breaking changes can be on different levels in a package and for each we should have a recommended path.