Change to Release
What is a change?
A change is a problem that need to be resolved. Even if the problem has a workaround, it can still be useful to move the problem to change, especially if a fix will be developed in the future. Changes only occur when a problem has been fully identified (root cause, symptoms and impact). Changes are the fix to a problem, this involves development to fix the problem. Problems don’t involve development directly, they are indirectly fixed through the change request (RFC - request for change).
What is a release?
A release is the planning and preparation for the public release of a service. This can be an update or the initial release. In our case, we will use it mostly for updates. This stage is for two parts;
The release plan
The plan of release is the plan for the roll out of the update. This can involve timing, app store, update log, informing client/end users.
Testing
Before the update can be released, it's best to check if the initial incident(s) has been rectified. This is why it's important to document the incidents in problems. If the testing fails, the development team can take another look and the testing restarts. This may also involve a reevaluation of the release plan, usually not.
How a change becomes a release
Once a change has been handled by the development team, the release can be made. It's at this point the testing can begin and the release plan can be put into action if testing is positive.