From 90e4b46998dcd16b3e38dd1923d0f4e7a88ae2b2 Mon Sep 17 00:00:00 2001 From: Bruce Momjian Date: Thu, 19 Apr 2007 03:07:32 +0000 Subject: Stamp releases 8.2.4, 8.1.9, 8.0.13, 7.4.17, 7.3.19. --- doc/src/FAQ/FAQ_DEV.html | 76 +++++++++++++++++++++++++----------------------- 1 file changed, 40 insertions(+), 36 deletions(-) (limited to 'doc/src/FAQ/FAQ_DEV.html') diff --git a/doc/src/FAQ/FAQ_DEV.html b/doc/src/FAQ/FAQ_DEV.html index 0cdffa28722..43ff0c8447f 100644 --- a/doc/src/FAQ/FAQ_DEV.html +++ b/doc/src/FAQ/FAQ_DEV.html @@ -13,7 +13,7 @@

Developer's Frequently Asked Questions (FAQ) for PostgreSQL

-

Last updated: Thu Jan 4 16:00:00 EST 2007

+

Last updated: Mon Mar 19 12:52:30 EDT 2007

Current maintainer: Bruce Momjian (bruce@momjian.us)
@@ -55,8 +55,8 @@ 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?
+ 1.19) Why haven't you replaced CVS with SVN, Git, + Monotone, VSS, <insert your favorite SCM system here>?

Technical Questions

@@ -120,10 +120,13 @@

Some developers use compilers from other software vendors with mixed results.

-

Developers who are regularly rebuilding the source often pass - the --enable-depend flag to configure. The result is that - when you make a modification to a C header file, all files depend - upon that file are also rebuilt.

+

Developers who regularly rebuild the source often pass the + --enable-depend flag to configure. The result is that when you + make a modification to a C header file, all files depend upon that + file are also rebuilt.

+ +

src/Makefile.custom can be used to set environment variables, + like CUSTOM_COPT, that are used for every compile.

1.3) What areas need work?

Outstanding features are detailed in the TODO list. This is located @@ -185,26 +188,26 @@ preferable if the file changes are single-line changes and do not rely on surrounding lines.) -
  • PostgreSQL is licensed under a BSD license, so any submissions must - conform to the BSD license to be included. If you use code that is - available under some other license that is BSD compatible (eg. public - domain) please note that code in your email submission
    • +
  • PostgreSQL is licensed under a BSD license. By posting a patch + to the public PostgreSQL mailling lists, you are giving the PostgreSQL + Global Development Group the non-revokable right to distribute your + patch under the BSD license.
  • Confirm that your changes can pass the regression tests. If your changes are port specific, please list the ports you have tested it on.
    • -
  • Provide an implementation overview, preferably in code comments. - Following the surrounding code commenting style is usually a good - approach.
    • +
  • If you are adding a new feature, confirm that it has been tested + thoroughly. Try to test the feature in all conceivable + scenarios.
  • New feature patches should also be accompanied by documentation patches. If you need help checking the SQL standard, see 1.16.
    • -
  • If you are adding a new feature, confirm that it has been tested - thoroughly. Try to test the feature in all conceivable - scenarios.
    • +
  • Provide an implementation overview, preferably in code comments. + Following the surrounding code commenting style is usually a good + approach.
  • If it is a performance patch, please provide confirming test results to show the benefit of your patch. It is OK to post patches @@ -705,7 +708,26 @@ the source code is available at http://gborg.postgresql.org/project/pgweb/projdisplay.php , the code for the next version of the website is under the - "portal" module. + "portal" module.

    + +

    1.19) Why haven't you replaced CVS with SVN, Git, + Monotone, VSS, <insert your favorite SCMS here>?

    + +

    Currently the core developers see no SCMS that will provide + enough benefit to outwiegh the pain involved in moving to a new + SCMS. Typical problems that must be addressed by any new SCMS include:

    + + + +

    Currently there is no intention for switching to a new SCMS until at least the + end of the 8.4 development cycle sometime in late 2008. For more information + please refer to the mailing list archives.

    +

    Technical Questions

    @@ -995,24 +1017,6 @@ 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.

    - -- cgit v1.2.3