Add steps for typical patch.

doc/FAQ_DEV

@@ -1,7 +1,7 @@
 
           Developer's Frequently Asked Questions (FAQ) for PostgreSQL
                                        
-   Last updated: Mon Feb 25 15:29:28 EST 2002
+   Last updated: Tue Apr 16 22:10:03 EDT 2002
    
    Current maintainer: Bruce Momjian (pgman@candle.pha.pa.us)
    
@@ -96,7 +96,7 @@
    
   1.2) How do I add a feature or fix a bug?
   
-   The source code is over 250,000 lines. Many problems/features are
+   The source code is over 350,000 lines. Many fixes/features are
    isolated to one specific area of the code. Others require knowledge of
    much of the source. If you are confused about where to start, ask the
    hackers list, and they will be glad to assess the complexity and give
@@ -111,6 +111,15 @@
    facilities in the source, for performance reasons and for simplicity.
    Often a review of existing code doing similar things is helpful.
    
+   The usual process for source additions is:
+     * Review the TODO list.
+     * Discuss hackers the desirability of the fix/feature.
+     * How should it behave in complex circumstances?
+     * How should it be implemented?
+     * Submit the patch to the patches list.
+     * Answer email questions.
+     * Wait for the patch to be applied.
+       
   1.3) How do I download/update the current source tree?
   
    There are several ways to obtain the source tree. Occasional

doc/src/FAQ/FAQ_DEV.html

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