@@ -3,6 +3,7 @@ RFC: 0000
33Author : Steve Lee
44Status : Draft
55Area : Process
6+ Version : 1.1
67Feedback : https://github.com/PowerShell/PowerShell-Language-RFC/issues/5
78---
89
@@ -35,6 +36,7 @@ RFC documents shall follow the following template:
3536RFC: <four digit unique incrementing number >
3637Author: <First Last >
3738Status: <Draft | Experimental | Accepted | Rejected | Final>
39+ Version: <Major >.<Minor >
3840Area: <Area within the PowerShell language >
3941---
4042
@@ -56,19 +58,24 @@ Description and rationale.
5658
5759## RFC Workflow
5860
59- RFCs go through several stages:
61+ RFCs go through applicable stages:
6062
6163* Draft
6264
6365This is the initial draft of a RFC posted for comments and considered a
6466work-in-progress. Typically, two months is allowed for comments.
6567
68+ * Draft-Accepted
69+
70+ Comments have been reviewed and new comments are not being sought. Code
71+ work has not started/planned or not needed.
72+
6673* Experimental
6774
6875Comments have been reviewed and code is being written to provide an working
6976example of the proposed design change to get further feedback.
7077
71- * Accepted
78+ * Experimental- Accepted
7279
7380Feedback from the experimental implementation and RFC have been reviewed.
7481Engineering team will work towards final implementation in code to match
@@ -82,3 +89,7 @@ Based on community feedback, this RFC was decided to not proceed any further.
8289
8390Design and implementation is considered complete. Any proposed changes
8491would be through a new RFC.
92+
93+ ---
94+ History:
95+ v1.1 - 5-20-2016 - Updated to enable RFCs for design changes that don't require code changes. Added Draft-Accepted state and Version header property.
0 commit comments