Update: Unity staff have provided clarification about the “Recommended” badge in Unity Hub. I’ve included this information in the video below. You can also check out My Complete Tutorial on choosing the right Unity version.
We’re using 6000.0.{patch}, where the patch is for “must-haves” only.
Of course we’re not going to use the later LTS and it certainly shouldn’t be “recommended”, since it’s still considered cutting-edge. Unity should know better than this 
It’s still frustrating that Unity users can’t even get a specific patch via Hub, despite the likelihood of team collaborators sticking to the same patch. It’s pointless to only offer the latest version for people creating new projects. How often are people actually creating NEW projects?
The reality is that the average team will be using the exact same version of Unity for the majority of the year, if not more. Maybe a patch here and there, but not every patch.
Hub should really consider realistic, not utopian, scenarios:
- Recommend the first major version and latest patch of the LTS
- During the LTS phase, I should be able to download any patch I want from Hub of that LTS. Your downloaders have detectable patterns - it wouldn’t be difficult to do this.
- Detect my project versions and show a list of what projects of that patch I’m actively using! Give us some minimal UX here, you have the info already
CC @kaylafortin Please help us pass the feedback 
Hey folks,
There’s not much we can say here, but please understand that Unity version numbering and recommendations are outside of our control.
Sorry I can’t give you a better answer!
Yes, it’s inconvenient to use the Archives page when I need the exact Unity version. The QoL improvement here is to use Unity Hub for this task.
Hi @makaka-org
We’ve received a few suggestions of that nature. We’ll look into it for 3.19 – we’re at capacity for testing and QA for 3.18. It would be a great QoL improvement.
Thanks for the feedback!