Hub should state editor versions more clearly

For the context: right now the newest Hub places the 2019.3.0f1 RC 1 into pre-releases, some former Hub version put it into stable releases and some didn’t show it up at all :slight_smile:

This is how it looks now:

but this isn’t obvious to all that it’s a release candidate as the hub nor the editor doesn’t state this in any way.

It would be so much better if they did it like this instead because it would leave out completely all the guesswork:

Additionally Unity sometimes releases custom experimental versions on the forums etc for people to try things out that are not ready for main distribution yet, we’ve seen these for all kinds of things like recently for raytracing and physx but not limited to these alone.

Issue with these is that the Hub does pick these up but doesn’t label them at all. Instead if you got say, experimental physx editor that’s built against say 2019.2.0f1 and you want to use Hub with it, Hub just assumes it’s regular 2019.2.0f1, doesn’t give it any extra label (so making it hard to differentiate from the real release) and also you can’t even install the exact same real version using Hub as Hub thinks it’s installed already :slight_smile:

All in all, it would be nice if there were some system where Unity could just mark certain editor versions (be it from the release hash code or whatever makes sense to them) so that we could get some additional data what that version is for, just like now happens with Alpha and Beta tags after the version.

3 Likes

+1 for this, we got a lot of support requests regarding 2019.3 over the weekend stating “it has been officially released now” because the 2019.3 RC showed up unmarked in the hub under official releases.

Just to add to the original post, this unclear naming isn’t just present when you add the engine version (where original post’s images were from), it’s even more confusing if you just look at the installed engine list:

Second install is RC and third is actual release, but these are not differentiated in any way so obviously users would assume both are full releases if they only look at this view.

Launching the 2019.3.0f1 editor doesn’t indicate you are using RC in any manner either.

I can totally see the reasons that lead to current approach but it still misleading for many engine users and should be fixed IMO.

1 Like

Thanks for the feedback! I’ll definitely circulate this internally, as it’s really valuable.

1 Like

Just wanted to note that we still get people coming up to official Unity discord every day either telling 2019.3 is out or just wondering why they didn’t get release announcement for 2019.3.

So despite it’s listed on pre-releases, it hasn’t stopped people from confusing it to an actual release.