MicrosoftThis might not be the right post to put this in, but this is an example of one of our concerns with the upcoming transition from Exchange 2019 to Exchange SE. That transition is leaving us very little time to prepare, when in the past we would typically wait until at least one service pack had been released and a majority of the issue had been resolved so that we could be confident to put the newest version into production. We are a large organization and not having proper time to prepare for the next release of Exchange is going to cause major impacts to our organization and we are also concerned the product may have unresolved major issues that will not have the proper time to be identified.
MicrosoftWe hear this concern but - IMO, there is nuance here. CU15 will release this CY; that will give you lots of time to get to "Exchange SE equivalent" testing in your organization. Indeed, there are still SUs that we will release, but we release SUs when needed; there could be an SU immediately after Exchange SE RTM, for example (and before CU1).
The issue here is that we still release updates (usually SUs) with regressions. This is a problem that we have done a lot of work on and have added to variety of testing scenarios and improvements. But issues still happen. We realize that "release quality" (particularly for SUs) is something that we must do better on.
