On 1/10/22 14:45, rbrown wrote:
On 2022-01-06 16:02, Michael Ströder wrote:
On 1/6/22 14:10, Matěj Cepl wrote:
Dne 06. 01. 22 v 12:21 Michael Ströder napsal(a):
Nobody is willing to pay for increasing backporting efforts needed for keeping outdated stuff. It's just that these costs are not really made transparent.
Sancta simplicitas! Who do you think actually pays real money to SUSE for maintaining SLE? Users of free Leap? Exactly the companies who complain that we upgrade too much.
Re-read my postings.
Actually you're oversimplifying.
And you are oversimplifying also
Nope.
The reality is simple SUSE is paid by its customers to stay in Python 3.6
The above simple statement can only be false. And you know that very well. SLE customers are paying for some sort of "stable" support. What they consider "stable" in various project situations is not as clear as you state here. It varies a lot. Most times customers do not care about specific package versions of something until project requirements are in conflict with what's provided by the OS. So the big question is how to keep average amount of these conflicts low - and where the budget comes from. Obviously nobody has any one-size-fits-it-all solution.
While the wishes of the community matter, SUSE is a money-making company in the business of making money, so SLE/Leap will 'follow the money' I fully understand this. Being self-employed I also have to follow the money.
Please note that personally I'm not interested in Leap at all. Maybe I should have rather used "SLE15SP4" instead of "Leap 15.4" in the subject. Because SLE is what will affect my own customer projects.
well what exactly do you offer SUSE in return?
Happy SLE customers who do not consider migrating to another OS. The challenge in product management is that decisions are sometimes self-fulfilling prophecy. E.g. you limit a product in a certain way and then you can claim that the rest of the customers still willing to pay for that product are the nearly 100% who want to be it exactly that way. You will not know about the other customers and their needs. Maybe a solution would be to market OBS and openQA even more to make customers familiar with these powerful tools, very helpful to reach "stable" production even when doing more regular OS upgrades. Actually I'm trying this but my customers are rather scared by the amount of work. Well, maintaining infrastructure is always short on budget. :-/ Ciao, Michael.