Skip to content
This repository has been archived by the owner on May 17, 2022. It is now read-only.

Distribution and automation of patches for software being developed #51

Closed
itscooper opened this issue Oct 13, 2018 · 3 comments
Closed
Assignees

Comments

@itscooper
Copy link
Collaborator

Where does this fit? How to distribute your own patches to customers. Do you force them?

@23bartman
Copy link
Collaborator

IMO this should go under Environment Management, stream B: Patching and Updating. but it's currently not described there. Do you agree ?

@dkefer
Copy link
Collaborator

dkefer commented Jun 2, 2019

If I understand the query correctly, I'm not quite sure this belongs in the model, given the implicit separation of responsibilities between a vendor and a customer.

IMHO as a customer, I'm responsible for patching of software provided by my vendor entirely myself. If it's otherwise, it's probably rather vendor's business decision than sign of particular maturity.

Maybe I'm overseeing sth? An example might help.

@SebaDele
Copy link
Member

covered in #53

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

No branches or pull requests

5 participants