forked from sofastack/sofa-jraft
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Block
authored
Oct 21, 2021
1 parent
c72a9b6
commit 280decf
Showing
2 changed files
with
70 additions
and
0 deletions.
There are no files selected for viewing
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,35 @@ | ||
- Feature Name: XXXX | ||
- Date: YYYY-MM-DD | ||
- RFC PR: # | ||
|
||
## Summary | ||
|
||
One para explanation of the proposal. | ||
|
||
## Motivation | ||
|
||
Why are we doing this? What use cases does it support? What is the expected | ||
outcome? | ||
|
||
## Detailed Design | ||
|
||
This is the bulk of the RFC. Explain the design in enough detail that: | ||
|
||
- It is reasonably clear how the feature would be implemented. | ||
- Corner cases dissected by example. | ||
- How is the feature used. | ||
|
||
## Drawbacks | ||
|
||
Why should we not do this? | ||
|
||
## Alternative | ||
|
||
- Why is this design the best in the space of possible designs? | ||
- What other designs have been considered and what is the rationale for not | ||
choosing them? | ||
- What is the impact of not doing this? | ||
|
||
## Unresolved questions | ||
|
||
What parts of the design are still to be determined? |
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,35 @@ | ||
- Feature Name: XXXX | ||
- Date: YYYY-MM-DD | ||
- RFC PR: # | ||
|
||
## Summary | ||
|
||
One para explanation of the proposal. | ||
|
||
## Motivation | ||
|
||
Why are we doing this? What use cases does it support? What is the expected | ||
outcome? | ||
|
||
## Detailed Design | ||
|
||
This is the bulk of the RFC. Explain the design in enough detail that: | ||
|
||
- It is reasonably clear how the feature would be implemented. | ||
- Corner cases dissected by example. | ||
- How is the feature used. | ||
|
||
## Drawbacks | ||
|
||
Why should we not do this? | ||
|
||
## Alternative | ||
|
||
- Why is this design the best in the space of possible designs? | ||
- What other designs have been considered and what is the rationale for not | ||
choosing them? | ||
- What is the impact of not doing this? | ||
|
||
## Unresolved questions | ||
|
||
What parts of the design are still to be determined? |