undefined | Better HN

0 pointsviccuad5y ago0 comments

  Debian Unstable     -> Testing       -> Stable -> Oldstable -> Oldstable with LTS
  Fedora              -> Centos Stream -> RHEL   -> RHEL with LTS
  Opensuse Tumbleweed -> Leap          -> SLES   -> SLES with LTS

Debian supports upgrades with major versions, and doesn't bump package major versions between minor versions. SLE/Leap don't support upgrades between major versions, and bump package major versions between minor versions.

0 comments

pferde5y ago

It is untrue that SLES does not support upgrades between major versions: https://documentation.suse.com/sles/15-SP2/single-html/SLES-...

It is, however, true that SLES is less conservative than e.g. RHEL when it comes to bumping software versions between their minor releases (service packs). I remember that they switched from 2.6 to 3.0 kernels sometimes in SLES10 days. Fun stuff.

pelasaco5y ago

openSUSE however doesn't support it https://en.opensuse.org/SDB:System_upgrade#Supported_scenari...

pferde5y ago

The link you posted only states that the upgrade is not supported for 64-bit ARM, and that 32-bit (x86) system cannot be upgraded to Leap. It doesn't say upgrade in general is not.

merb5y ago

tumbleweed does or rather, tumbleweed does not have point releases. in my eyes tumbleweed is way better for cloud, IoT and desktops, as soon as you use transactional-update

P.S. I'm fallen in love with it.

rombert5y ago

Note that the gap between Leap and SLE will become quite small after Leap 15.3, with binary packages for SLE being reused for Leap.

It's interesting that while RH/IBM are moving away from the 'community rebuild' model SUSE are moving close.

https://en.opensuse.org/Portal:Leap/FAQ/ClosingTheLeapGap

pelasaco5y ago

> Opensuse Tumbleweed -> Leap -> SLES -> SLES with LTS

Almost right :)

Leap is the fixed point release, based on SLE. SLE is rebased on Tumbleweed every 3-4 years.

viccuadOP5y ago

Well, my intent was to roughly chart the supported timeframe and expectations of each, not the flow of code through them. That SLE gets rebased from Tumbleweed directly every 3-4 years justs showcases my second point from before: SLE bumps major versions of packages between minor SLE versions.

j / k navigate · click thread line to collapse

0 pointsviccuad5y ago0 comments

  Debian Unstable     -> Testing       -> Stable -> Oldstable -> Oldstable with LTS
  Fedora              -> Centos Stream -> RHEL   -> RHEL with LTS
  Opensuse Tumbleweed -> Leap          -> SLES   -> SLES with LTS

0 comments

pferde5y ago

It is untrue that SLES does not support upgrades between major versions: https://documentation.suse.com/sles/15-SP2/single-html/SLES-...

pelasaco5y ago

openSUSE however doesn't support it https://en.opensuse.org/SDB:System_upgrade#Supported_scenari...

pferde5y ago

The link you posted only states that the upgrade is not supported for 64-bit ARM, and that 32-bit (x86) system cannot be upgraded to Leap. It doesn't say upgrade in general is not.

merb5y ago

tumbleweed does or rather, tumbleweed does not have point releases. in my eyes tumbleweed is way better for cloud, IoT and desktops, as soon as you use transactional-update

P.S. I'm fallen in love with it.

rombert5y ago

Note that the gap between Leap and SLE will become quite small after Leap 15.3, with binary packages for SLE being reused for Leap.

It's interesting that while RH/IBM are moving away from the 'community rebuild' model SUSE are moving close.

https://en.opensuse.org/Portal:Leap/FAQ/ClosingTheLeapGap

pelasaco5y ago

> Opensuse Tumbleweed -> Leap -> SLES -> SLES with LTS

Almost right :)

Leap is the fixed point release, based on SLE. SLE is rebased on Tumbleweed every 3-4 years.

viccuadOP5y ago

j / k navigate · click thread line to collapse