diff options
| author | Bryan Newbold <bnewbold@archive.org> | 2018-01-05 13:57:05 +0100 |
|---|---|---|
| committer | Bryan Newbold <bnewbold@archive.org> | 2018-01-05 13:57:05 +0100 |
| commit | c7082aecd14121c04dbc6584d704026eeee04dab (patch) | |
| tree | 43712d7f133c32a81a0384050d65cd32ab319ffd /rfcs | |
| parent | 38b2aab96f9ad2bbf4ace6bbef47670c41240828 (diff) | |
| download | dat-docs-c7082aecd14121c04dbc6584d704026eeee04dab.tar.gz dat-docs-c7082aecd14121c04dbc6584d704026eeee04dab.zip | |
changelog section in RFC template
Diffstat (limited to 'rfcs')
| -rw-r--r-- | rfcs/template.md | 8 |
1 files changed, 8 insertions, 0 deletions
diff --git a/rfcs/template.md b/rfcs/template.md index 78fdeb9..6fa0386 100644 --- a/rfcs/template.md +++ b/rfcs/template.md @@ -47,3 +47,11 @@ Why should we *not* do this? - What parts of the design do you expect to resolve through the RFC consensus process before this gets merged? - What parts of the design do you expect to resolve through implementation and code review, or are left to independent library or application developers? - What related issues do you consider out of scope for this RFC that could be addressed in the future independently of the solution that comes out of this RFC? + +# Changelog +[changelog]: #changelog + +A brief statemnt about current status can go here, follow by a list of dates +when the status line of this RFC changed (in most-recent-last order). + +- YYYY-MM-DD: First complete draft submitted for review |