Sorry to say, but to me it looks that you and we are on a complete different path of understanding, which makes it difficult to communicate.
Yes, thats my impression too. If the “normal” user is expected to be installing a fresh Leap, accepting everything is fine and not changing it, just running some delivered programs in the Version delivered - than that may be. But in my experience, that does not work out. Many Programs are out of date and if you read the docs of that program in the net, you want to update that version. You will than shortly run into things that are not working out of the box like the users are expected to be, which make them getting frustrated and deleting leap again. This may be the reason, why opensuse is not wide spread when talking to other linux users. (BTW. i always had bad experience with tumbleweed, which broke after some time beeing used many times sadly)
So my recommandations would be: deliver the full features to the customers like me! Explain to them what can be done and how it should be done. I i were experienced like that, i would definitely do so in the wiki.
That far, none of the docs shown here would explain what SPs are for and which are the right Repos to use in the openSUSE world. By not documenting them, the problem is not solved as they are there and do have some meanings currently not beeing clear to the users.
Especially the way, they disappear again and cause error in refreshing is not made clear. I expected them to be additionally for ever, only having Versions not beeing available in the main repos as this is what they used to be in the beginning (could be the reason, why they where there).
That their versions are taken to the above main repos, after some time, which is making them obsolete, but still they are not removed from repositories automatically is confusing.
For me, the simple statement like
“http…/…SP3/” had been integrated into “http…/update/someting” at Date X, making SpX obsolete
would have been enough not to ask here.
Or a way in yast to see, that all programs of that repo are now in another repository and that this one is deprecated (a function, which i cannot find in yast).
Or - coming back to my original question and even better - if they had been automagically removed from the repositories after them beeing integrated in the main repos or maybe stating that they are obsoleted by that when running “zypper up” by hand.
The other part- doing updates on a time base - is already done by online-configuration (which is done via cron) and which i am using unattended on many clients never having problems with that great function.
Maybe the user forum is not the right place to discuss the functionality. Neverless i would appreciate it, if someone could improve the wiki-docs for that.
Thanks for your clearance. Maybe sometime i can help improve this great product. And thanks for your patience