zciklacekic wrote:So why is this patch is not a public one?
Hotfixes are always private (to limit the scope, as they receive limited testing for the purpose of fast release). Once we have collected a number of hotfixes, validated them on some affected customers, and support tells us they need a patch because support load is too high on some specific issues existing hotfixes are addressing, we release the patch. We are trying to release patches as rare as possible, as no one likes to upgrade too often due to all the validation/upgrade testing required.
However, patches are always public - they contain all hotfixes to date, and pass full QC cycle (takes a few weeks) to make sure there is no unforeseen collateral damage on some product functionality due to specific hotfix, or due to how those multiple hotfixes the patch consists of play together. This is what allows to make them publicly available (remember, anything we make public goes to over 40'000 customers - we have to be 200% sure before we can make anything public).
zciklacekic wrote:Do you want them to force to buy subscription& support?
No, absolutely not. I guess you are missing the fact that customers without active subscription have simply no rights to upgrade to the new versions anyway. Everyone who upgrades to the new version HAS to have active subscription to be able to upgrade, meaning they can reach out to our support and get any hotfix they need for the new version.