Chapter 3: Basics of Continuous Delivery

1. What we mean by delivering software is that the actual software product has been delivered to the intended user and not just that the software product has been approved by the QA department. In other words the intended users are actually using the software.
2. Deploying software manually is an antipattern as well as manual software configuration.
3. Some benefits of automation when delivering software is team empowerment ( teams feel empowered to make decisions ), error reduction as you eliminate errors that creep up due to manual processes as well as stress reduction.
4. Configuration Management is the process by which all software artifacts that are pertinent to each given project as well as any relationships among the software artifacts are retrieved, stored, identified and modified.
5. Writing descriptive and meaningful commit messages helps developers quickly track the issue that is worked on and helps developers understand the work that you actually did.
6. A deployment pipeline can thought of as the process for getting software that is written by developers into the hands of your users.
7. The deployment should be done the same in each environment so that you get reliably know that it is being tested the same in each environment and avoid possible configuration mismatches.