[opensuse-project] Re: Name for the new openSUSE release (was: [opensuse-factory] The community)
On 14/04/2020 15.53, Johannes Kastl wrote:
On 14.04.20 at 15:20 Gerald Pfeifer wrote:
As an aside, Jump is an awful name, since it's a way too common of a word in the English language to build any reasonable branding around it.
Isn't Jump more like $JUMP, its actual name to be determined?
We should decide on a sensible name very soon, otherwise Jump will be mentioned in dozens of places already... :-(
I think it is a very bad idea to change names, Yet another Time. -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)
On Tue, Apr 14, 2020 at 03:59:49PM +0200, Carlos E. R. wrote:
On 14/04/2020 15.53, Johannes Kastl wrote:
On 14.04.20 at 15:20 Gerald Pfeifer wrote:
As an aside, Jump is an awful name, since it's a way too common of a word in the English language to build any reasonable branding around it.
Isn't Jump more like $JUMP, its actual name to be determined?
We should decide on a sensible name very soon, otherwise Jump will be mentioned in dozens of places already... :-(
I think it is a very bad idea to change names, Yet another Time.
I think this is not to change name, rather to refer to the SLE based Leap while it exists alongside the Leap as it is built now. I don't really see a problem with Jump as a name for such temporary project. Thanks Michal -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org To contact the owner, email: opensuse-project+owner@opensuse.org
Dne úterý 14. dubna 2020 16:11:20 CEST, Michal Suchánek napsal(a):
We should decide on a sensible name very soon, otherwise Jump will be mentioned in dozens of places already...
I think it is a very bad idea to change names, Yet another Time.
I think this is not to change name, rather to refer to the SLE based Leap while it exists alongside the Leap as it is built now. I don't really see a problem with Jump as a name for such temporary project.
I don't really see any problem in keeping name Leap during the transition phase. There will be "old" Leap 15.1 and "new" 15.2, won't it? So why not to keep Leap name? It's normal that distributions develop, and they don't have to be necessarily renamed. It'd be more natural to do the transition between 15 and 16, but otherwise I don't really see problem in keeping the name. -- Vojtěch Zeisek https://trapa.cz/ Komunita openSUSE GNU/Linuxu Community of the openSUSE GNU/Linux https://www.opensuse.org/
Em ter., 14 de abr. de 2020 às 11:36, Vojtěch Zeisek
Dne úterý 14. dubna 2020 16:11:20 CEST, Michal Suchánek napsal(a):
We should decide on a sensible name very soon, otherwise Jump will be mentioned in dozens of places already...
I think it is a very bad idea to change names, Yet another Time.
I think this is not to change name, rather to refer to the SLE based Leap while it exists alongside the Leap as it is built now. I don't really see a problem with Jump as a name for such temporary project.
I don't really see any problem in keeping name Leap during the transition phase. There will be "old" Leap 15.1 and "new" 15.2, won't it? So why not to keep Leap name? It's normal that distributions develop, and they don't have to be necessarily renamed. It'd be more natural to do the transition between 15 and 16, but otherwise I don't really see problem in keeping the name.
Hi, If I'm not wrong, there will be Leap 15.2 (released in June with openSUSE rpms made from SLE sources) and Leap 15.2 Jump (released in october with SLE rpms) Regards, Luiz -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org To contact the owner, email: opensuse-project+owner@opensuse.org
Dne úterý 14. dubna 2020 16:40:22 CEST, Luiz Fernando Ranghetti napsal(a):
Em ter., 14 de abr. de 2020 às 11:36, Vojtěch Zeisek escreveu:
Dne úterý 14. dubna 2020 16:11:20 CEST, Michal Suchánek napsal(a):
We should decide on a sensible name very soon, otherwise Jump will be mentioned in dozens of places already...
I think it is a very bad idea to change names, Yet another Time.
I think this is not to change name, rather to refer to the SLE based Leap while it exists alongside the Leap as it is built now. I don't really see a problem with Jump as a name for such temporary project.
I don't really see any problem in keeping name Leap during the transition phase. There will be "old" Leap 15.1 and "new" 15.2, won't it? So why not to keep Leap name? It's normal that distributions develop, and they don't have to be necessarily renamed. It'd be more natural to do the transition between 15 and 16, but otherwise I don't really see problem in keeping the name.
If I'm not wrong, there will be Leap 15.2 (released in June with openSUSE rpms made from SLE sources) and Leap 15.2 Jump (released in october with SLE rpms)
If there would be two different Whatever 15.2, it'd be super confusing... -- Vojtěch Zeisek https://trapa.cz/ Komunita openSUSE GNU/Linuxu Community of the openSUSE GNU/Linux https://www.opensuse.org/
Hello team On Tue, 2020-04-14 at 17:43 +0200, Vojtěch Zeisek wrote:
Dne úterý 14. dubna 2020 16:40:22 CEST, Luiz Fernando Ranghetti napsal(a):
Em ter., 14 de abr. de 2020 às 11:36, Vojtěch Zeisek escreveu:
Dne úterý 14. dubna 2020 16:11:20 CEST, Michal Suchánek napsal(a):
We should decide on a sensible name very soon, otherwise Jump will be mentioned in dozens of places already...
I think it is a very bad idea to change names, Yet another Time.
I think this is not to change name, rather to refer to the SLE based Leap while it exists alongside the Leap as it is built now. I don't really see a problem with Jump as a name for such temporary project.
I don't really see any problem in keeping name Leap during the transition phase. There will be "old" Leap 15.1 and "new" 15.2, won't it? So why not to keep Leap name? It's normal that distributions develop, and they don't have to be necessarily renamed. It'd be more natural to do the transition between 15 and 16, but otherwise I don't really see problem in keeping the name.
If I'm not wrong, there will be Leap 15.2 (released in June with openSUSE rpms made from SLE sources) and Leap 15.2 Jump (released in october with SLE rpms)
If there would be two different Whatever 15.2, it'd be super confusing...
We want to test new workflows, maintenance updates etc asap, see if there are some major design flaws. You should really see this just as a having an early protype for the next release priorthe planning phase. Put your hands on it early, because this is how we propose that 15.3 should look like. The More feedback, the better the result. Some people are open to the option that we'd exchange build worklfow in maintenance phase of 15.2. It would not be my preferance, unless protype would work flawlessly and it would be an obvious choice from process/resources point of view. First we really need to know if we'd be even able to do that. That's why the prototype is so important here. -- Best regards Luboš Kocman Release Manager openSUSE Leap SUSE Software Solutions Germany GmbH Maxfeldstr. 5 90409 Nuremberg Germany (HRB 36809, AG Nürnberg) Managing Director: Felix Imendörffer
Dne úterý 14. dubna 2020 16:11:20 CEST, Michal Suchánek napsal(a):
On Tue, Apr 14, 2020 at 03:59:49PM +0200, Carlos E. R. wrote:
On 14/04/2020 15.53, Johannes Kastl wrote:
On 14.04.20 at 15:20 Gerald Pfeifer wrote:
As an aside, Jump is an awful name, since it's a way too common of a word in the English language to build any reasonable branding around it.
Isn't Jump more like $JUMP, its actual name to be determined?
We should decide on a sensible name very soon, otherwise Jump will be mentioned in dozens of places already... :-(
I think it is a very bad idea to change names, Yet another Time.
I think this is not to change name, rather to refer to the SLE based Leap while it exists alongside the Leap as it is built now. I don't really see a problem with Jump as a name for such temporary project.
If the plan is something like Leap 15.1 -> Leap 15.2 -> Jump 15.2 -> Leap 15.3/16.0 (if I get it correctly), why not rather something like Leap 15.1 -> Leap 15.2 -> Leap 15.2.1 -> Leap 15.3/16.0? -- Vojtěch Zeisek https://trapa.cz/ Komunita openSUSE GNU/Linuxu Community of the openSUSE GNU/Linux https://www.opensuse.org/
On 4/14/20 8:57 AM, Vojtěch Zeisek wrote:
I think this is not to change name, rather to refer to the SLE based Leap while it exists alongside the Leap as it is built now. I don't really see a problem with Jump as a name for such temporary project.
If the plan is something like Leap 15.1 -> Leap 15.2 -> Jump 15.2 -> Leap 15.3/16.0 (if I get it correctly), why not rather something like Leap 15.1 -> Leap 15.2 -> Leap 15.2.1 -> Leap 15.3/16.0?
brand product version e.g. suse sle 15sp2 opensuse tumbleweed 20200414 opensuse leap 15.2 opensuse jump 15.2 & a corresponding description of each on the website, for whatever the [set] of distros ends up being. as long as the version # doesn't DECREASE or completely change format, there's really nothing confusing sure, it's possible i'm completely missing a demographic ... -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org To contact the owner, email: opensuse-project+owner@opensuse.org
On Tue, 2020-04-14 at 17:57 +0200, Vojtěch Zeisek wrote:
Dne úterý 14. dubna 2020 16:11:20 CEST, Michal Suchánek napsal(a):
On Tue, Apr 14, 2020 at 03:59:49PM +0200, Carlos E. R. wrote:
On 14/04/2020 15.53, Johannes Kastl wrote:
On 14.04.20 at 15:20 Gerald Pfeifer wrote:
As an aside, Jump is an awful name, since it's a way too common of a word in the English language to build any reasonable branding around it.
Isn't Jump more like $JUMP, its actual name to be determined?
We should decide on a sensible name very soon, otherwise Jump will be mentioned in dozens of places already... :-(
I think it is a very bad idea to change names, Yet another Time.
I think this is not to change name, rather to refer to the SLE based Leap while it exists alongside the Leap as it is built now. I don't really see a problem with Jump as a name for such temporary project.
If the plan is something like Leap 15.1 -> Leap 15.2 -> Jump 15.2 -> Leap 15.3/16.0 (if I get it correctly), why not rather something like Leap 15.1 -> Leap 15.2 -> Leap 15.2.1 -> Leap 15.3/16.0?
There are two options on the plate. But first let's make sure that it's clear that we will not support two openSUSE Leap based distributions in parallel at least not for primary Arches (RISC-V, armv7 might be different stories). The goal is to reduce effort, not to double it! What's really Jump? Jump is under name "jump" only a tech preview / prototype, which is subject to further research. It's not a supproted upgradable product/project from 15.1 or 15.2. Nobody blocks you to migrate to the tech-preview, we'll be happy for an extra testing, but it's unsupported. In the end we will have to do some heavy testing on all kinds of migrations, as one of goals is seamless migration to SLE. So back to options Option (1) - All goes well (prototype is accepted well, all works as expected). We Start setting up Leap 15.3 Alpha in later summer. openSUSE 15.3 Alpha is already based on the new Jump build workflow. openSUSE 15.2 mainteinance stays untouched. Leap 15.2 is discontinued/unsupported 6 months after 15.3 is releases. Option (2) - Same as (1) + But at some point in time we will rework 15.2 updates to be build in a way like the new openSUSE Leap 15.3 Alpha . openSUSE Leap 15.2 receives a maintenance update which will be released together with install image refresh "aka" intermediate release 15.2.1. I'd really vote for as seamless-as-possible upgrade or even update if possible (let's see how research goes). A lot of packages would be replaced due to vendor changes. This would most likely happen somewhen in Autumn. Perhaps we will really have to use 15.2.1 in case that 15.2 itself would not be upgradable to SLE (again let's see how research goes). But I believe we already claim that user is expected to install all available updates. Option (3) - Everything goes bad, protoype is not accepted well and we keep Leap as it is, but at least we were able to align SLE and Leap sources. Resource-wise (2) is the best option as we can finally focus just at "one" openSUSE Leap build workflow alredy in late Summer/Autumn and save a lot of duplicity on keeping both operational. 12 months is really a lot of time. I'd still like to see Jump operational before we decide to flip the switch. -- Best regards Luboš Kocman Release Manager openSUSE Leap SUSE Software Solutions Germany GmbH Maxfeldstr. 5 90409 Nuremberg Germany (HRB 36809, AG Nürnberg) Managing Director: Felix Imendörffer
On Dienstag, 14. April 2020, 17:57:46 CEST wrote Vojtěch Zeisek:
Dne úterý 14. dubna 2020 16:11:20 CEST, Michal Suchánek napsal(a):
On Tue, Apr 14, 2020 at 03:59:49PM +0200, Carlos E. R. wrote:
On 14/04/2020 15.53, Johannes Kastl wrote:
On 14.04.20 at 15:20 Gerald Pfeifer wrote:
As an aside, Jump is an awful name, since it's a way too common of a word in the English language to build any reasonable branding around it.
Isn't Jump more like $JUMP, its actual name to be determined?
We should decide on a sensible name very soon, otherwise Jump will be mentioned in dozens of places already... :-(
I think it is a very bad idea to change names, Yet another Time.
I think this is not to change name, rather to refer to the SLE based Leap while it exists alongside the Leap as it is built now. I don't really see a problem with Jump as a name for such temporary project.
If the plan is something like Leap 15.1 -> Leap 15.2 -> Jump 15.2 -> Leap 15.3/16.0 (if I get it correctly), why not rather something like Leap 15.1 -> Leap 15.2 -> Leap 15.2.1 -> Leap 15.3/16.0?
It is right now not defined what will happen exactly. But we needed another name, because I need to be able to setup it in parallel in OBS. And I must be sure not to break Leap 15.2 with that. So we have therefore openSUSE:Jump:15.2 for now. My only goal there is to get media build (including ftp tree) there atm. So many packages are missing for now. The only thing what is a clear goal for Jump 15.2 is to have a release so that we can also verify maintenance update workflows afterwards. But it is not clear yet if Jump 15.2 will be conidered as experimental release, a parallel official release or even a successor to leap 15.2 This is something what we need to discuss later this year, because I think we all do not have enough insight before. -- Adrian Schroeter email: adrian@suse.de SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org To contact the owner, email: opensuse-project+owner@opensuse.org
participants (7)
-
Adrian Schröter -
Carlos E. R. -
Lubos Kocman -
Luiz Fernando Ranghetti -
Michal Suchánek -
PGNet Dev -
Vojtěch Zeisek