eg 2018.4.36f1 to 2018.4.36
The f makes version numbers “f” ing confusing.
ie
2018.4.4f1 is way less than 2018.4.36f1, even though it looks bigger.
f stand for final, as end users we know it’s a final , or a p patch. If you must put it somewhere, don’t put it at the end.
Cheers
Could also be 2018.4.04f1 to make it less confusing. 2018.4.04 is best version number though.
It doesn’t make them confusing at all, it just preserves a standard convention.
Unity does not use sematic versioning for Unity engine, but it is very similar. Leading zeros are not allowed there.
When was the last time we‘ve had a Unity version ending in f2, f3 or higher?
I agree that the whole „f“ scheme could simply be dropped, while alpha and beta builds retain their a and b suffixes.
seems quite rare
f22 
What ever happened there? Was the whole QA department on vacation?? 
i think f[×] are builds from the same source, maybe there were build problems…
ah that makes sense, the f stands for „oh fxxx, not again!“
2020.3.15f2 it seems.
That build doesn’t exist. I don’t know where that screenshot is from but it’s 2018.1.8f2 not 2018.1.8f22: https://unity3d.com/unity/whatsnew/unity-2018.1.9f2
In any case, it’s unlikely we would be changing this. There’s just no point and would break everyone’s Unity’s version parsing code. Unity Download Archive makes it very easy to tell which builds are newer.