[Gzz-commits] gzz/doc/pegboard/201 PEG_201.rst

[Benja Fallenstein]

CVSROOT:        /cvsroot/gzz
Module name:    gzz
Changes by:     Benja Fallenstein <address@hidden>      03/02/22 13:55:37

Modified files:
        doc/pegboard/201: PEG_201.rst 

Log message:
        Process changes as discussed on gzz-dev

CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/gzz/gzz/doc/pegboard/201/PEG_201.rst.diff?tr1=1.13&tr2=1.14&r1=text&r2=text

Patches:
Index: gzz/doc/pegboard/201/PEG_201.rst
diff -u gzz/doc/pegboard/201/PEG_201.rst:1.13 
gzz/doc/pegboard/201/PEG_201.rst:1.14
--- gzz/doc/pegboard/201/PEG_201.rst:1.13       Wed Jan  1 11:20:14 2003
+++ gzz/doc/pegboard/201/PEG_201.rst    Sat Feb 22 13:55:37 2003
@@ -4,8 +4,8 @@
 
 :Authors:  Tuomas Lukka
 :Stakeholders: Asko Soukka
-:Last-Modified: $Date: 2003/01/01 16:20:14 $
-:Revision: $Revision: 1.13 $
+:Last-Modified: $Date: 2003/02/22 18:55:37 $
+:Revision: $Revision: 1.14 $
 :Status:   Incomplete
 
 This META-PEG deals with formatting PEGs.
@@ -70,14 +70,18 @@
 posted to gzz-dev. At this point, the PEG may still be edited
 in response to comments from the list.
 
+As long as the PEG is in Incomplete or Current state, the author
+may change its status to Current, Incomplete (for revision),
+or Irrelevant (e.g., other PEGs superceded the current one).
+
 **NOTE**: PEGs should not be made Current as long as there are unresolved
 issues. If the responses from the list raise issues that cannot be immediately
 resolved, the PEG should be put into Incomplete state again.
 
 At some point after this, the architect (tjl) will make a decision
 to either accept, force revision, declare rejected, or declare
-irrelevant (e.g. other PEGs superceded the current one). No-one
-else may change the status of the PEGs to any of these categories.
+irrelevant. No-one else may change the status of the PEGs 
+to Accepted or Rejected.
 
 If the PEG was accepted, rejected or declared irrelevant, it may not
 be edited any more, except for the architect or author