Thanks for the quick response. Migrating from v2.2 to v2.4 in our production system sounds scary. Is there any kind of patch or hotfix that solves this problem and can be applied on v2.2.0 or v2.2.1?
↧
Thanks for the quick response. Migrating from v2.2 to v2.4 in our production system sounds scary. Is there any kind of patch or hotfix that solves this problem and can be applied on v2.2.0 or v2.2.1?