Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Discuss: guidelines for a package with breaking changes #229

Open
mtojek opened this issue Oct 13, 2021 · 1 comment
Open

Discuss: guidelines for a package with breaking changes #229

mtojek opened this issue Oct 13, 2021 · 1 comment
Labels
discuss Issue needs discussion migration-path

Comments

@mtojek
Copy link
Contributor

mtojek commented Oct 13, 2021 •
edited
Loading

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
@mtojek mtojek added discuss Issue needs discussion migration-path labels Oct 13, 2021
@ruflin
Copy link
Contributor

ruflin commented Nov 25, 2021

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.

@jsoriano jsoriano mentioned this issue Aug 10, 2022
Closed
@jsoriano jsoriano mentioned this issue Oct 16, 2024
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
discuss Issue needs discussion migration-path
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@ruflin @mtojek