This white paper discusses the various branch methodologies and merge scenarios used in development, and the importance of using the same methodology for both application and database development.
Using mixed methodologies between application development and database development creates unnecessary challenges, adding both time and complexity to the already-rushed, already-complex development lifecycle.
In today’s climate, the ability to automate development, and merge and deploy changes rapidly – without introducing serious mistakes – relies on using the same branch methodology for database development as you use for application development.
- Application Development Branches
- How Database Development Fits into the Picture
- Database Branching and Baseline-Aware Merging
- Getting the Best Database Deployment Outcomes