Status and Support Level #263
Conversation
Co-authored-by: Fabrizio Ferri-Benedetti <[email protected]>
|
For our own protection this file needs to contain headers included in the source document. Especially it has to directly refer to Splunk Terms and Conditions link as main source of definitions. |
|
|
||
| **Status**: [Experimental](../README.md#versioning-and-status-of-the-specification) | ||
|
|
||
| ## Definitions of status levels |
There was a problem hiding this comment.
The status levels definitions are scattered in two places (here and specification/versioning.md). It makes me hard to follow.
I think that there are 3 concepts and they should be described in the following order:
- status levels and development stages of components
- support levels depending on the component owner and status level
- versioning (and structuring) depending on component status level
I propose to describe everything above in a file named component-status.md or simply status.md. I think we can even get rid of versioning.md as I do not think we need to call out the specification versioning policy.
There was a problem hiding this comment.
well - it is not that simple - I think I would follow with the change as proposed - We need much more time to restructure whole thing + versioning policy is required
There was a problem hiding this comment.
Based on the conversion it should be spitted into 3 documents:
status.mdsupport.mdversioning.md
In future we will also need releasing.md defining the component releasing requirements.
Changing the PR to draft.
|
@akubik-splunk, I am closing this PR as a stale. Feel free to reopen when needed. |
Definitions prepared by @akubik-splunk.