add lifecycle doc #208
add lifecycle doc #208
Conversation
There was a problem hiding this comment.
@kim-tsao I've added some minor suggestions. Feel free to reject them if you think they are not correct :)
A qq I have is about versioning. Should we include a section in the lifecycle doc about versioning or you think is un related (e.g how a stack provider should be versioning their stack's versions etc)
|
/retest |
|
In order to spread the word for the stack's lifecycle PR and get as many reviews as possible for the document, I'm listing here all stack providers. Feel free to review the PR so we can optimize our lifecycle processes: |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: kim-tsao, michael-valdron, thepetk The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
New changes are detected. LGTM label has been removed. |
Signed-off-by: Kim Tsao <[email protected]> Signed-off-by: thepetk <[email protected]>
Signed-off-by: thepetk <[email protected]> Co-authored-by: Armel Soro <[email protected]> Signed-off-by: thepetk <[email protected]>
Signed-off-by: thepetk <[email protected]>
Signed-off-by: thepetk <[email protected]> Co-authored-by: Armel Soro <[email protected]> Signed-off-by: thepetk <[email protected]>
Signed-off-by: thepetk <[email protected]>
Signed-off-by: thepetk <[email protected]> Co-authored-by: Armel Soro <[email protected]> Signed-off-by: thepetk <[email protected]>
Signed-off-by: thepetk <[email protected]> Co-authored-by: Armel Soro <[email protected]> Signed-off-by: thepetk <[email protected]>
Co-authored-by: Michael Valdron <[email protected]> Signed-off-by: thepetk <[email protected]>
Co-authored-by: Michael Valdron <[email protected]> Signed-off-by: thepetk <[email protected]>
Co-authored-by: Michael Valdron <[email protected]> Signed-off-by: thepetk <[email protected]>
Co-authored-by: Michael Valdron <[email protected]> Signed-off-by: thepetk <[email protected]>
Co-authored-by: Michael Valdron <[email protected]> Signed-off-by: thepetk <[email protected]>
Co-authored-by: Michael Valdron <[email protected]> Signed-off-by: thepetk <[email protected]>
Co-authored-by: Michael Valdron <[email protected]> Signed-off-by: thepetk <[email protected]>
Signed-off-by: thepetk <[email protected]>
Signed-off-by: thepetk <[email protected]>
Signed-off-by: thepetk <[email protected]>
Signed-off-by: thepetk <[email protected]>
Signed-off-by: thepetk <[email protected]> Co-authored-by: Mario Loriedo <[email protected]> Signed-off-by: thepetk <[email protected]>
What does this PR do?:
Summarize the changes. Are any stacks or samples added or updated?
Documents a proposed devfile lifecycle management process
Which issue(s) this PR fixes:
Link to github issue(s)
devfile/api#1066
PR acceptance criteria:
Have you read the devfile registry contributing guide and followed its instructions?
Does this repository's tests pass with your changes?
Does any documentation need to be updated with your changes?
Have you tested the changes with existing tools, i.e. Odo, Che, Console? (See devfile registry contributing guide on how to test changes)
How to test changes / Special notes to the reviewer: