Not true for CR, for Support Tickets everything uses one of the 3 versions but not all the same. I know for a fact this is even confusing internally. It make no sense!
Look at Chrome, FireFox at all they gave up and just went to Whole Number Versions every time sequential Zero confusion. Version 32!
I still wanna know what release is 11.2.300 
^ proving my point 
No see… exactly! We just got 11.200.2 in the Fall (october) release which mapped to 2022.2
So 11.200.3 by definition is AFTER october, and I do not believe Epicor has a Winter Release in 2022… so it has to be 2023.X (can’t figure out the X)
Let me know if you wanna barrow my Abacus…
(it didn’t help) but its fun to use.
CC: @bconner (help us out from a developer side… DOWN WITH MARKETING VERSION!!!)
11.2.300 = 2023.1
Thanks Olga
So… 11.2.300 correlates to 2023.1 (in marketing) yeah that’s not going to confuse anyone. 
So if the 300 patch changes with the year? then what changes the initial 11.2 ← .2… or even the 11?
Following the above pattern
11.2.200 → 2022.2
11.2.300 → 2023.1
11.2.400 → 2023.2
11.2.500 → 2024.1
11.2.600 → 2024.2
When do we go from 11.2 to 11.3? or 12?
So the take-away is support and development need to use the marketing numbers and not the assembly segments when talking to us?
.2 was set because of big technolofy change, WCF => ASP.NET Core. It is not supposed to change second digit every year. Well, at least for now.
I dug through my files and found the workflow they use to come up with the version numbers. It is clearly defined below if anyone is confused refer to this.
Thanks! 
Sorry, @josecgomez, I can’t read the previous image as provided. Too small. Could you please supply the previous schematic on microfiche so that I may utilize my microfiche reader to blow up the image to readable size for my old eyes. Thank you!
Apologies ours broke years ago and haven’t been able to find replacement parts. I do have a hand copied version that our scribes put together circa 1487 which I could mail to you.
It must be handled in a clean room though
OPE!
this is a complete sentence
Also to add to this… In 2022.2 many of the CSF version numbers changed as well and are now lower/older than their 2022.1 version number so you get an undocumented warning when installing them in the solution workbench… fun times
I really like:
I’m sure they just use “Internal Part Cross Reference” to keep it all straight.
^ this wins the internet today thank you for that
“I have Epicor Idea votes to sell…”
11.2.300.x is Kinetic 2023.1.x, Spring Release. If anything besides the last dot release increments it’s next seasonal update year.1 (spring) or year.2 (fall). Before anyone asks, no i have no power to change the versioning scheme :D. The former version is complexity based, the latter is time based, so the numbers dont really have a relationship to find. There’s no puzzle to unlock there.
And just for fun it’s also epicor ux platform version 9.x which is semantic versioned 
We do feel your pain. This causes confusion within Epicor. We have similar complaints about Microsoft around SQL server with the public version getting a year name, the actual version being a few digits behind that and then everyone forgets to check the DB compatibility level which is yet another number but maps to the capabilities available at a specific SQL server release
But this is about Kinetic not other product lines with similar issues. I am not in charge of versioning. What I can do is provide you with something that may help - this is not an official Epicor Document - do not treat it as such. But I hope it can help with some of the confusion.
Bad link sorry - try this one: Kinect Versioning.docx
