70 |
posted to gzz-dev. At this point, the PEG may still be edited |
posted to gzz-dev. At this point, the PEG may still be edited |
71 |
in response to comments from the list. |
in response to comments from the list. |
72 |
|
|
73 |
|
As long as the PEG is in Incomplete or Current state, the author |
74 |
|
may change its status to Current, Incomplete (for revision), |
75 |
|
or Irrelevant (e.g., other PEGs superceded the current one). |
76 |
|
|
77 |
**NOTE**: PEGs should not be made Current as long as there are unresolved |
**NOTE**: PEGs should not be made Current as long as there are unresolved |
78 |
issues. If the responses from the list raise issues that cannot be immediately |
issues. If the responses from the list raise issues that cannot be immediately |
79 |
resolved, the PEG should be put into Incomplete state again. |
resolved, the PEG should be put into Incomplete state again. |
80 |
|
|
81 |
At some point after this, the architect (tjl) will make a decision |
At some point after this, the architect (tjl) will make a decision |
82 |
to either accept, force revision, declare rejected, or declare |
to either accept, force revision, declare rejected, or declare |
83 |
irrelevant (e.g. other PEGs superceded the current one). No-one |
irrelevant. No-one else may change the status of the PEGs |
84 |
else may change the status of the PEGs to any of these categories. |
to Accepted or Rejected. |
85 |
|
|
86 |
If the PEG was accepted, rejected or declared irrelevant, it may not |
If the PEG was accepted, rejected or declared irrelevant, it may not |
87 |
be edited any more, except for the architect or author |
be edited any more, except for the architect or author |