@@ -3,6 +3,7 @@ RFC: 0000
3
3
Author : Steve Lee
4
4
Status : Draft
5
5
Area : Process
6
+ Version : 1.1
6
7
Feedback : https://github.com/PowerShell/PowerShell-Language-RFC/issues/5
7
8
---
8
9
@@ -35,6 +36,7 @@ RFC documents shall follow the following template:
35
36
RFC: <four digit unique incrementing number>
36
37
Author: <First Last>
37
38
Status: <Draft | Experimental | Accepted | Rejected | Final>
39
+ Version: <Major>.<Minor>
38
40
Area: <Area within the PowerShell language>
39
41
---
40
42
@@ -56,19 +58,24 @@ Description and rationale.
56
58
57
59
## RFC Workflow
58
60
59
- RFCs go through several stages:
61
+ RFCs go through applicable stages:
60
62
61
63
* Draft
62
64
63
65
This is the initial draft of a RFC posted for comments and considered a
64
66
work-in-progress. Typically, two months is allowed for comments.
65
67
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
+
66
73
* Experimental
67
74
68
75
Comments have been reviewed and code is being written to provide an working
69
76
example of the proposed design change to get further feedback.
70
77
71
- * Accepted
78
+ * Experimental- Accepted
72
79
73
80
Feedback from the experimental implementation and RFC have been reviewed.
74
81
Engineering 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.
82
89
83
90
Design and implementation is considered complete. Any proposed changes
84
91
would 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