Use the bundle manifest editor and the resource editors to edit the contents of a CICS® bundle and to increase its version number. Then deploy the new version of the CICS bundle, or an application bundle that includes it, to your CICS regions.
You manage changes to CICS bundles by using version control. You must apply a versioning policy to your CICS bundles and management bundles to deploy and manage updates in the CICS environment.
Each bundle has an ID and version information to uniquely identify it. The version uses major, minor, and micro identifiers, so you can indicate the significance of a change and manage the dependencies between bundles. This concept is called semantic versioning and is taken from the OSGi Alliance. Although it focuses on Java™ packages, you can use the same principles to apply to bundles in general.
Semantic versioning provides a way to increment the major, minor, or micro parts of a version to indicate the compatibility or incompatibility with previous versions of a bundle. For example, bug fixes might increment the micro part of the version, compatible changes increment the minor part of the version, and incompatible changes increment the major part of the version. For more information about semantic versioning, see Semantic Versioning Technical Whitepaper.
You can specify that a CICS bundle has changed by increasing the version number in the bundle manifest file. If the CICS bundle is referenced by an application bundle, you must also increase the version of the application bundle for redeployment.