*** FAQ_DEV.html.old 2006-10-17 11:03:19.000000000 +0300
--- FAQ_DEV.html 2006-10-17 11:17:32.000000000 +0300
***************
*** 13,19 ****
Developer's Frequently Asked Questions (FAQ) for
PostgreSQL
! Last updated: Mon Oct 16 15:24:36 EDT 2006
Current maintainer: Bruce Momjian (bruce@momjian.us)
--- 13,19 ----
Developer's Frequently Asked Questions (FAQ) for
PostgreSQL
! Last updated: Tue Oct 17 11:15:12 EDT 2006
Current maintainer: Bruce Momjian (bruce@momjian.us)
***************
*** 21,27 ****
The most recent version of this document can be viewed at http://www.postgresql.org/files/documentation/faqs/FAQ_DEV.html.
--- 21,27 ----
The most recent version of this document can be viewed at http://www.postgresql.org/docs/faqs.FAQ_DEV.html.
***************
*** 83,89 ****
development?
Download the code and have a look around. See 1.7.
Subscribe to and read the pgsql-hackers
--- 83,89 ----
development?
Download the code and have a look around. See 1.7.
Subscribe to and read the pgsql-hackers
***************
*** 132,138 ****
You can learn more about these features by consulting the
archives, the SQL standards and the recommend texts (see 1.10).
1.4) What do I do after choosing an item to
work on?
--- 132,138 ----
You can learn more about these features by consulting the
archives, the SQL standards and the recommend texts (see 1.10).
1.4) What do I do after choosing an item to
work on?
***************
*** 165,171 ****
- Ensure that your patch is generated against the most recent version
of the code, which for developers is CVS HEAD. For more on branches in
! PostgreSQL, see 1.15.
- Try to make your patch as readable as possible by following the
project's code-layout conventions. This makes it easier for the
--- 165,171 ----
- Ensure that your patch is generated against the most recent version
of the code, which for developers is CVS HEAD. For more on branches in
! PostgreSQL, see 1.15.
- Try to make your patch as readable as possible by following the
project's code-layout conventions. This makes it easier for the
***************
*** 196,202 ****
- 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
--- 196,202 ----
- 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
***************
*** 701,711 ****
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. You will also find code for the "techdocs"
! website if you would like to contribute to that. A temporary todo
! list for current website development issues is available at http://xzilla.postgresql.org/todo
Technical Questions
--- 701,707 ----
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.
Technical Questions