-
Notifications
You must be signed in to change notification settings - Fork 8
00. Workflow Summary
VTechWorks sprints last four weeks. New VTechWorks changes will be decided at sprint planning meetings every 4th Monday. Code changes will be committed to the source control system using a modified Gitflow workflow described elsewhere on this wiki.
The main branch for development will be vt_6_x_dev. Use
- feature branches based on vt_6_x_dev to implement new features and changes that require feedback.
- commits directly to vt_6_x_dev for simple configuration changes
Daily standup meetings will be held to discuss progress and issues.
When code on vt_6_x_dev is ready to deploy to the development server, the pre-production server, or the production server, the product manager will move all the commits to be deployed to the appropriate branch and notify the sysadmin that that branch should be deployed.
- Development deployment branch is named vt_6_x_dev_deploy
- Pre-production deployment branch is named vt_6_x_pprd_deploy
- Production deployment branch is named vt_6_x_prod_deploy
Occasionally, there may be a need to deploy hot fixes to production in between releases. A hotfix branch will be created based on the vt_6_x_prod_deploy branch (because the last commit holds the latest production version) and then merged into the vt_6_x_prod_deploy branch for deployment.