Difference between revisions of "Source code repository"
| Line 19: | Line 19: | ||
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. | 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. | ||
| − | |||
* [http://git.postgresql.org/gitweb/?p=pgpool2.git;a=shortlog;h=refs/heads/V3_4_STABLE 3.4-stable] | * [http://git.postgresql.org/gitweb/?p=pgpool2.git;a=shortlog;h=refs/heads/V3_4_STABLE 3.4-stable] | ||
* [http://git.postgresql.org/gitweb/?p=pgpool2.git;a=shortlog;h=refs/heads/V3_3_STABLE 3.3-stable] | * [http://git.postgresql.org/gitweb/?p=pgpool2.git;a=shortlog;h=refs/heads/V3_3_STABLE 3.3-stable] | ||
Revision as of 08:59, 5 July 2015
Pgpool source code repository is managed by PostgreSQL's git repository.
- pgpool-II git repository
- pgpoolAdmin git repository
- pgpool-HA git repository
- pgpool-I git repository (legacy version of pgpool. Not maintained anymore)
About pgpool-II source code management
pgpool-II version policy
We releases "major version" each year, which is mostly upper compatible with the previous release, but sometimes drops or changes features, which brings certain incompatibilities with the previous releases. We represent each major version "3.x" at this point. Sometimes we call 3.x as "3.x series".
To absolutely identify version number, specifying "minor version" is required. The second decimal point of the version number represents the "minor version", which is used for bug fixes. Unlike major versions, we guarantee that each minor version is compatible with previous minor version. Every a few month we releases "minor version up". For example 3.5.0 is the first minor version of 3.5 series and 3.5.1 is the next minor version.
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.
