Source code repository

From pgpool Wiki
Jump to: navigation, search

Pgpool source code repository is managed by PostgreSQL's git repository.

About pgpool-II source code management

pgpool-II version policy

We release "major version" each year, which is mostly backward compatible with the previous release, Exceptions to this rule are listed in the release notes when sometimes some existing feature is dropped, depreciated or a change that brings certain incompatibilities with the older versions. The versions are numbered in the form of A.B.C where A.B is the major version number while C represents the minor version of a release. Currently pgpool-II versions are represented by A == 3 i.e 3.B.C where 3.B represents the major version number, So current releases of pgpool-II is also sometimes referred as "3. X series".

To absolutely identify version number, specifying the "minor version number (part C of A.B.C version string)" is important. This minor version is incremented for the bug fix release, which is roughly released every month. For example pgpool-II 3.5.0 represents the first release of pgpool-II 3.5 series and 3.5.1 is the second minor (bug fix) release of the same. Unlike major versions the new minor release is guaranteed to be 100% backward compatible with the previous minor release.

pgpool-II branch policy

pgpool-II source code is managed by git and hosted at PostgreSQL's git repository. Currently we have several branches to track each development tree. The under development branch (the candidate for next major version) is master branch.

Each time new major version is released, we create a branch to maintain the previous major version. We call them as "stable branches". Currently we have following stable branches.

pgpool-II release support policy

The pgpool-II project aims to fully support a major release for five years. (if you need longer support, please contact SRA OSS, Inc.).

After a release falls out of full support, we may (at our committers' discretion) continue to apply further critical fixes to the source code, on a best-effort basis. No formal releases or binary packages will be produced by the project, but the updated source code will be available from our source code control system.

This policy will be followed on a best-effort basis. In extreme cases it may not be possible to support a release for the planned lifetime; for example if a serious bug is found that cannot be resolved in a given major version without significant risk to the stability of the code or loss of application compatibility. In such cases, early retirement of a major version may be required.

Version First release date EOL date
3.6 2016/11 2021/11
3.5 2016/1 2021/1
3.4 2014/11 2019/11
3.3 2013/7 2018/7
3.2 2012/8 2017/8
3.1 2011/9 2016/9