Please log in to subscribe to updates for this article
Last updated at Tue Feb 19 15:26, by zegenie
Introduction ⇑ topWe provide the source code in a Git repository, of which the URL is below:
You can retrieve the source code without a github account, and our git page http://github.com/thebuggenie/thebuggenie also allows you to download the code, look through the commit history log and more.
Git branches ⇑ topWe do our development in different git branches. Each git branch has a specific purpose, described below.
Master ⇑ topThe master branch is unstable
The master branch is where the next non-bugfix release development goes on. The next non-bugfix release can be a 3.x release, 4.0, 5.0, etc., but is generally unstable. You can use this if you want to track the ongoing development of new features and rewrites, but do not use the master branch on production servers. Releases never happen from the master branch, but from one of the release branches.
Release branches ⇑ topThere are a number of release branches, representing the ongoing bugfix development of each point release. The release branches are considered generally stable, but may contain bugs. All new releases (3.2.4, 3.2.5, etc) happen from a release branch.
branch-32 - TBG 3.2.x development, 3.2.x tags branch-31 - TBG 3.1.x development, 3.1.x tags
As soon as a new point release (3.x, 4.x etc) is released, a new branch will be created for this release, and its initial release and all continuing development happening on that version will occur in its release branch. The main development will continue in the master branch.