Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
flux2
Manage
Activity
Members
Code
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Deploy
Releases
Model registry
Analyze
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
GitLab community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
GitHub Mirror
fluxcd
flux2
Commits
c5b2c670
Unverified
Commit
c5b2c670
authored
3 years ago
by
Stefan Prodan
Browse files
Options
Downloads
Patches
Plain Diff
Add status, creation and last update date fields to RFC template
Signed-off-by:
Stefan Prodan
<
stefan.prodan@gmail.com
>
parent
8354ac93
No related branches found
No related tags found
No related merge requests found
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
rfcs/README.md
+15
-3
15 additions, 3 deletions
rfcs/README.md
with
15 additions
and
3 deletions
rfcs/README.md
+
15
−
3
View file @
c5b2c670
...
...
@@ -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 a
nswer
the following questions:
The design details should a
ddress 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?
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment