Hello,
In general, the latest available preview version includes the same content as the following stable release. For example, 21.1.65.1744 [Preview] from January 20 is basically the same version as 21.1.65.1767 [Stable] from January 26. The difference in the build number (the fourth number in the version number, here .1744 and .1767) is because the preview build and the stable build come from different development branches, so when we promote a preview version to stable we get a new build with a higher build number.
We use the first preview build (here 21.1.65.1667) of a new “major” version (here .65) to run our extensive tests for this version and fix the findings before we release it as stable. And usually we also release the preview with these fixes in advance. This is not always the case, though, but in most cases, and depends a bit on the individual scenario. New features and improvements are always the same for one major version in both release channels.
The release notes of the preview channel might be a bit confusing here. On the one hand, fixes for newly introduced issues that only affect the preview do not appear in the stable release notes. This is simply because such test findings never made it into a stable version and as such are not a change to the previous stable version. On the other hand, some entries of one preview major version might appear twice, in the first preview release and in the following preview release(s) of one major version. This is simply for technical reasons.
Regards.
Add comment