Hi all,
I’m confused what the release branch is, on github. The description implies that it is the QA-tested version, so I assumed that it only holds official versions. I expected 4.10.2 to be there, only after compiling on Linux, to find 4.11. As far as I know, 4.11 is not an official release, yet.
Is this correct, that the release branch may have preview versions too?
Thanks
4.11 was accidentally merged into release branch.
So for this release, the preview is already merged in.
Next release will be back to normal.
Ah, cool, thanks for the update! 
I’ll wait for the official 4.11 release, I think, since this one crashes on load. And I can’t build 4.10 on my system, since I have a newer version of clang, and cannot figure how how to tell the engine to use a different version.
Anyway if you want to ensure to pickup the engine version you want the easiest way is to pull the dedicated branches or the tags.
Yup, done that, and that part is fine. The way clang is being invoked seems off, though, since the LIB/INCLUDE paths are referenced more than once in the BuildThirdParty.sh. Makes it insanely tedious to try and figure out how to use a custom, pre-built version of clang. Especially since the engine versions seem very picky with which versions of clang you can use to compile it.
I had a warning message about this on the Github Readme but it seems to have gotten overwritten. I’ll see about getting this back up permanently (until 4.11 officially releases)
This $64K question is whether anything built with 4.11 preview will be compatible with 4.11 release. There’s been significant issues with stuff built using preview versions refusing to load on release versions.
I know its not ideal situation to be in, but it hasn’t happen to me (not saying all that much) and it has been a pretty rare situation (in general). I’ll bet 64 cents 
Actually, it’s a serious question. Anyone who downloaded and started using the 4.11 pre-release fork and who is unaware that the fork was posted to release by mistake is at risk of losing all their work as any content modified under 4.11 will possibly have a poison version number attached to the content rendering it totally inaccessible in the release versions.
No one should be using 4.11 pre-release for any production ready work.