mirrors/tor
1
0
Fork 0
mirror of https://gitlab.torproject.org/tpo/core/tor.git synced 2024-11-20 10:12:15 +01:00
Code Issues Projects Releases Wiki Activity

SVN-specific metadata should no longer be part of a proposal

Browse Source 
Update the proposal creation instructions to remove the Version
and Last-Modified fields.
This commit is contained in:
Sebastian Hahn 2009-05-05 15:48:23 +02:00
parent df8a47464a
commit d0cb5e5b0b
1 changed files with 2 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
doc/spec/proposals/001-process.txt
View File

@ -47,7 +47,7 @@ How to change the specs now:
Like an RFC, every proposal gets a number. Unlike RFCs, proposals can Like an RFC, every proposal gets a number. Unlike RFCs, proposals can
change over time and keep the same number, until they are finally change over time and keep the same number, until they are finally
accepted or rejected. The history for each proposal accepted or rejected. The history for each proposal
will be stored in the Tor Subversion repository. will be stored in the Tor repository.
Once a proposal is in the repository, we should discuss and improve it Once a proposal is in the repository, we should discuss and improve it
until we've reached consensus that it's a good idea, and that it's until we've reached consensus that it's a good idea, and that it's
@ -82,9 +82,7 @@ How new proposals get added:
What should go in a proposal: What should go in a proposal:
Every proposal should have a header containing these fields: Every proposal should have a header containing these fields:
Filename, Title, Version, Last-Modified, Author, Created, Status. Filename, Title, Author, Created, Status.
The Version and Last-Modified fields should use the SVN Revision and Date
tags respectively.
These fields are optional but recommended: These fields are optional but recommended:
Target, Implemented-In. Target, Implemented-In.