Am Samstag, 22. April 2017, 13:37:48 CEST schrieb Richard Brown:

[...] openSUSE Leap 15 [...] SUSE have decided that their next version of SLE will be 15, not 13. [...] 45 was also considered, as were some frankly hilarious ideas that made me worry about my own sanity and that of my fellow contributors.

What exactly is so bad about openSUSE Leap 45? Reminds me of 45 rpm. :)

[...] Packagers should be able to look forward to an easier time of things as a result of this change. We intend to deprecate the 0%{leap_version} macro and simplify the current complex nest of suse_version and sle_versions that can make it very frustrating to build packages appropriately for Tumbleweed, Leap and SLE. [...]

Cool! I like the idea. Gruß Jan -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org To contact the owner, email: opensuse-project+owner@opensuse.org

22.04.2017 14:37, Richard Brown пишет:

Hi all,

On behalf of the openSUSE Board and Leap Release Management I am pleased to announce the next version of openSUSE Leap after 42.3 will be:

openSUSE Leap 15

What version will be after openSUSE Leap 41?

As with Leap 42.x, minor releases are expected annually for at least 3 years, so you can expect a Leap 15.1 to follow, then 15.2 and onwards.

Obviously this is quite a dramatic change from the current version number of 42.x, so I will explain what justifies this change in some detail below.

First, some history. When we started openSUSE Leap, the version number was an issue that needed addressing. openSUSE at that time was at 13.2, but SUSE Linux Enterprise (SLE) was at 12 and heading towards 12 SP1.

As the main unique selling point of Leap compared to every other distribution is the fact it is based on SLE sources. We wanted to reflect that in the version number. This was particularly important when you consider that a major version in SLE really means something ("major architectural changes from the last version are introduced here") whereas minor versions/service packs have a very different message ("easy to upgrade to, no major workflow breaking changes"). Leap follows a similar philosophy, so we wanted a versioning scheme to reflect SLEs.

But openSUSE had already had versions starting with 12, so we couldn't sync up with SLE. This is where 42.x came from. It gave us the opportunity to establish a relationship with SLE versions (SLE Version + 30 = Leap Version), reflect the major/minor nature of Leap releases, and avoid clashes with version numbers we'd already used. The choice of 42 doubled as a humorous nod to hitchhikers guide to the galaxy and the first version numbers of SuSE Linux and YaST (4.2 and 0.42 respectively).

The plan was therefore for the next version of Leap to be 43 with it's release aligned with SLE 13, followed by Leap 43.1 (with SLE 13 SP1), Leap 43.2 (w. SP2), etc

However, like all good plans, things change.

SUSE have decided that their next version of SLE will be 15, not 13.

Upon learning of SUSE's plans the Board and Leap release team have been considering our options. This included ignoring the changes to SLE and releasing Leap 43 as planned, at the cost of the link between SLE versions and Leap versions. 45 was also considered, as were some frankly hilarious ideas that made me worry about my own sanity and that of my fellow contributors.

After considering the pros and cons of all the options however, the decision has been that Leap 15 will be our next version.

SUSE's decision to skip SLE 13 and 14 gave us a perfect opportunity to sync up with SLE versions like we always wanted to originally with Leap. It's an opportunity we will not be able to take so easily a few years from now if we continued with Leaps current versioning.

There are only a few packages in our distribution that reference the 42.x versioning, and they should be easily handled as part of a zypper dup, so we are not concerned about this decision impacting users upgrading.

We are aware that this decision could be a minor annoyance for users of Leap with configuration management tools like saltstack and puppet, but the long term opportunity to simplify such configuration (by being able to treat SLE and Leap similarly) outweighed our desire to avoid a 'one-time' effort for people currently handling the overly complicated situation caused by Leap being at 42.x and SLE being at 12 SPx.

Packagers should be able to look forward to an easier time of things as a result of this change. We intend to deprecate the 0%{leap_version} macro and simplify the current complex nest of suse_version and sle_versions that can make it very frustrating to build packages appropriately for Tumbleweed, Leap and SLE.

0%{suse_version} should continue to be available as a simple indicator of the major version of Leap & SLE for packagers (eg, 0%{suse_version} == 1500 is the expected value for SLE 15 and Leap 15 and all of their minor versions/service packs).

0%{sle_version} should remain as a more precise indicator when packagers need to handle specific versions of Leap and SLE (eg. 0%{sle_version} == 150000 is the expected value for SLE 15 & Leap 15, with 150100 being the expected value for SLE 15 SP1 & Leap 15.1)

0%{is_opensuse} will continue for those times when packagers need to distinguish between Leap and SLE even though they will now more closely share their versions.

The above examples and what the future suse_version number will be for Tumbleweed is not yet final, so expect to see emails from ludwig in opensuse-factory@opensuse.org when they are set.

Thanks to everyone involved in this so far, I'm looking forward to seeing what we make out of Leap 15, and even though I cross-posted this I would like to ask that any followup conversation is kept to the opensuse-project@opensuse.org thread.

Regards,

Richard Brown on behalf of the openSUSE Board

-- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org To contact the owner, email: opensuse-project+owner@opensuse.org

On 2017-04-22T13:37:48, Richard Brown wrote: Having just paid for a locksmith's emergency fee because I locked myself out on Sunday morning put me into the perfect mood for commenting on this! ;-) This seems ill-advised, even more so then the utterly crazy SLE numbering change that triggered it. (And they at least have the advantage of being able to blame it on non-technical folks.) Version numbers that are not strictly monotonous ought to be taken out and shot. The joke with 42, yes, silly, but I could get behind it, because everyone loves 42. You could have gone with 50, or 51 (maintains that Leap uses "funny numbers" (area 51), happens to be the reverse of 15, *and* meet the sensible requirement of, you know, being larger than your previous version number). I know one shouldn't test for version numbers but feature presence, but ... Seriously? Are you *trying* to alienate and confuse users on purpose? On the plus side, I hope it'll drive even more folks to Tumbleweed which does have a nice and tidy incremental scheme and none of this madness. Oh, also?

Thanks to everyone involved in this so far, I'm looking forward to seeing what we make out of Leap 15, and even though I cross-posted this I would like to ask that any followup conversation is kept to the opensuse-project@opensuse.org thread.

Conversation implies dialogue. Apparently, the best one can do here is rant and whine about a decision that has already been reached. That works for a corporate context, but making such a publicly visible decision that exposes the community to ridicule and confusion behind closed doors? You might as well have announced to switch the default DE to Unity. And now I'll pretend to be a grown-up with a life. But the eye-rolling was getting to painful and needed an outlet. Regards, Lars -- SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) "Experience is the name everyone gives to their mistakes." -- Oscar Wilde -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org To contact the owner, email: opensuse-project+owner@opensuse.org

Hi, On Sat, Apr 22, 2017 at 2:37 PM, Richard Brown wrote:

Hi all,

On behalf of the openSUSE Board and Leap Release Management I am pleased to announce the next version of openSUSE Leap after 42.3 will be:

openSUSE Leap 15

What is the reason for not moving to 15 as an internal version number, e.g. in the RPM macros and using 43.x in version numbers that are communicated to end users? As a packager, I need to be up to date with various RPM building techniques, macros and best practices, one more is not going to make a lot of difference. As an end user, I would appreciate strictly incrementing version numbers, as it gives me a clear sense which version is the most recent one. Robert -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org To contact the owner, email: opensuse-project+owner@opensuse.org