| title | target-version |
|---|---|
feature-name |
release-X.X |
List the specific goals of the proposal. How will we know that this has succeeded?
What is out of scope for this proposal? Listing non-goals helps to focus discussion and make progress.
This is where we get down to the nitty gritty of what the proposal actually is. API changed in any, Golang snippets.
What are the risks of this proposal and how do we mitigate. Think broadly. For example, consider both security and how this will impact the larger OKD ecosystem.
The idea is to find the best form of an argument why this feature should not be implemented.
Similar to the Drawbacks section the Alternatives section is used to
highlight and record other possible approaches to delivering the value proposed
by a feature.
This is where to call out areas of the design that require closure before deciding to implement the design.