Skip to content

Discuss: guidelines for a package with breaking changes #229

@mtojek

Description

@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

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions