FarCry Community Distro

Owned by Geoff Bowers
Last updated: Sept 24, 2010Version comment
1 min read

FarCry CMS Release

Subversion Structure

You can browse the REL repository root at: https://farcry.jira.com/source/browse/REL

Or via subversion at:
svn checkout https://farcry.jira.com/svn/REL

The root level of the Subversion project follows a standard trunk, branches and tags format. However, each release is managed from a branch of each of these folders.

For example, for the Community Distro the relevant folder structure is as follows:

https://farcry.jira.com/svn/REL
./trunk/community
./branches/community-p600 (maps to the p600 branch of core)
./tags/community-6-0-4 (maps to milestone-6-0-4 version of core)

Each folder in Subversion is a set of externals pointing to a specific version of the relevant code base. Together the externals pull together a distribution according to the distribution policies outlined below.

Distribution Policies

Milestone Releases

Distro milestones are bound to the FarCry Core milestone. FarCry CMS tags are synchronised with FarCry Core.

Maintenance Branches

Distro maintenance release is bound to all the current maintenance branches for the relevant code base. Where no maintenance branches are maintained the distro is bound to trunk.

Bleeding Edge

Distro is bound to the trunk for all code bases.

Release Checklist

Milestone Creation

  • create a tag for the relevant code base
  • release the corresponding version in JIRA Studio; push all open tickets to the next release, and add another version to project
  • export milestone code base, generate zip and upload to Amazon S3
  • generate text based release notes; publish to forum and blog