This is my first message here, so hello to everyone . I’m an user of Debian and Ubuntu and, in general terms, I’m very happy with them. However, I feel that the 2 years period to upgrade between LTS versions may be too long for a workstation. And that the 6 months period between non-LTS versions may be too short. So the 1 year period between releases of OpenSUSE Leap appeals to me.
But I would like to know what is upgraded in minor versions of OpenSUSE Leap in comparison with major versions. I’ve read that major versions are aligned with the releases of SUSE Linux Enterprise, whereas minor ones are aligned with the releases of SUSE Linux Enterprise Service Pack. However, when I’ve checked the differences between the version 42.1 and 42.2, I’ve seen that some components that are part of the “core” of SLE have been upgraded, whereas others have remained the same. For example, the kernel has been upgraded, but PostgreSQL remains in version 9.4.
Is there a document that shows which packages will be upgraded and which won’t? Or is it arbitrary between releases? For example, Will the PostgreSQL version remain the same until the next major version?
The default versions of applications in the standard repository (OSS) can be considered rock solid stable (or should be) but should be updated regularly, incorporating new features and fixes.
You can get a later version, perhaps even the latest version of any application (like PostgreSQL) compiled from the project’s sources in another repository.
So, for instance you can get PostgreSQL 9.6.1 (almost the very latest as of today, 9.6.2 was just released 1 week ago) version by searching for it on software.opensuse.org
Thanks for your answer . Before writing my post, I read that article and also this one: openSUSE:Roadmap. However, none of them says which packages are upgraded in minor releases.
Thanks for your answer too . But I still am not clear about what packages from the OSS repository are upgraded to major versions when a minor version of Leap is released. For example, VIM and PostgreSQL remain the same in versions 42.1 and 42.2, but the packages of KDE Plasma 5 and the kernel were upgraded in version 42.2.
What criteria do the maintainers apply? Could it be said that, excepting the kernel, only the components that are NOT INCLUDED in SLE are upgraded to major versions in each minor release of Leap? That would correspond with what I’ve seen, but I’m not sure.
I also found those packages during my search. But I wasn’t sure about who were their maintainers and whether they came from reliable people. I guess that it depends on each repository, and that I’ve to check it manually before adding it to my list. Just as we have to do with PPAs in Kubuntu. Am I right? Thanks .
Hi, welcome to openSUSE and to the Forums! Not clear to me if you like “more stability” or “the latest stable packages”…
Anyway with openSUSE the choice is yours to a large extent. I’m not involved in release development, just an “active” user here, so I cannot add to the documents you already read.
But maybe a few comments about the “repo ecosystem” here in real life might help.
Want “more stability”? Just stick to a (minor) release until it is EOL, that is some 18 months from release. The OSS and NON-OSS repos there still carry the versions “as released”. Then the OSS-update and NON-OSS-update repos carry each and every version of packeges released since the System release date and you may choose just what release you like among them (or not updating at all).
Want “the latest stable packages” (or even “unstable” sometimes)? Upgrade to the latest “minor” Leap version and add extra repos to your liking.
“Not all repos are created equal”, as you already noticed. Some have a reliability comparable to the “official” OSS repos though.
Examples include the Kernel:/Stable repo, the X11: repo, several repos dedicated to the major desktop environments, the Packman repo for non-OSS codecs and the like.
Repos named home:<username> carry the reputation of their respective owners: some come from the original developers or packagers themselves, some are from “ordinary” users experimenting with their systems.
Ask here on the Forums if unsure (and look for the reputation of those who answer…).
Want “The bleeding Edge”? Switch to Tumbleweed, openSUSE’s rolling release, but expect glitches here and there from time to time (not suitable to you, if I understood correctly).
As an example, I use a “plain” Leap 42.2 for ordinary day-to-day work (Gnome version, rock-solid so far) and a “test” 42.2 with added Kernel:/Stable and X11:/Xorg repos to play with the latest graphics stack (quite stable so far, excluding the hiccups I created myself…).
If unsure, ask here on the Forums, lots of knowledgeable volunteers are ready to help
Thank you for your welcome, and for such interesting information .
I have always had an internal struggle with both strategies. I usually install LTS versions of Debian and Ubuntu. But, during their use, I usually have to upgrade this or that package because I want or need certain feature urgently. I’m a developer, so it’s not rare that that situation often occurs in my computer. In my servers is less frequent, but it also happens sometimes. In the workstations of my relatives, that rarely occurs (luckily; because I maintain them ).
To take advantage of my acquired knowledge, I try to use the same distribution and version in all that computers. Then, I upgrade some packages (or compile from source code) as needed.
That’s why I’ve paid attention to OpenSUSE Leap, because its release cycle seems to be a good balance between both “worlds”: stability during 1 year and, after that, new stable versions to enjoy for the next year. Obviously, that can’t avoid that you need a newer version of certain package during the current release. But I hope that that situation is less frequent, because there are some upgrades that can wait until the end of the cycle (for example, Inskape).
Using unofficial repositories to complement the official ones is what I’m doing with Debian and Ubuntu, so it doesn’t sound bad. But I wanted to reduce that dependency on “external” stuff.
Your idea of using two distinct installations, each one with its own configuration, also appeals to me. Maybe more. In my case I would need to use both distributions simultaneously. So I guess that I should use a virtual machine and try to get used to a workflow using 2 machines. I tried once and it was tiring to switch from one to another but… Maybe I can find a solution for that. It would be interesting to use Leap as host and Tumbleweed as guest .
Thank you! It has been a very interesting reading. Assuming that I’ve read it right, that confirms that b]the packages that are part of the core of SLE, aren’t upgraded between minor releases. The kernel comes from the development repository, so it has its own evolution.