Do you have plans for how one should communicate, for example, “Requires Unity 2022.3 and newer” when Unity 6 is released?
I’m asking because most of my packages have a minimum Unity version, and it sounds confusing to write: “Requires Unity 2022.3 and newer, and Unity 6 or newer” since Unity 2022.3 gives the impression of being newer than Unity 6.
I’m sure you understand what I mean 
Will the versioning change also be reflected in the UNITY_2022_3_OR_NEWER-like scripting defines?
Well, what about:
Requires:
Don’t forget UNITY_VERSION in shaders
Let me chime in quickly here…
If we skip the “since Unity 2022.3 gives the impression of being newer than Unity 6.” part what seems to be the problem?
In my opinion - 2022.3 doesn’t mean never version than Unity 6. Maybe for someone totally outside of this ecosystem it would, but I bet that the majority of us know a bit about Unity, so for example
seems redundant to me. I mean the 2nd bullet point as the 1st one states things clearly.
Maybe we should rename Unity 6 to 2024 LTS and every version should get the year number it gets actually released. Or something…
Redundant to people who know their stuff around Unity, the others might need a little more. Honestly, I don’t know if Unity 2022.3 and Unity 6 are the same thing. I thought 2023.3 would be Unity 6.
If they are the same then:
Unity 2022.3 is already LTS and will not be renamed. The upcoming 2023.4 (since Unity announced 2023.3 as a tech release and the LTS will be renamed) version will be called Unity 6 from my understanding. Since there already are released versions of 2023.x, it should matter what is displayed as requirement.
Hi all,
I just wanted to do some quick clarification on versioning so you can prepare your documentation and other materials accordingly.
Current releases:
Future releases:
Versioning:
Unity 2023.3 - initially as can be seen in the beta released last week, the version will be 2023.3.x. However, by the time we hit the production supported version of this release, this will switch over to the new 6000.x.x version numbering.
Unity 6 - will use the 6000.x version numbering scheme.
Therefore:
We’re going to communicate more about this very soon, but didn’t want to hold you up on this specific piece of the puzzle.
Thank you very much for the help!
Ah, very interesting decision to go with 6000 (I like it). Looking forward to Unity over 9000! 
In the year 6000, Unity 6 was released unto the world…
Unity 2024… what could have been the best version in years… sadly we must go back to Unity 6
Sorry…
In the year 6000,
if man is still alive
If Unity can survive,
they may find version 6
In the year 6006
Ain’t gonna need to tell the truth, tell no lie
Everything you think, do and say
Is in the bug you submitted today still has no fix
In the year 6060
You ain’t gonna need your teeth, won’t need your shader
You won’t find a thing to render
Nobody’s gonna look at you
In the year 6066
Your arms hangin’ limp at your sides
Your legs got nothin’ to do
Sentis’ doin’ that for you
In the year 6666
You won’t need no husband, won’t need no wife
You’ll pick your editor, pick your AI too
Unity finally releases Unity 6.6
Thank you Zager and Evans for the psychedelic song
lol
you guys are too much
and when the current CEO gets the boot and the new one likes his years back, to keep number sorting we’ll end up in 20250, by that time the Padishar Emperor is long gone, Ix machines replaced the Guild of Navigator then what? what? Unity!
I had gotten that right.
Uh? An example, please? Thank you.
From now on I will solely refer to Unity 6 as Unity 6000.
I’ll wait for Unity 8086 to make full circle in this gamedev adventure.
I’m waiting for Unity 6502
I’m waiting for Unity 9000. Watch out HAL!