All CKZ-Packages of Cloning Tool should be bound with versioning (like the packages in AdminTool).
This would simplify fallback-Szenarios (=> no rebind necessary) and the rollout of a new version (=> packages can be created before activation).
|Who would benefit from this IDEA?||For installation I would prefer this change to simplify fallback and rollout of CloningTool.|
How should it work?
Specify VERSION in source of CKZ-modules (e.g. PTF-level) so during rollout of new maintenance old versions are kept. Maybe also expand customization-dialog and installation-jobs by steps for FREEing of old versions.