diff options
Diffstat (limited to 'doc/src/FAQ/FAQ_DEV.html')
| -rw-r--r-- | doc/src/FAQ/FAQ_DEV.html | 76 |
1 files changed, 40 insertions, 36 deletions
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 @@ <H1>Developer's Frequently Asked Questions (FAQ) for PostgreSQL</H1> - <P>Last updated: Thu Jan 4 16:00:00 EST 2007</P> + <P>Last updated: Mon Mar 19 12:52:30 EDT 2007</P> <P>Current maintainer: Bruce Momjian (<A href= "mailto:bruce@momjian.us">bruce@momjian.us</A>)<BR> @@ -55,8 +55,8 @@ assistance?<BR> <A href="#item1.18">1.18</A>) How do I get involved in PostgreSQL web site development?<BR> - <A href="#item1.19">1.19</A>) What is the timeline for the next major - PostgreSQL release?<BR> + <A href="#item1.19">1.19</A>) Why haven't you replaced CVS with SVN, Git, + Monotone, VSS, <insert your favorite SCM system here>? <H2>Technical Questions</H2> @@ -120,10 +120,13 @@ <P>Some developers use compilers from other software vendors with mixed results.</P> - <P>Developers who are regularly rebuilding the source often pass - the --enable-depend flag to <I>configure</I>. The result is that - when you make a modification to a C header file, all files depend - upon that file are also rebuilt.</P> + <P>Developers who regularly rebuild the source often pass the + --enable-depend flag to <I>configure</I>. The result is that when you + make a modification to a C header file, all files depend upon that + file are also rebuilt.</P> + + <P><I>src/Makefile.custom</I> can be used to set environment variables, + like <I>CUSTOM_COPT</I>, that are used for every compile. <H3 id="item1.3">1.3) What areas need work?</H3> 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.)</li> - <li>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</li> + <li>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.</li> <li>Confirm that your changes can pass the regression tests. If your changes are port specific, please list the ports you have tested it on.</li> - <li>Provide an implementation overview, preferably in code comments. - Following the surrounding code commenting style is usually a good - approach.</li> + <li>If you are adding a new feature, confirm that it has been tested + thoroughly. Try to test the feature in all conceivable + scenarios.</li> <li>New feature patches should also be accompanied by documentation patches. If you need help checking the SQL standard, see <a href= "#item1.16">1.16</a>.</li> - <li>If you are adding a new feature, confirm that it has been tested - thoroughly. Try to test the feature in all conceivable - scenarios.</li> + <li>Provide an implementation overview, preferably in code comments. + Following the surrounding code commenting style is usually a good + approach.</li> <li>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 <A href= "http://gborg.postgresql.org/project/pgweb/projdisplay.php">http://gborg.postgresql.org/project/pgweb/projdisplay.php</A> , the code for the next version of the website is under the - "portal" module. + "portal" module.</P> + + <H3 id="item1.19">1.19) Why haven't you replaced CVS with SVN, Git, + Monotone, VSS, <insert your favorite SCMS here>?</H3> + + <P>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:</P> + + <ul> + <li>Run natively on all of our <a href="http://www.postgresql.org/docs/current/interactive/supported-platforms.html">supported platforms</a>.</li> + <li>Integrate into the <a href="http://pgbuildfarm.org/">Buildfarm</a>.</li> + <li>Import our entire CVS Repository while preserving complete history.</li> + <li>Allow for anonymous checkouts.</li> + </ul> + + <P>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.</P> + <H2>Technical Questions</H2> @@ -995,24 +1017,6 @@ requires a compile with <I>-DLINUX_PROFILE</I> for proper profiling.</P> - <H3 id="item2.9">2.9) What is the timeline for the next major - PostgreSQL release?<BR> - - <P>The development schedule for the 8.3 release is:</P> - <DL> - <DD>March 1, 2007</DD> - <DT>Initial community review of all major feature patches</DT> - <DD>April 1, 2007</DD> - <DT>Feature freeze, all patches must be submitted for review and application</DT> - <DD>mid-May, 2007</DD> - <DT>All patches applied, beta testing begins</DT> - <DD>July, 2007</DD> - <DT>Release of 8.3.0</DT> - </DL> - - <P>Patches that appear after appropriate dates are typically - not applied but held for the next major release.</P> - </BODY> </HTML> |