Skip to content

Remove trailing whitespace from template. #93

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
merged 1 commit into from
Oct 1, 2021
Merged

Remove trailing whitespace from template. #93

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
10 changes: 5 additions & 5 deletions enhancements/template.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,7 +12,7 @@ creation-date: yyyy-mm-dd
last-updated: yyyy-mm-dd
status: provisional|implementable|implemented|deferred|rejected|withdrawn|replaced
see-also:
- "/enhancements/this-other-neat-thing.md"
- "/enhancements/this-other-neat-thing.md"
replaces:
- "/enhancements/that-less-than-great-idea.md"
superseded-by:
Expand Down Expand Up @@ -61,17 +61,17 @@ around the enhancement process.
## Open Questions [optional]

This is where to call out areas of the design that require closure before deciding
to implement the design. For instance,
to implement the design. For instance,
> 1. This requires exposing previously private resources which contain sensitive
information. Can we do this?
information. Can we do this?

## Summary

The `Summary` section is incredibly important for producing high quality
user-focused documentation such as release notes or a development roadmap. It
should be possible to collect this information before implementation begins in
order to avoid requiring implementors to split their attention between writing
release notes and implementing the feature itself.
release notes and implementing the feature itself.

A good summary is probably at least a paragraph in length.

Expand Down Expand Up @@ -166,7 +166,7 @@ These are generalized examples to consider, in addition to the aforementioned
- Sufficient test coverage
- Gather feedback from users rather than just developers

##### Tech Preview -> GA
##### Tech Preview -> GA

- More testing (upgrade, downgrade, scale)
- Sufficient time for feedback
Expand Down