aboutsummaryrefslogtreecommitdiff
path: root/doc/spec/proposals/001-process.txt
diff options
context:
space:
mode:
authorNick Mathewson <nickm@torproject.org>2008-07-14 20:44:44 +0000
committerNick Mathewson <nickm@torproject.org>2008-07-14 20:44:44 +0000
commitb2da39fd9d42813e71f1cf33a837a20dd8e8024f (patch)
treea8cd374200513ea9cd0b0c4542ba2ea1766edbeb /doc/spec/proposals/001-process.txt
parent36d6f50d09c759355741be4fad9254512cacdda5 (diff)
downloadtor-b2da39fd9d42813e71f1cf33a837a20dd8e8024f.tar
tor-b2da39fd9d42813e71f1cf33a837a20dd8e8024f.tar.gz
For some open and accepted proposals, note their target versions.
svn:r15904
Diffstat (limited to 'doc/spec/proposals/001-process.txt')
-rw-r--r--doc/spec/proposals/001-process.txt7
1 files changed, 7 insertions, 0 deletions
diff --git a/doc/spec/proposals/001-process.txt b/doc/spec/proposals/001-process.txt
index e23f7c978..3a767b5fa 100644
--- a/doc/spec/proposals/001-process.txt
+++ b/doc/spec/proposals/001-process.txt
@@ -86,6 +86,13 @@ What should go in a proposal:
The Version and Last-Modified fields should use the SVN Revision and Date
tags respectively.
+ These fields are optional but recommended:
+ Target, Implemented-In.
+ The Target field should describe which version the proposal is hoped to be
+ implemented in (if it's Open or Accepted). The Implemented-In field
+ should describe which version the proposal was implemented in (if it's
+ Finished or Closed).
+
The body of the proposal should start with an Overview section explaining
what the proposal's about, what it does, and about what state it's in.