1.1.14+Strategies+for+managing+releases+and+updates

=__**1.1.4 Describe strategies for managing releases and updates.**__=

One should be aware of a variety of ways in which updates and patches are made available and deployed. Performance issues related to the inability to install updates may hinder end-users and reduce compatibility between systems in geographically diverse locations.

__**Managing updates:**__
 * Things to consider:**
 * Is the update required?
 * Was the update tested enough?
 * Will the program still need updating soon after the release of this update?
 * Consequences for lousy updates:**
 * Loss of customers due to malfunction through the update.
 * Resource required to roll back the update or make a new one.
 * Customers will doubt the skills of the developers.

__**Patching:**__
 * Types:**
 * **Patch in the form of binary executable **instead of a source code,** mostly used in proprietary software. This patch modifies the program executable either by modifying the binary file to include the fixes or replacing it.**
 * **Patch in the form of a source code modifications. Patch consisits of textual differences between two source code files. These types of patches are mostly used for open source programs, where it is also expected for the user to compile the new patch.**
 * **Bigger updates are referred to as "service packs" or as "software updates".**

Created By:D3LTA Last update:10/5/13

Sources: >
 * []
 * []