From the list of changes, I noticed the following:
> Revert "icuuc: Add initial dll."
> Revert "icu: Add stub dll."
In the recent 10.20 release, a number of applications I had previously been using without issue stopped working due to the change they had made to those dlls, and it took a bit of digging for for me to eventually find the solution that I needed to add new overrides for them (disabling one entirely and using the native or built-in version of the other). It's a bit mystifying to me why a breaking regression can slip into a minor release but fixing it not happen until a major release. I understand that this isn't semantic versioning, and I imagine that this is probably a case of them just happening to already have planned a major release next rather than a minor one, but it would be kind of nice if stuff like this could get fixed without having to be blocked on all of the other numerous (and much larger) changes when they're already aware of the problem and have identified the fix.
From the list of changes, I noticed the following:
> Revert "icuuc: Add initial dll."
> Revert "icu: Add stub dll."
In the recent 10.20 release, a number of applications I had previously been using without issue stopped working due to the change they had made to those dlls, and it took a bit of digging for for me to eventually find the solution that I needed to add new overrides for them (disabling one entirely and using the native or built-in version of the other). It's a bit mystifying to me why a breaking regression can slip into a minor release but fixing it not happen until a major release. I understand that this isn't semantic versioning, and I imagine that this is probably a case of them just happening to already have planned a major release next rather than a minor one, but it would be kind of nice if stuff like this could get fixed without having to be blocked on all of the other numerous (and much larger) changes when they're already aware of the problem and have identified the fix.