Merged
Conversation
Includes now status attribute and list of allowed options
Both Schemas now contain the status attribute with options as optional attribute
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Reference to related issue
#5
This PR adds a status field to productStrategy and updates both the YAML and JSON Schemas.
Change
New field: productStrategy.status
Allowed values: Planned, Active, At Risk, Achieved, Partially Achieved, Cancelled, Expired
Rationale
Separates strategy execution status from product lifecycle status and supports governance and reporting.
Breaking changes
None
---- Leave intact! Approval of Contributor Agreement -----
By submitting pull request you approve the Contributor Agreement, https://governance.opendataproducts.org/v1/contributions/contributor-agreement