Magento 2 Development Processes
These are the development processes we use for building and maintaining Magento 2 sites:
- Deployment
- For on-premise deployments, we use the Magento 2 Capistrano Gem. See this article written by Erik Hansen about Deploying Magento 2 Using Capistrano
- For each site we maintain, we have a standard set of features that should be tested on stage before deployments are approved to production. We have another checklist for things to test after a production deployment.
- Code management
- We used a subset of Gitflow practices for deployment:
- All development is done in a “feature/<FEATURE NAME>” branch. Features are then merged into the develop branch. The develop branch is deployed to stage for testing/UAT. The develop branch is then merged into master for deployment to production.
- For time-sensitive bug fixes, we use hotfix branches
- All commit messages are prefixed with a reference to the source Jira task
- We follow these guidelines for commit messages
- We used a subset of Gitflow practices for deployment:
- Coding standards
- We follow the Magento 2 coding standards
- We use PhpStorm for authoring code editing and have created code styles to enforce the Magento 2 coding standards