|
13 | 13 | <H1>Developer's Frequently Asked Questions (FAQ) for |
14 | 14 | PostgreSQL</H1> |
15 | 15 |
|
16 | | -<P>Last updated:Mon Oct 16 15:24:36 EDT 2006</P> |
| 16 | +<P>Last updated:Tue Oct17 08:54:26 EDT 2006</P> |
17 | 17 |
|
18 | 18 | <P>Current maintainer: Bruce Momjian (<Ahref= |
19 | 19 | "mailto:bruce@momjian.us">bruce@momjian.us</A>)<BR> |
20 | 20 | </P> |
21 | 21 |
|
22 | 22 | <P>The most recent version of this document can be viewed at<A |
23 | 23 | href= |
24 | | - "http://www.postgresql.org/files/documentation/faqs/FAQ_DEV.html">http://www.postgresql.org/files/documentation/faqs/FAQ_DEV.html</A>.</P> |
| 24 | + "http://www.postgresql.org/docs/faqs.FAQ_DEV.html">http://www.postgresql.org/docs/faqs.FAQ_DEV.html</A>.</P> |
25 | 25 | <HR> |
26 | 26 | <BR> |
27 | 27 |
|
@@ -83,7 +83,7 @@ <H3 id="item1.1">1.1) How do I get involved in PostgreSQL |
83 | 83 | development?</H3> |
84 | 84 |
|
85 | 85 | <P>Download the code and have a look around. See<Ahref= |
86 | | - "#1.7">1.7</A>.</P> |
| 86 | + "#item1.7">1.7</A>.</P> |
87 | 87 |
|
88 | 88 | <P>Subscribe to and read the<Ahref= |
89 | 89 | "http://archives.postgresql.org/pgsql-hackers">pgsql-hackers</A> |
@@ -132,7 +132,7 @@ <H3 id="item1.3">1.3) What areas need work?</H3> |
132 | 132 |
|
133 | 133 | <P>You can learn more about these features by consulting the |
134 | 134 | archives, the SQL standards and the recommend texts (see<Ahref= |
135 | | - "#1.10">1.10</A>).</P> |
| 135 | + "#item1.10">1.10</A>).</P> |
136 | 136 |
|
137 | 137 | <H3id="item1.4">1.4) What do I do after choosing an item to |
138 | 138 | work on?</H3> |
@@ -165,7 +165,7 @@ <H3 id="item1.5">1.5) I've developed a patch, what next?</H3> |
165 | 165 | <ol> |
166 | 166 | <li>Ensure that your patch is generated against the most recent version |
167 | 167 | of the code, which for developers is CVS HEAD. For more on branches in |
168 | | - PostgreSQL, see<ahref="#1.15">1.15</a>.</li> |
| 168 | + PostgreSQL, see<ahref="#item1.15">1.15</a>.</li> |
169 | 169 |
|
170 | 170 | <li>Try to make your patch as readable as possible by following the |
171 | 171 | project's code-layout conventions. This makes it easier for the |
@@ -196,7 +196,7 @@ <H3 id="item1.5">1.5) I've developed a patch, what next?</H3> |
196 | 196 |
|
197 | 197 | <li>New feature patches should also be accompanied by documentation |
198 | 198 | patches. If you need help checking the SQL standard, see<ahref= |
199 | | - "#1.16">1.16</a>.</li> |
| 199 | + "#item1.16">1.16</a>.</li> |
200 | 200 |
|
201 | 201 | <li>If you are adding a new feature, confirm that it has been tested |
202 | 202 | thoroughly. Try to test the feature in all conceivable |
@@ -701,11 +701,7 @@ <H3 id="item1.18">1.18) How do I get involved in PostgreSQL |
701 | 701 | the source code is available at<Ahref= |
702 | 702 | "http://gborg.postgresql.org/project/pgweb/projdisplay.php">http://gborg.postgresql.org/project/pgweb/projdisplay.php</A> |
703 | 703 | , the code for the next version of the website is under the |
704 | | - "portal" module. You will also find code for the "techdocs" |
705 | | - website if you would like to contribute to that. A temporary todo |
706 | | - list for current website development issues is available at<A |
707 | | -href= |
708 | | - "http://xzilla.postgresql.org/todo">http://xzilla.postgresql.org/todo</A></P> |
| 704 | + "portal" module. |
709 | 705 |
|
710 | 706 | <H2>Technical Questions</H2> |
711 | 707 |
|
|