Results 1 to 5 of 5

Thread: Upgrade policy of Plasma 5 in Leap 42.x

  1. #1

    Default Upgrade policy of Plasma 5 in Leap 42.x

    Hello mates.

    What is the upgrade policy of Plasma 5 in Leap 42.1 and successive?. In SLES 11 used the same major version of KDE 4.5x and I will afraid to do the same with SLED 12. As Leap 42.x is a clone of SLED 12.x, I will fear that the same thing happens in Leap 42.x. Now Plasma 5 uses version 5.1x, this version will be used throughout the development of Leap 42.x

    I don't want to use the repository KDE Frameworks 5.

    Here it says:
    Every minor version of openSUSE Leap users can expect a new KDE and GNOME, but today is all about openSUSE Leap 42.1, so if you are tired of a brown desktop, try a green
    one.
    That's true?.

    Greetings.

  2. #2

    Default Re: Upgrade policy of Plasma 5 in Leap 42.x

    Well, I understand than graphical desktops don't belong to the basis, so they can have a normal time of release. ¿Is it?

    Cheers!

  3. #3

    Default Re: Upgrade policy of Plasma 5 in Leap 42.x

    Quote Originally Posted by DiabloRojo View Post
    What is the upgrade policy of Plasma 5 in Leap 42.1 and successive?.
    Plasma 5 comes from Factory, so Leap 42.2 will get the latest Plasma 5 that's available in Factory at release time (in about a year).

    For 42.1 I am not sure.
    Like with every other release before, you normally only get security and bugfix updates (although exceptions are possible).
    Plasma 5.4.3 has been submitted and will be released as update soon.

    But I don't know if the upcoming 5.5.0 (and further releases) will be released as update too

    In SLES 11 used the same major version of KDE 4.5x and I will afraid to do the same with SLED 12.
    AFAIK SLES 11 and SLED 12 did/do not contain KDE at all.

    As Leap 42.x is a clone of SLED 12.x, I will fear that the same thing happens in Leap 42.x.
    Leap 42.1 is *not* a "clone" of SLED 12.x.
    Some base packages come from SLE 12, and are maintained by SUSE.

    Now Plasma 5 uses version 5.1x, this version will be used throughout the development of Leap 42.x
    Leap 42.1 comes with Plasma 5.4.2, this will be updated to 5.4.3 soon.

    You probably mixed that up with the Frameworks (the libraries), which are at version 5.15.0 in Leap 42.1. Here an update to 5.16.0 has been submitted too, again I cannot tell you if/how many future updates will be officially released for Leap 42.1.

    I don't want to use the repository KDE Frameworks 5.
    If you always want to have the latest version, you'll probably have to.
    Just like it was with *every* openSUSE release before.

    Or use Tumbleweed.

    Here it says:


    That's true?.
    Why should that not be true?

    It has been true for every openSUSE release before.

    Also GNOME has been taken from Factory (because the version in SLE is rather old) so is/was also the latest version (ok, 3.18 has been released since), and this will be the same for 42.2.

    Quote Originally Posted by karlggest View Post
    Well, I understand than graphical desktops don't belong to the basis, so they can have a normal time of release. ¿Is it?
    Actually, the corresponding maintainers have to decide whether a package is taken from SLE or Factory, or even is developed in a dedicated branch for Leap (like the kernel and Xorg, e.g.).

    But yes, the desktops (KDE and GNOME at least) are taken from Factory as mentioned.
    Last edited by wolfi323; 21-Nov-2015 at 04:52.

  4. #4

    Default Re: Upgrade policy of Plasma 5 in Leap 42.x

    Hi.

    What would happen it a core component provided by SLE is frozen during the whole life cycle of a Leap version but a desktop require a newer version of that component? Three years is a long time in terms of software development. I suppose that it would prevent the update of the desktop in later service packs.

    I don't really know it this is a plausible scenario because I haven't yet read what are those core components provided by SLE.

    Greetings.

  5. #5

    Default Re: Upgrade policy of Plasma 5 in Leap 42.x

    Quote Originally Posted by jcsl View Post
    What would happen it a core component provided by SLE is frozen during the whole life cycle of a Leap version but a desktop require a newer version of that component? Three years is a long time in terms of software development. I suppose that it would prevent the update of the desktop in later service packs.
    Service Packs are allowed to do version upgrades.

    But if a component coming from SLE is too old, there are e.g. those options for the next Leap 42.x release:
    - upgrade the package in SLE (in the service pack), has to be done by the SUSE maintainer of course
    - patch the necessary stuff in, i.e. backport the missing things
    - take the corresponding package from Factory instead, or create a separate branch for Leap with a suitable version (happened with Xorg e.g.)

    I don't really know it this is a plausible scenario because I haven't yet read what are those core components provided by SLE.
    Here's a list of what comes from where in 42.1:
    https://build.opensuse.org/package/v...p.yml?expand=1

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •