On Tue, 2022-11-29 at 10:46 +0100, Jiri Slaby wrote:
On 29. 11. 22, 10:17, Richard Biener wrote:
It always depends on the benchmark, but the more strong argument is marketing and manager perception.
Ah, I was so dumb and now I see -- it's only politics in it. And it affects community-based distro. Yes, I understand the SUSE's POV -- to sell, sell, sell. I also know, that managers always affected openSUSE in some manner. At least indirectly by e.g. providing HW, manpower etc. But this is sort of different. This appears to be a non-technical decision applied to _open_SUSE for reasons I still don't follow.
How about considering the following Factory/Tumbleweed has an important role as the target for SUSE's "Factory First" policy That function of Factory/Tumbleweed is a lynchpin that justifies the HW, manpower, etc that SUSE provide openSUSE for Factory/Tumbleweed A Factory/Tumbleweed that is still v0 when SUSE's commercial products are all v2 is significantly degraded/pointless in it's role as SUSE's "Factory First" target Ergo, it makes perfect sense that Factory/Tumbleweed must at least be v2 if SUSE is jumping to v2 (no matter SUSE's reasons, be they technical, political, religious, or otherwise) It's the right call, purely to ensure the relationship between Tumbleweed and SUSE's products remains relevant.
And as a workaround, it seems it will result in building Tumbleweed exactly twice. Bah. OK.
Well we don't NEED to build Tumbleweed twice. If we didn't have you or someone like you stepping up to take on the burden of looking after it, I'm pretty sure we wouldn't be doing the second build. Regards, -- Richard Brown Linux Distribution Engineer - Future Technology Team SUSE Software Solutions Germany GmbH, Frankenstraße 146, D-90461 Nuremberg, Germany (HRB 36809, AG Nürnberg) Managing Directors/Geschäftsführer: Ivo Totev, Andrew Myers, Andrew McDonald, Martje Boudien Moerman