Hello,
when will the official long-term version for OS7 be released?
When it is ready.
Moving topic to appropriate place, this has nothing to do with swos
MT is waiting until you give up waiting and will release it the next day.
Do you like asking questions that no one here knows and even MT staff do not know.
Which existing version should become long-term?
My favourite kebab-retailer said that 7.1.5 was a good one …
You could build 7.11.3 and push that to long-term. 
I recent watched a video with Dave Cuttler (architect of VMS, WinNT, Xbox), so pretty sure his answer be when there are 0 known bugs.
More realistically given the loose definitions & existing complaints that stable isn’t stable – it a no win game. So using “long-term” as the previous stable seems like a worthwhile plan. With more data, y’all likely have a better sense of what stable based on ratio/# of support cases difference between stable and “long-term”.
And the ability to use System>Package to change channel allows easier roll-back if stable wasn’t stable.
I read somewhere that after the release of 7.12 you release not only stable but also long-term
long-term is not a special version.
it is a “status” that is assigned to an existing version.
let’s say 7.12 is super stable and has zero bugs. after 3 months if it still is PERFECT. we may rename it to long-term
in theory
You’re going to get grief regardless. Right now it’s an “empty slot” in /system/package that could be used for something (e.g. last known stable). When a future 7.13 stable eventually ships, y’all can make a call if 7.12 becomes long-term based on some real data.
That used to be different with 6.x… A version from stable never made it to long-term, instead we had new build with even more cherry-picked fixes.
For me 7.12 is perhaps the roundest version and the incorporation of BTH is a plus.
I consider it to be a good basis to maintain, correcting only bugs that may appear in the future.
Thanks MKT for this hard work. 
that’s not true. first long-term is always an exsting version.
but then it can get small updates for CVE issues
The central idea, which I agree 100%, is “long term” is a promoted stable build (“copied”) that’s been in field for at some amount of time. 7.12 came out yesterday – it’s not useful to have stable and long-term be identical.
Respectful side note (since I was paying attention in Economics class):
perfection is impossible to achieve for quite a lot of things (especially something as complex as ROS) and way too expensive even trying to get there.
That’s a simple reality.
You are wrong. Let’s have a look…
v6.48.4 [stable] on Mon Aug 23, 2021
v6.49 [stable] on Thu Oct 07, 2021
v6.48.5 [long-term] on Fri Oct 08, 2021
It has always been like that, perhaps with the very recent versions in 6.49 just a few weeks or month ago being an exception.
What your table doesn’t show and I’m not sure it’s possible to get that missing info from the past: when exactly did 6.48.x got promoted into long-term? Was it the same second when 6.49 was released into stable (and logically 6.48.4 was not the latest stable any more) … or was it only when 6.48.5 got released directly into long-term (in this particular case one day later)? I seem to remember that it was the former, so whatever latest stable became long-term and frequently it did not see a new “patch release” until much later. Long term release changelog corroborates my theory somehow. E.g. 6.45.7 (stable) 2019-10-18 … 6.45.8 (long-term) 2020-01-19 … 6.46 (stable) 2019-12-03 … so what misses is info about which was long-term between 2019-12-03 and 2020-01-19 … my memory says it was 6.45.7.
No, it was not. That was a stable release and never made it into long-term.
Hello,
Any news on a long-term support version 7? Is the development team waiting for a bug-free version to mark this release?
Thank’s
J.D
Why??