as well as a reference to get up to date with the changes made to the core since the CakePHP 2.x branch. Be sure to read the other pages in this guide for all the new features and API changes. Requirements create a topic branch. The branch you create should be based on the version that your fix/enhancement is for. For example if you are fixing a bug in 3.x you would want to use the master branch as the base base for your branch. If your change is a bug fix for the 2.x release series, you should use the 2.x branch: # fixing a bug on 3.x git fetch upstream git checkout -b ticket-1234 upstream/master # fixing

as well as a reference to get up to date with the changes made to the core since the CakePHP 2.x branch. Be sure to read the other pages in this guide for all the new features and API changes. Requirements create a topic branch. The branch you create should be based on the version that your fix/enhancement is for. For example if you are fixing a bug in 3.x you would want to use the master branch as the base base for your branch. If your change is a bug fix for the 2.x release series, you should use the 2.x branch: # fixing a bug on 3.x git fetch upstream git checkout -b ticket-1234 upstream/master # fixing

create a topic branch. The branch you create should be based on the version that your fix/enhancement is for. For example if you are fixing a bug in 3.x you would want to use the master branch as the base base for your branch. If your change is a bug fix for the 2.x release series, you should use the 2.x branch: # fixing a bug on 3.x git fetch upstream git checkout -b ticket-1234 upstream/master # fixing descriptive name for your branch. Referencing the ticket or feature name is a good convention. Examples include ticket-1234 and feature-awesome. The above will create a local branch based on the upstream

create a topic branch. The branch you create should be based on the version that your fix/enhancement is for. For example if you are fixing a bug in 3.x you would want to use the master branch as the base base for your branch. If your change is a bug fix for the 2.x release series, you should use the 2.x branch: # fixing a bug on 3.x git fetch upstream git checkout -b ticket-1234 upstream/master # fixing descriptive name for your branch. Referencing the ticket or feature name is a good convention. Examples include ticket-1234 and feature-awesome. The above will create a local branch based on the upstream

Shim plugin [https://github.com/dereuromark/cakephp-shim] with the old behavior/generation (4.x branch). FormHelper now sets the default step size to seconds for datetime widgets with a time component create a topic branch. The branch you create should be based on the version that your fix/enhancement is for. For example if you are fixing a bug in 3.x you would want to use the master branch as the base base for your branch. If your change is a bug fix for the 2.x release series, you should use the 2.x branch: # fixing a bug on 3.x git fetch upstream git checkout -b ticket-1234 upstream/master # fixing

markup, a shimmed FormHelper can be found in Shim plugin34 with the old behavior/generation (4.x branch). • FormHelper now sets the default step size to seconds for datetime widgets with a time component create a topic branch. The branch you create should be based on the version that your fix/enhancement is for. For example if you are fixing a bug in 3.x you would want to use the master branch as the base base for your branch. If your change is a bug fix for the 2.x release series, you should use the 2.x branch: # fixing a bug on 3.x git fetch upstream git checkout -b ticket-1234 upstream/master # fixing

create a topic branch. The branch you create should be based on the version that your fix/enhancement is for. For example if you are fixing a bug in 2.3 you would want to use the 2.3 branch as the base for for your branch. If your change is a bug fix for the current stable release, you should use the master branch. This makes merging your changes in later much simpler: # fixing a bug on 2.3 git fetch upstream for your branch, referencing the ticket or feature name is a good convention. e.g. ticket-1234, feature-awesome The above will create a local branch based on the upstream (CakePHP) 2.3 branch. Work on

create a topic branch. The branch you create should be based on the version that your fix/enhancement is for. For example if you are fixing a bug in 2.3 you would want to use the 2.3 branch as the base for for your branch. If your change is a bug fix for the current stable release, you should use the master branch. This makes merging your changes in later much simpler: # fixing a bug on 2.3 git fetch upstream for your branch, referencing the ticket or feature name is a good convention. e.g. ticket- 1234, feature-awesome The above will create a local branch based on the upstream (CakePHP) 2.3 branch. Work on