The version control system for phpBB3 is subversion. The repository is available at http://code.phpbb.com/svn/phpbb. + +
7.i. Repository Structure
+ +-
+
- trunk
The latest unstable development version with new features etc. Contains the actual board in/trunk/phpBB
+ - branches
Development branches of stable phpBB releases. Copied from/trunk
at the time of release. +-
+
- phpBB3.0
/branches/phpBB-3_0_0/phpBB
Development branch of the stable 3.0 line. Bug fixes are applied here.
+ - phpBB2
/branches/phpBB-2_0_0/phpBB
Old phpBB2 development branch.
+
+ - phpBB3.0
- tags
Released versions. Copies of trunk or the respective branch, made at the time of release. +-
+
/tags/release_3_0_BX
Beta release X of the 3.0 line.
+ /tags/release_3_0_RCX
Release candidate X of the 3.0 line.
+ /tags/release_3_0_X-RCY
Release candidate Y of the stable 3.0.X release.
+ /tags/release_3_0_X
Stable 3.0.X release.
+ /tags/release_2_0_X
Old stable 2.0.X release.
+
+
7.ii. Commit Messages
+ +The commit message should contain a brief explanation of all changes made within the commit. Often identical to the changelog entry. A bug ticket can be referenced by specifying the ticket ID with a hash, e.g. #12345. A reference to another revision should simply be prefixed with r, e.g. r12345.
+ +Junior Developers need to have their patches approved by a development team member first. The commit message must end in a line with the following format:
+ ++Authorised by: developer1[, developer2[, ...]] +