Development

How to contribute to the Pgpool-II project

Pgpool-II is an open source project and the contribution style follows the way PostgreSQL does except that we don't have CF application.

• Source code is managed by the git repository.

We maintain 5-6 stable branches (see https://pgpool.net/mediawiki/index.php/EOL_information for more details). The under development branch is always the master branch. We don't add new features to stable branches. New features should be added to the master branch.

• New feature proposals should be discussed on the pgpool-hackers mailing list

The proposal should include reason, back ground, architecture design, and the most important thing: why this is good for users (and developers). The proposal need not to be completed. Just throwing an idea to start a discussion is welcome.

Actual code should be proposed as a patch to the master branch. A patch does not need to be included in the first, or early discussions.

The committable patch should include not only complete code, but documentation (SGML format) and possibly tests (under src/test).

Once the patch is verified by committers, a committer will commit/push the patch to the master branch.

Projects already done

• pgpool-II 4.2 development

• pgpool-II 4.1 development

• pgpool-II 4.0 development

• pgpool-II 3.7 development

• pgpool-II 3.6 development

• Watchdog feature enhancement

• pgpool-II 3.5 development

• pgpool-II 3.5 watchdog test

Buildfarm

The Pgpool-II project runs the regression test everyday. The result is mailed to buildfarm mailing list. Also the regression test results including errors can be downloaded here. The data is kept up to last 7 days.