Zorin updates roll out in a trickle effect. They update the main server, then the mirrors (your local servers and any clones of main, will be updated in time).
So everyone receives the update at different times. Some may just be getting to the update prior to the point release. All will eventually see this update.
The only people who are notified directly, and only if there are major changes, feature additions or major bug fixes, are pro users. Otherwise, the blog is too share with the community.
Download iso's are not the first to receive the update. Usually the community gets it, then the iso follows shortly after.
The upgrader has a place holder, which allows the ZorinGroup to quickly add the finished product. Many application developers do this, as it informs users as well as gets the "easy" portion out of the way, allowing more time to focus on what will be released. I would not use the upgrader as an indicator of impending release.
While this is good news, it's somewhat disheartening that this precedes the lite and education variants.
This should help community members realize the complexity of what they do. It also shows their dedication to quality over quantity, as they want core, their flagship, to be a stable experience. Then these fixes can be incorporated in lite and education. Which should make their release less problematic.
@Omnimaxus if you could run your system through some testing...
- built in applications,
- sleep and returning (double lock screen? ) after some time (hour or two)
- as well as some load testing (something graphically complex [video game/ movie stream]) while other applications are running (firefox, chrome, libre office)
- and any third party application you have installed (discord, zoom or other software not provided by the Zorin repos)...
- even brighteness changes,
- audio,
- Bluetooth?
This will give us an idea of what all was changed and how it is performing.
These are the things reported as having issues. While you don't have everyone's hardware, the info is still useful to gage the changes and performance.
Whatever you do test, if you decide to, keep track of the test (what you were testing) and the outcome (what the final result was).
Example:
-
Testing lock screen return after two hour sleep.
-
Result was single login screen, without issue of keyboard or mouse.
