low-hanging-fruit
on Github.git pull --rebase
to get latest changes from upstreamgit checkout -b feature/<feature_name>
git checkout -b bug/<bug_number>
Resolves Issue #1127
Partially Resolves Issue #9873
master
- Development for the next minor stable release.portland
- Development for the next major release.dev/3.1.x
dev/3.3.x
dev/4.1.x
dev/4.3.x
etc
stable/0.8.x
stable/1.0.x
stable/1.2.x
stable/2.0.x
stable/2.2.x
stable/3.0.x
stable/3.2.x
etc
<Major>.<Minor>.<Bugfix>
1.x.x
version of Cement will need to be completely rewritten for the 2.x.x
versions of Cement.2.2.x
, the only updates should be bug and/or security related. At times, minor features may be introduced during a 'bugfix' release but that should not happen often.even == stable
, and odd == development
scheme. Therefore, the current version in git will always end in an 'odd number'. For example, if the current stable version is 2.0.18
, then the version in stable/2.0.x
would be 2.0.19
. That said, the master
branch might then be 2.1.1
which is the first version of the next minor release. Bugfixes would get applied to both branches, however feature updates would only be applied to master
. The next stable release would then be 2.2.0
and a new git branch of stable/2.2.x
will be created.portland
branch is always very forward looking, and will contain significant (and likely broken) code changes. It should never be used for anything other than development and testing.Cement X.YY.Z Release Tracker
with the following: