On Montag, 21. Juni 2021, 17:01:45 CEST Michael Kromer wrote:

...

...

The big question is, what should this repository name be?

People need to understand that they can use it on openSUSE Leap 15.3 or on any SUSE SLE 15 SP3 installation.

Do you have any suggestions? My suggestion is to keep it simple. I like reference to Codestream 15.

I second that opinion.

My proposals: - "scr" e.g. "SUSE-compatible repository" - "iscr" e.g. "Inter-SUSE-compatible repository" - "disr" e.g. "Distribution-branch independent SUSE/Software repository"

pick one. :p

The problem I see is that people won't understand that they can use eg. "scr_15.3" repository instead of openSUSE_Leap_15.3 when they look at places like this one: http://download.opensuse.org/repositories/openSUSE:/Tools/ -- Adrian Schroeter Build Infrastructure Project Manager SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany (HRB 247165, AG München), Geschäftsführer: Felix Imendörffer

Hey, On 21.06.21 17:07, Adrian Schröter wrote:

On Montag, 21. Juni 2021, 17:01:45 CEST Michael Kromer wrote:

...

...

...

The big question is, what should this repository name be?

People need to understand that they can use it on openSUSE Leap 15.3 or on any SUSE SLE 15 SP3 installation.

Do you have any suggestions? My suggestion is to keep it simple. I like reference to Codestream 15.

I second that opinion.

My proposals: - "scr" e.g. "SUSE-compatible repository" - "iscr" e.g. "Inter-SUSE-compatible repository" - "disr" e.g. "Distribution-branch independent SUSE/Software repository"

pick one. :p

The problem I see is that people won't understand that they can use eg. "scr_15.3" repository instead of openSUSE_Leap_15.3 when they look at places like this one:

http://download.opensuse.org/repositories/openSUSE:/Tools/

Maybe determining if something is a variant of $CODE_STREAM by the name of the repository is not such a good idea? We can determine this inside OBS in some other way (relationship probably) and use speaking repository names like - SUSE_SLE_15_SP3 - SLE_15_SP3_Backports - openSUSE_Leap_15.3 depending on what the people chose? No need need for "consumers" of repositories to understand some new concept. Henne -- Henne Vogelsang http://www.opensuse.org Everybody has a plan, until they get hit. - Mike Tyson

...

So, in near future OBS will change it's interface and allow basically only to select one repository for "Code 15-3". You can decide to include Backports or Leap packages on top of SLE 15 SP3 as build and install dependencies, but no matter how you configure it as OBS user, the resulting repository name should have the same name.

The big question is, what should this repository name be?

Just make it short.

openSUSE_Leap_15.3 and friends always make me cringe. I always manually named my repos "Factory", "TW" and "Leap_15.2" etc. but it's additional hassle, especially as you cannot use "zypper ar obs:///..." easily with them.

What about just naming it

        15.3

...

People need to understand that they can use it on openSUSE Leap 15.3 or on any SUSE SLE 15 SP3 installation.

Everyone out there calls that beast SLES15.3 anyway, so it would fit naturally.

very good point, however I wouldn't use 15.3 alone, you might at some point end up with collisions with some other distro (yes, there is still quite some room, but never forget the factor of time, and OBS is quite around now) Then how about just simply: SUSE_15.3

Stefan Seyfried composed on 2021-06-21 17:45 (UTC+0200):

Michael Kromer wrote:

...

Then how about just simply:

...

SUSE_15.3

Not so simple....

Also good and still short enough. Or we go the other way: openSUSE_Leap_15.3_or_SLE_15_SP3_Backports_or_SUSE_SLE_15_SP3_or_whatever_is_related_to_SLES15_SP3

Where does the fascination developers have with underscores and dots come from? Would anyone not know what it meant if it was SUSE153? -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata

On Mon 2021-06-28, Jan Engelhardt wrote:

...

Would anyone not know what it meant if it was SUSE153? Yes there is a problem. Example: Our gcc package used to be called "gcc33", and lo and behold, gcc went to increment its major version numbers by a factor of 10. We are now already at gcc11.

That could be address by adding a dot, i.e. SUSE15.3? Though, realistically, even if SUSE/openSUSE did one release per month, going from 15 to 153 would take us more than a decade. ;-) Gerald

On 28.06.21 21:16, Gerald Pfeifer wrote:

On Mon 2021-06-28, Jan Engelhardt wrote:

...

...

Would anyone not know what it meant if it was SUSE153? Yes there is a problem. Example: Our gcc package used to be called "gcc33", and lo and behold, gcc went to increment its major version numbers by a factor of 10. We are now already at gcc11.

That could be address by adding a dot, i.e. SUSE15.3?

Though, realistically, even if SUSE/openSUSE did one release per month, going from 15 to 153 would take us more than a decade. ;-)

Told you so. https://lists.opensuse.org/archives/list/factory@lists.opensuse.org/message/... Or, to phrase it less politely: Leap 15.x was a braindead idea IMNSHO from the beginning. -- Stefan Seyfried "For a successful technology, reality must take precedence over public relations, for nature cannot be fooled." -- Richard Feynman

I did not want to be the one mentioning :-) On Mon, 2021-06-21 at 11:20 -0400, Neal Gompa wrote:

On Mon, Jun 21, 2021 at 7:34 AM Adrian Schröter wrote:

...

Hi,

