git pull --rebaseto get latest changes from upstream
git 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.
1.x.xversion of Cement will need to be completely rewritten for the
2.x.xversions 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 == developmentscheme. 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
2.0.19. That said, the
masterbranch might then be
2.1.1which 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.0and a new git branch of
stable/2.2.xwill be created.
portlandbranch 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 Trackerwith the following: