/[gzz]/gzz/doc/pegboard/201/PEG_201.rst
ViewVC logotype

Diff of /gzz/doc/pegboard/201/PEG_201.rst

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

revision 1.7 by tjl, Thu Nov 7 09:33:31 2002 UTC revision 1.8 by tjl, Fri Nov 8 13:37:04 2002 UTC
# Line 31  Issues Line 31  Issues
31          at any other point. Once an issue is resolved, the resolution          at any other point. Once an issue is resolved, the resolution
32          and its rationale should be here.          and its rationale should be here.
33    
34          NOTE: PEGs should not be accepted as long as there are          Issues should be clear **questions** which need answers.
35          unresolved issues.          "I'm not sure about X." would be much better phrased as
36            "Should we do X?". That way there is a clear question,
37            to which we are seeking a simple answer.
38    
39            Resolutions of issues should always contain reasoning
40            behind them::
41    
42                - should we do X?
43    
44                    RESOLVED: No
45    
46            is not good. Should be::
47    
48                - should we do X?
49    
50                    RESOLVED: No, since that would interfere with Y.
51    
52            Even ::
53    
54                - should we do X?
55    
56                    RESOLVED: No, not yet
57    
58            is much better, since it at least gives more information.
59    
60      - Do we need the Scope and Type fields?      - Do we need the Scope and Type fields?
61    
# Line 46  When the PEG seems ready for review, it Line 69  When the PEG seems ready for review, it
69  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
70  in response to comments from the list.  in response to comments from the list.
71    
72    **NOTE**: PEGs should not be made Current as long as there are unresolved
73    issues. If the responses from the list raise issues that cannot be immediately
74    resolved, the PEG should be put into Incomplete state again.
75    
76  At some point after this, the architect (tjl) will make a decision  At some point after this, the architect (tjl) will make a decision
77  to either accept, force revision, declare rejected, or declare  to either accept, force revision, declare rejected, or declare
78  irrelevant (e.g. other PEGs superceded the current one). No-one  irrelevant (e.g. other PEGs superceded the current one). No-one

Legend:
Removed from v.1.7  
changed lines
  Added in v.1.8

savannah-hackers-public@gnu.org
ViewVC Help
Powered by ViewVC 1.1.26