- Thank you for updating them last week.
- Well, while “mistakes may happen”, to repeat the simple mistake “forgot to update the list for more than half a year” should be avoided IMO (which now happened for at least the second time, IIRC the third).
For now I assume, that Jolla / you will pay more attention in the future.
Stop Releases should not have a big role anymore, in my understanding, as most users are able to reflash their Xperia devices again, instead of taking the painful reset-device-and-update-via-stop-releases approach.
Well, you see how much grief issues cause, which may easily be caused by “jumping over” a stop release in this thread here and e.g., the thread “Problems with OS update 4.3.0”
(although it seems the most of the issues are caused by something else, the effects are similar).
And it was your assumption that “traversing a stop release” is the reason for a good part of the issues discussed at “Problems with OS update 4.3.0”.
And I do not concur that users should upgrade SailfishOS by re-flashing to a newer release (instead of upgrading at the GUI or TUI)! While you sure did not intend to state that this way, it is ultimately what you are saying, because there is sufficient incentive (due to the many new bugs in every recent SailfishOS release since v3.2.1) to omit installing some releases (for me: all; I re-evaluate this with each new release).
Thus, I disagree that stop releases do “not have a big role any more”, especially when every release is a stop release (3.4.0, 4.0.1, 4.1.0, 4.2.0, 4.3.0, and there were not documented as such).
What comes to [1], at least I have done nothing to “prevent scripted downloads programmatically” - I do not even know how to do it.
- Thank you very much for addressing this issue (seriously); this is the very first time any sailor does that!
- Nobody ever stated that you personally have caused this AFAICS.
- Please let us continue to discuss this issue at its original thread.
I provided an in-depth issue description, its history and proposed solutions.
And I still believe, that something which has been working for years and then some configuration change broke it, must be easily fixable.
P.S.: Does the fact that you as a sailor references the list of stop releases at the English Wikipedia imply, that this list officially maintained by Jolla (e.g., you)?
I.e., are you saying that I should use that one instead of the now un-retrievable one at Jolla’s Zendesk instance?
As denoted, I do not believe it is easier for you / Jolla to maintain multiple lists, rather the opposite!