https://sourceforge.net/p/postgres-xc/xc-wiki/Release_Policy/Recent changes to Release_PolicyenFri, 27 Jun 2014 02:32:33 -0000https://sourceforge.net/p/postgres-xc/xc-wiki/Release_Policy/<div class="markdown_content"><p>&lt;gallery&gt; &lt;/gallery&gt;This document describes the release policy of Postgres-XC. This policy is respected from version 0.9.5. </p> <div class="toc"> <ul> <li><a href="#about-code-base">About code base</a></li> <li><a href="#versioning">Versioning</a></li> <li><a href="#release-process-in-git">Release process in GIT</a></li> <li><a href="#tarball-name">Tarball name</a></li> <li><a href="#merge-policy-with-postgresql">Merge policy with PostgreSQL</a></li> </ul> </div> <h2 id="about-code-base">About code base</h2> <p>In GIT repository, Postgres-XC master branch is aligned with PostgreSQL code up to the latest intersection of PostgreSQL master branch and X_X_STABLE branches (determined with git merge-base). As PostgreSQL stable branches are created more or less at each beta2 release once a year, Postgres-XC master branch is realigned once a year with PostgreSQL master branch. This allows to make releases of Postgres-XC by including code commits of latest PostgreSQL stable branch and having a stable version. </p> <h2 id="versioning">Versioning</h2> <p>Each major release of Postgres-XC is numbered 0.9.5, 0.9.6, etc. by incrementing the latest digit number. Minor releases are numbered 0.9.X.X and then 1.X.X for versions from 1.0. </p> <p>A minor release is made respecting a 3-month cycle. Minor releases just contain the latest commits of PostgreSQL stable branch release depending on the stable branch is forked on and Postgres-XC maintenance fixes. For example, release 0.9.5 used this number as major release number, then minor releases are numbered 0.9.5.1, 0.9.5.2, etc. by incrementing the latest digit number. </p> <h2 id="release-process-in-git">Release process in GIT</h2> <p>At a new release, a new branch called REL0_9_X_STABLE for 0.9.X versions and REL1_X_STABLE for 1.X versions is created. This new branch contains the latest Postgres-XC development and a merge of the latest PostgreSQL stable branch where Postgres-XC master branch is forked on. All the commits of stable branch are included at the time of Postgres-XC release to include a maximum of fixes. </p> <p>Then when a release minor or major is made, a tag is created. </p> <p>Then following format is respected depending on if release is minor or major, on if release is numbered more or less than 1.0. </p> <ul> <li>XC0_9_Y_PG8_X for major release 0.9.Y up to 1.0 based on PostgreSQL 8.X </li> <li>XC0_9_Y_Z_PG8_X for minor releases 0.9.Y.Z up to 1.0 based on PostgreSQL 8.X </li> <li>XC0_9_Y_PG9_X for major release 0.9.Y up to 1.0 based on PostgreSQL 9.X </li> <li>XC0_9_Y_Z_PG9_X for minor releases 0.9.Y.Z up to 1.0 based on PostgreSQL 9.X </li> <li>XC1_Y_PG9_X for major releases 1.Y from 1.0 based on PostgreSQL 9.X </li> <li>XC1_Y_Z_PG9_X for minor releases 1.Y.Z from 1.0 based on PostgreSQL 9.X </li> </ul> <p>This system permits to keep a trace on versions of PostgreSQL Postgres-XC is based on. </p> <h2 id="tarball-name">Tarball name</h2> <p>A release of Postgres-XC has a tarball name respecting the following convention: </p> <ul> <li>For release X.Y.Z, tarball name is postgres-xc.X.Y.Z.tar.gz </li> <li>RPM, SRPM packages or spec files share the same grammar, postgres-xc.X.Y.Z.spec. </li> </ul> <p>RPM specifications files use the same grammar. Caution: This grammar is not respected until Postgres-XC 0.9.6. </p> <h2 id="merge-policy-with-postgresql">Merge policy with PostgreSQL</h2> <p><img src="./attachment/PG-XC_Release_Policy_Diagram.png" /> </p></div>Koichi SuzukiFri, 27 Jun 2014 02:32:33 -0000https://sourceforge.netd0ab1f9059af16d7ce0535054fea3f486a88a306