33 |
NOTE: PEGs should not be accepted as long as there are |
NOTE: PEGs should not be accepted as long as there are |
34 |
unresolved issues. |
unresolved issues. |
35 |
|
|
36 |
|
- Do we need the Scope and Type fields? |
37 |
|
|
38 |
Names |
Names |
39 |
----- |
----- |
40 |
|
|
75 |
Comma-separated list of author names or handles |
Comma-separated list of author names or handles |
76 |
Date |
Date |
77 |
CVS date tag |
CVS date tag |
78 |
|
|
79 |
Revision |
Revision |
80 |
CVS revision tag |
CVS revision tag |
81 |
|
|
82 |
Status |
Status |
83 |
The PEG status |
The PEG status |
84 |
|
|
85 |
Date-Created |
Date-Created |
86 |
The date when the PEG was created, for sorting |
The date when the PEG was created, for sorting |
87 |
|
|
88 |
|
Scope |
89 |
|
How large the effects of this PEG are: |
90 |
|
|
91 |
|
Major |
92 |
|
Most code needs a touchup |
93 |
|
Minor |
94 |
|
limited |
95 |
|
Trivial |
96 |
|
few places need to be changed in a trivial way |
97 |
|
Cosmetic |
98 |
|
name changes and the like |
99 |
|
|
100 |
|
Type |
101 |
|
The type of the PEG |
102 |
|
|
103 |
|
Architecture |
104 |
|
Large-scale architecture |
105 |
|
Feature |
106 |
|
A new feature |
107 |
|
Interface |
108 |
|
An adjustment of one or more interfaces |
109 |
|
Implementation |
110 |
|
An adjustment of how an implementation does something |
111 |
|
|
112 |
Low-level Format |
Low-level Format |
113 |
---------------- |
---------------- |
114 |
|
|