File tree 2 files changed +4
-2
lines changed 2 files changed +4
-2
lines changed Original file line number Diff line number Diff line change 7
7
# Kani RFCs
8
8
9
9
- [ 0001-mir-linker] ( rfcs/0001-mir-linker.md )
10
+ - [ 0002-function-stubbing] ( rfcs/0002-function-stubbing.md )
10
11
Original file line number Diff line number Diff line change @@ -34,9 +34,10 @@ This is the overall workflow for the RFC process:
34
34
1 . Create an RFC
35
35
1 . Create a tracking issue for your RFC (e.g.: [ Issue-1588] ( https://github.com/model-checking/kani/issues/1588 ) ).
36
36
2 . Start from a fork of the Kani repository.
37
- 3 . Copy the template file ([ ` rfc/src/template.md ` ] ( ./template.md ) ) to ` rfc/src/<ID_NUMBER><my-feature>.md ` .
37
+ 3 . Copy the template file ([ ` rfc/src/template.md ` ] ( ./template.md ) ) to ` rfc/src/rfcs/ <ID_NUMBER><my-feature>.md ` .
38
38
4 . Fill in the details according to the template instructions.
39
- 5 . Submit a pull request.
39
+ 5 . Add a link to the new RFC inside [ ` rfc/src/SUMMARY.md ` ] ( https://github.com/model-checking/kani/blob/main/rfc/src/SUMMARY.md )
40
+ 6 . Submit a pull request.
40
41
2 . Build consensus and integrate feedback.
41
42
1 . RFCs should get approved by at least 2 Kani developers.
42
43
2 . Once the RFC has been approved, update the RFC status and merge the PR.
You can’t perform that action at this time.
0 commit comments