12
12
< H1 > Developer's Frequently Asked Questions (FAQ) for
13
13
PostgreSQL</ H1 >
14
14
15
- < P > Last updated: Mon Feb 25 15:29:28 EST 2002</ P >
15
+ < P > Last updated: Tue Apr 16 22:10:03 EDT 2002</ P >
16
16
17
17
< P > Current maintainer: Bruce Momjian (< A href =
18
18
"mailto:pgman@candle.pha.pa.us "> pgman@candle.pha.pa.us</ A > )< BR >
@@ -134,7 +134,7 @@ <H3><A name="1.1">1.1</A>) How go I get involved in PostgreSQL
134
134
135
135
< H3 > < A name ="1.2 "> 1.2</ A > ) How do I add a feature or fix a bug?</ H3 >
136
136
137
- < P > The source code is over 250 ,000 lines. Many problems /features
137
+ < P > The source code is over 350 ,000 lines. Many fixes /features
138
138
are isolated to one specific area of the code. Others require
139
139
knowledge of much of the source. If you are confused about where to
140
140
start, ask the hackers list, and they will be glad to assess the
@@ -151,6 +151,16 @@ <H3><A name="1.2">1.2</A>) How do I add a feature or fix a bug?</H3>
151
151
simplicity. Often a review of existing code doing similar things is
152
152
helpful.</ P >
153
153
154
+ < P > The usual process for source additions is:
155
+ < UL >
156
+ < LI > Review the TODO list.</ LI >
157
+ < LI > Discuss hackers the desirability of the fix/feature.</ LI >
158
+ < LI > How should it behave in complex circumstances?</ LI >
159
+ < LI > How should it be implemented?</ LI >
160
+ < LI > Submit the patch to the patches list.</ LI >
161
+ < LI > Answer email questions.</ LI >
162
+ < LI > Wait for the patch to be applied.</ LI >
163
+ </ UL > </ P >
154
164
< H3 > < A name ="1.3 "> 1.3</ A > ) How do I download/update the current source
155
165
tree?</ H3 >
156
166
0 commit comments