actions/fluxcd-flux2
3
0
Fork 0
mirror of https://github.com/fluxcd/flux2.git synced 2026-02-08 00:37:27 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

Add status, creation and last update date fields to RFC template

Browse source 
Signed-off-by: Stefan Prodan <stefan.prodan@gmail.com>
This commit is contained in:
Stefan Prodan 2021-11-30 14:54:02 +02:00
parent 8354ac937c
commit c5b2c6709a
No known key found for this signature in database
GPG key ID: 3299AEB0E4085BAF
1 changed files with 15 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

18
rfcs/README.md
View file

@ -28,6 +28,17 @@ Examples of substantial changes:
The title must be short and descriptive.
-->
**Status:** provisional
<!--
Status represents the current state of the RFC.
Must be one of `provisional`, `implementable`, `implemented`, `deferred`, `rejected`, `withdrawn`, or `replaced`.
-->
**Creation Date:** YYYY-MM-DD
**Last update:** YYYY-MM-DD
## Summary
<!--
@ -73,8 +84,9 @@ Optional if existing discussions and/or issues are linked in the motivation sect
### Alternatives
<!--
List plausible alternatives to the proposal and
motivate why the current proposal is superior.
List plausible alternatives to the proposal and explain why the proposal is superior.
This is a good place to incorporate suggestions made during discussion of the RFC.
-->
## Design Details
@ -83,7 +95,7 @@ motivate why the current proposal is superior.
This section should contain enough information that the specifics of your
change are understandable. This may include API specs and code snippets.
The design details should answer the following questions:
The design details should address at least the following questions:
- How can this feature be enabled / disabled?
- Does enabling the feature change any default behavior?
- Can the feature be disabled once it has been enabled?