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.

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

kpt pkg rebase #2548

Open
bgrant0607 opened this issue Oct 12, 2021 · 0 comments
Open

kpt pkg rebase #2548

bgrant0607 opened this issue Oct 12, 2021 · 0 comments
Labels
area/pkg design-doc enhancement New feature or request p2 triaged Issue has been triaged by adding an `area/` label

Comments

@bgrant0607
Copy link
Contributor

Kpt makes it pretty easy to fork a fork of a fork, though it doesn't explicitly have the concept of a fork (see #2544).

I'd like to keep versioning simple, rather than trying to use something like semantic versioning: A.B.C.D.E.F...

For continuously delivered configuration, I am leaning towards a single version integer.

However, I may want to switch to another branch of the package inheritance at some point -- think of it as like a major version change.

To do that, I think we would need a "kpt pkg rebase" command to switch to a new upstream.

Without recording the branch points of the tree, I'm not sure how to implement the 3-way merge, but it's worth thinking about.

cc @justinsb

@bgrant0607 bgrant0607 added the enhancement New feature or request label Oct 12, 2021
@droot droot added area/pkg triaged Issue has been triaged by adding an `area/` label labels Oct 20, 2021
@phanimarupaka phanimarupaka self-assigned this Nov 2, 2021
@droot droot assigned droot and unassigned droot and phanimarupaka Mar 21, 2022
@mortent mortent added this to kpt Jan 21, 2023
@mortent mortent moved this to Backlog in kpt Jan 25, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/pkg design-doc enhancement New feature or request p2 triaged Issue has been triaged by adding an `area/` label
Projects
None yet
Development

No branches or pull requests

4 participants