Release Procedure
Official vtigercrm releases will be made available only by the process documented on this page. Other release scenarios, such as variants of the codebase for community testing should be maintained as repository branches, documented in RepositoryBranching.
Release Procedure Objectives
The release procedure is documented and adhered to for several reasons, including:
- Can be undertaken by any developer so authorized by the vtigercrm team
- Is repeatable across releases
- Has a predictable output of release files
- Packagers can rely on predictable download URLs
- Emergency releases are no more or less work than regular releases
- Community and packagers know where to look for release notification
Release Procedure Output
The release process always results in exactly three files and one subversion tag, as described in Canonical Name Forms (ReleaseNaming)
- Unix Archive Name: vtigercrm-x.y.z[-][suffix#].tar.gz
- Windows Archive Name: vtigercrm-x.y.z[-][suffix#].zip
- Windows Installer Name: vtigercrm-x.y.z[-][suffix#].exe
- Subversion Tag Name: /vtigercrm/tags/x.y.z[-][suffix#]
Release Procedure Steps
- Prepare one repository branch (which can include vtigercrm/trunk) to be configured exactly as the release files.
- Use svn export to create a filesystem copy of this branch containing no .svn control information.
- Test configuration of your exported codebase, unaltered, to evaluate your satisfaction
- Make necessary changes with svn commits, do not post-process svn exported codebase.
- Repeat from step 1, until no packaging defects can be found.
- (to be continued...)
