Just found today that official download page https://get.opensuse.org/leap/16.0/ points to 1/2 year old images which is not good - considering both security and need to upgrade lot of packages after each install.
Alpha version testers should know the difference between an alpha ISO release and a GA version. Wolfheri is completely correct. There wonât be any new ISO for Leap 16.0
Thatâs quite some basics. For Alphas and Betas you have many refreshed ISOâs until final release. And the final release (GA) is published on day x. After that, the updates are only available via repos and not via new ISOs.
Some linux distributions had to relase a refreshed ISO of a fixed release due to some issues. As example a serious issue was only discovered after final release which made it necessary to publish new ISOs. Or the release schedule was missed for over a year and the devs decided to publish a new ISO so that you donât have to update everything after installation.
Iâm sorry for confusion: Iâm not talking about rolling (Slowroll) or bleeding edge (Tumbleweed) updates:
Iâm talking about installation images with latest Fixes and Security updates (these are actually already published to stock repo-oss and repo-non-oss in case of Leap 16).
At least up-to-date Cloud images would be fine as is the case of:
The problem is exaggerated in case of Cloud image - because normally it is converted to read-only template and every VM created from such template need to install bunch of updates again and again.
It is generally not possible to manually update such template VM, because it requires post clean-up - remove of all instance specific data.
Having up-to-date cloud images (as does Debian and Fedora) would really help to save bandwidth and speed up instance createion.
There always only was the release ISO. All updates (security and recommended) came via the Update repos).
But, somewhere during the lifetime of some 15.x version (sorry, not knowing exactly which one) the idea to have from time to time a re-mastered ISO was implemented. This was done to avoid very large updates to be done direct after an installation e.g. half a year after release. I have no idea if this is still (to be) done with 16.0. In any case, it is was/is a bit of an ad hoc extra service when the stack of updates increased considerable and not a standard feature of the leap release/update policy.
Yes, I know. But that does not change the possibility of a re-mastered ISO. If the re-mastered ISO includes to contents of the Update repos (< 16.0), or the now contents of the altered main repos (16.0) results in the same: an installation with a smaller update action direct after it. And again, I do not know what âtheyâ are going to do with 16.0 in this respect.