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

Support a hotfix process #119

Closed
cgwalters opened this issue Mar 24, 2015 · 1 comment
Closed

Support a hotfix process #119

cgwalters opened this issue Mar 24, 2015 · 1 comment

Comments

@cgwalters
Copy link
Member

Suppose that an OS vendor wants to provide a custom tree just to a specific user that contains a hotfix.

Of course one mechanism for hot fixes could be #107
but let's presume for this bug that we are focusing on the "new tree" approach. (Although possibly provided as a delta, knowing the customer is running the latest tree).

Regardless, let's assume that this tree data is provided out of band - in a tarball, Docker container, or whatever that is only accessible to that user.

We want a user experience here where the user can:

  • Switch to the tree
  • The tree is clearly labeled as a hotfix
  • There is an easy command to swtich back to the mainline tree (e.g. rpm-ostree upgrade should clearly show a message that you're on a dead-end hotfix stream)

Things are obviously simpler here if the OS vendor provides online-accessible hotfixes, possibly in the same repository; then one can use rebase to switch to it.

@cgwalters
Copy link
Member Author

Calling this one fixed by ostreedev/ostree#212

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant