Develop a Devfile Lifecycle management process

[kim-tsao]

Which area this feature is related to?

/area documentation

Which area is this documentation change is related to?

/area registry

Issue details

Currently, we only have onboarding instructions for our registry. We need to expand on what we have and document what it means to own and maintain a devfile throughout the course of its lifespan

What mistake did you find / what is missing in the documentation?

[kim-tsao]

March 20, 2023:

Discussed details of the deprecation process in today's community call and it was suggested that we set a 1 yr time limit to remove community devfiles whereas, we can leave deprecated devfiles in the product registry indefinitely for now. We can always adjust the timeframes as needed.

[github-actions]

This issue 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.

[kim-tsao]

As discussed in our stand up today, we will not publish this just yet because there are dependent items in the Epic that need to be in place. We will put this PR in waiting state and create a proposal which will link to this.

[thepetk]

Bringing this item back in progress and handle the review & merge of the related PR

[thepetk]

Putting item in progress status as a discussion over the proposed PR will be open

[thepetk]

The issue is now under review as the proposed PR is ready to get more reviews from the team & the stack owners

[thepetk]

devfile/registry#208 is now merged. The only detail remains for the documentation is to merge the proposal PR #1286 too

cc @kim-tsao

[thepetk]

cc @kim-tsao

Closing this issue as the #1286 is now merged