Skip to content

Update lifecycle doc for exernal stack providers #495

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.

Sign up for GitHub

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

Merged
Jdubrick merged 2 commits into from
Nov 22, 2024
Merged

Update lifecycle doc for exernal stack providers #495

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
515cab3
update lifecycle doc for exernal stack providers
Jdubrick Nov 22, 2024
add79cf
reword to remove rh explicit
Jdubrick Nov 22, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions LIFECYCLE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,6 +16,8 @@ The following sections describe the steps that can happen in the lifecycle of a
## [Onboarding](CONTRIBUTING.md)
When a `Stack Provider` is ready to share their devfile to the public registry, they must follow the steps in the [contributing guide](CONTRIBUTING.md) to ensure there’s basic information that identifies the version, owner, description, etc. of the stack or sample. They must also ensure the stack or sample meets minimal testing requirements against the supported clients.

In some cases new `Stack Providers` may be accepted on a trial basis. In this case, the owner listed in [`.github/CODEOWNERS`](./.github/CODEOWNERS) will be the `Devfile Team` to limit the number of users with repository write-acess. These `Stack Providers` will begin on a 3-month trial basis where the `Devfile Team` reserves the right to deprecate if they feel the stack is not properly maintained.

| Role | Responsibilities |
|:-----------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| `Stack Provider` | <ul>Follow the [contributing guide](CONTRIBUTING.md) and ensure stack or sample is tested against the supported clients </ul> |
Expand Down Expand Up @@ -45,6 +47,7 @@ When a stack or sample is no longer maintained due to inactivity, lack of timely

* Deprecated devfiles will remain in the community registry for 1 year before it’s removed.

The only exception to the above rules regarding deprecation are in the case that the `Stack Provider` is still within their trial period. In that case the `Devfile Team` reserves the right to deprecate the stack without agreement from the `Stack Provider`.

| Role | Responsibilities |
|:------------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
Expand Down
Loading