I like to discuss the upcomming single common name for repositories for "Code 15-3".

Given that we use the Jump concept now with Leap 15.3, it makes no sense that we offer by default

SUSE_SLE_15_SP3 SLE_15_SP3_Backports openSUSE_Leap_15.3

repositories in parallel for each OBS project anymore. The content should be identical and it contradicts the purpose of having a binary compatible base.

So, in near future OBS will change it's interface and allow basically only to select one repository for "Code 15-3". You can decide to include Backports or Leap packages on top of SLE 15 SP3 as build and install dependencies, but no matter how you configure it as OBS user, the resulting repository name should have the same name.

The big question is, what should this repository name be?

People need to understand that they can use it on openSUSE Leap 15.3 or on any SUSE SLE 15 SP3 installation.

Do you have any suggestions?

I'm going to throw out the "crazy" suggestion: SUSE Linux 15.3

I personally track things in my personal tracker as SUSE Linux versions and tag things as "openSUSE" or "SLE" depending on what I have to interface with.

On Tue 2021-06-22, Stefan Seyfried wrote:

...

I'm going to throw out the "crazy" suggestion: SUSE Linux 15.3 I'd drop the "Linux" word in there.

Short is beautiful.

Unless SUSE starts to also build and ship other operating systems, "Linux" is just redundant,

Hmm, at one point SUSE Manager is set to reach version 15, even if at the current version trajectory that might be decades (plural) out. :-) And there's openSUSE Kubic (which alas doesn't use regular version numbers at this point I believe). And openSUSE MicroOS which describes itself as "Micro Service OS built by the openSUSE community. I do agree that short is beautiful. Just "openSUSE $VERSION" or "SUSE $VERSION" may be too general. Gerald

On Tue, Jun 22, 2021 at 1:06 PM Stefan Seyfried wrote:

On 22.06.21 18:18, Gerald Pfeifer wrote:

...

On Tue 2021-06-22, Stefan Seyfried wrote:

...

...

I'm going to throw out the "crazy" suggestion: SUSE Linux 15.3 I'd drop the "Linux" word in there.

Short is beautiful.

Unless SUSE starts to also build and ship other operating systems, "Linux" is just redundant,

Hmm, at one point SUSE Manager is set to reach version 15, even if at the current version trajectory that might be decades (plural) out. :-)

Is SUSE Manager a project/product you build against in OBS? Or is it just a package? (Maybe an overcomplicated set of packages, fortunately I did not have to look at it for many years :-P)

It's a project with a bunch of packages and weird configs of its own.

...

And there's openSUSE Kubic (which alas doesn't use regular version numbers at this point I believe).

Is this a project/project you build against in OBS? Or "just" a compilation of SUSE_15.3/Factory/Tumbleweed/whatever packages plus some glue / configuration?

It is a project for SUSE, the openSUSE version is integrated with Factory (mostly).

...

And openSUSE MicroOS which describes itself as "Micro Service OS built by the openSUSE community.

Is this a project/project you build against in OBS? Or "just" a compilation of SUSE_15.3/Factory/Tumbleweed/whatever packages plus some glue / configuration?

It is a project for SUSE, the openSUSE version is integrated with Factory (mostly).

...

I do agree that short is beautiful.

Just "openSUSE $VERSION" or "SUSE $VERSION" may be too general.

I still vote for just $VERSION :-P

These other projects just have to find non-conflicting $VERSION patterns ;-)

Hah... -- 真実はいつも一つ！/ Always, there's only one truth!

On Tue, Jun 22, 2021 at 12:56 PM Gerald Pfeifer wrote:

On Tue 2021-06-22, Stefan Seyfried wrote:

...

...

I'm going to throw out the "crazy" suggestion: SUSE Linux 15.3 I'd drop the "Linux" word in there.

Short is beautiful.

Unless SUSE starts to also build and ship other operating systems, "Linux" is just redundant,

Hmm, at one point SUSE Manager is set to reach version 15, even if at the current version trajectory that might be decades (plural) out. :-)

And there's openSUSE Kubic (which alas doesn't use regular version numbers at this point I believe).

And openSUSE MicroOS which describes itself as "Micro Service OS built by the openSUSE community.

I do agree that short is beautiful.

Just "openSUSE $VERSION" or "SUSE $VERSION" may be too general.

SUSE Linux $VERSION (or in OBS-speak: SUSE:Linux:$VERSION) is my proposal. :) -- 真実はいつも一つ！/ Always, there's only one truth!

Dne úterý 22. června 2021 9:10:35 CEST, Adrian Schröter napsal(a):

Also the entire purpose of the Jump project was to have an identical base of SLE and openSUSE. IMHO it is important to make this also visible here for all users.

Fool-proof openSUSE_SLE_15.3 ? -- Vojtěch Zeisek https://trapa.cz/ Komunita openSUSE GNU/Linuxu Community of the openSUSE GNU/Linux https://www.opensuse.org/

On 22.06.21 08:38, Axel Braun wrote:

Having an openSUSE-hat on it should *of course* be called openSUSE_Leap_15.3 -

Please not, this pattern was plain wrong from the beginning IMVHO. These are build service repo "tags" / URL components. Make them short. The UI can show whatever it wants, no matter how long. -- Stefan Seyfried "For a successful technology, reality must take precedence over public relations, for nature cannot be fooled." -- Richard Feynman

_15.3 was choosen as the winner yesterday as that had the most votes