In the course of development, teams are continually adding features, and sometimes need to make major architectural changes. During these activities the application is not releasable, although it will still pass the commit stage of continuous integration. Usually, before release, teams will stop developing new functionality and enter a stabilization phase during which only bugfixing takes place. When the application is released, a release branch is created in version control, and new development begins again on trunk. However, this process generally results in weeks or months between releases. The aim of continuous delivery is for the application to always be in a releasable state. How can we achieve this?
One approach is ...
- Chapter 13. Managing Components and Dependencies
- from Continuous Delivery: Reliable Software Releases through Build, Test, and Deployment Automation, Video Enhanced Edition
- Publisher: Addison-Wesley Professional
- Released: July 2010
How to keep an application releasable during changes.
Share this highlighthttp://www.safaribooksonline.com/a/continuous-delivery-reliable/568136/