Stamp release 8.2.1. Update FAQs.

doc/FAQ_DEV

@@ -1,7 +1,7 @@
 
           Developer's Frequently Asked Questions (FAQ) for PostgreSQL
                                        
-   Last updated: Mon Nov 13 23:18:46 EST 2006
+   Last updated: Thu Jan 4 16:00:00 EST 2007
    
    Current maintainer: Bruce Momjian (bruce@momjian.us)
    
@@ -30,6 +30,7 @@ General Questions
    1.16) Where can I get a copy of the SQL standards?
    1.17) Where can I get technical assistance?
    1.18) How do I get involved in PostgreSQL web site development?
+   1.19) What is the timeline for the next major PostgreSQL release?
    
 Technical Questions
 
@@ -99,7 +100,9 @@ General Questions
    both the internal implementation method you plan to use, and any
    user-visible changes (new syntax, etc). For complex patches, it is
    important to get community feeback on your proposal before starting
-   work. Failure to do so might mean your patch is rejected.
+   work. Failure to do so might mean your patch is rejected. If your work
+   is being sponsored by a company, read this article for tips on being
+   more effective.
    
    A web site is maintained for patches awaiting review,
    http://momjian.postgresql.org/cgi-bin/pgpatches, and those that are
@@ -225,7 +228,7 @@ General Questions
     ccsym           find standard defines made by your compiler
      copyright       fixes copyright notices
 
-    entab           converts tabs to spaces, used by pgindent
+    entab           converts spaces to tabs, used by pgindent
     find_static     finds functions that could be made static
     find_typedef    finds typedefs in the source code
     find_badmacros  finds macros that use braces incorrectly
@@ -796,3 +799,24 @@ typedef struct nameData
    pgsql/data directory. The client profile file will be put in the
    client's current directory. Linux requires a compile with
    -DLINUX_PROFILE for proper profiling.
+   
+  2.9) What is the timeline for the next major PostgreSQL release?
+  
+   The development schedule for the 8.3 release is:
+   
+          March 1, 2007
+          
+   Initial community review of all major feature patches
+          April 1, 2007
+          
+   Feature freeze, all patches must be submitted for review and
+          application
+          mid-May, 2007
+          
+   All patches applied, beta testing begins
+          July, 2007
+          
+   Release of 8.3.0
+          
+   Patches that appear after appropriate dates are typically not applied
+   but held for the next major release.