Add Lifecycle doc proposal

[kim-tsao]

What does this PR do?

"Converts" the existing PR to a proposal as discussed in today's stand-up. We can't publish the doc until stories in the Epic are done so we will park it as a proposal and wait for more feedback for now

Which issue(s) does this PR fix

#1066

PR acceptance criteria

Testing and documentation do not need to be complete in order for this PR to be approved. We just need to ensure tracking issues are opened.

• Open new test/doc issues under the devfile/api repo
• Check each criteria if:
• There is a separate tracking issue. Add the issue link under the criteria
  or
• test/doc updates are made as part of this PR
• If unchecked, explain why it's not needed

• Unit/Functional tests

• QE Integration test

• Documentation

• Client Impact

How to test changes / Special notes to the reviewer

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 35.75%. Comparing base (e05a235) to head (911cbd4).
Report is 10 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1286      +/-   ##
==========================================
- Coverage   35.79%   35.75%   -0.05%     
==========================================
  Files          52       52              
  Lines        6679     6696      +17     
==========================================
+ Hits         2391     2394       +3     
- Misses       4144     4158      +14     
  Partials      144      144              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[github-actions]

This PR is stale because it has been open for 90 days with no activity. Remove stale label or comment or this will be closed in 60 days.

[thepetk]

@elsony @amisevsk @yangcao77 & @johnmcollier fyi the devfile/registry#208 is merged.

I've noticed we had this PR too opened so we can track the process of the proposal. IMO it would be a good thing to link the lifecycle doc here too. Could you please review?

[michael-valdron]

/lgtm

We could merge this for archival sake, also a link to our registry lifecycle from here. We could also include something like this in one of our other devfile api docs which make mention of the devfile registry. What does everybody else think?

cc: @thepetk @johnmcollier @yangcao77 @amisevsk

[michael-valdron]

/lgtm

We could merge this for archival sake, also a link to our registry lifecycle from here. We could also include something like this in one of our other devfile api docs which make mention of the devfile registry. What does everybody else think?

cc: @thepetk @johnmcollier @yangcao77 @amisevsk

cc: @elsony

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: johnmcollier, kim-tsao, michael-valdron

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment