Hint for people posting release announcements: you could save a great many people quite a lot of time, cumulatively, with just a single short sentence in the first paragraph of your announcement. You probably would pick up some new participants who would have given up in disgust before they could discover what the hell the thing is.
Release notes for a new version are not the place to list all the features of the engine. You can literally click on the home page and see "Object-oriented API with language options such as GDScript, C#, C++ and visual scripting.".
If people give up "in disgust" because they can't find what language the engine uses for scripting immediately in the first sentence of a release announcement then they're probably not cut out for making any kind of software which requires digging through documentation.
Nobody asked for, or needs, a list of "all the features" in a release announcement. Saying what the project is (such as that it is some kind of "engine", and maybe even what kind?) would have been a completely different, and much shorter and overwhelmingly more useful statement.
What should motivate a reader who cannot even tell what it is to spend time groveling around to find out whether they might be interested in the thing? Hint: most projects are not interesting to most people. Forced to guess, the best guess has to be "no".
I am repeatedly astonished that such elementary reasoning seems beyond so many.
As it happens, for example, a game engine in C# is of zero interest to me, but one in C++ could be quite interesting. I dismissed it as a direct consequence of the failure of the announcement to give me any reason to pay it any more attention.
"I am repeatedly astonished that such elementary reasoning seems beyond so many." Perhaps you're just wrong? If everywhere you go smells like shit you should check your shoes.
[1]https://devblogs.microsoft.com/dotnet/announcing-net-core-3-...
I feel no slight temptation to look at .NET announcements, nor to draw conclusions on good practices from them.
But all of the apoplectic rage is clearly on your side.
Is this supposed to be a joke? The information exists but you didn't try to find it.
It is the entire topic of my original post.
Really, what would be so terrible about a short sentence in an announcement so that people who don't already know all about it get some hint at what it is? No one has suggested anything like an answer. Instead, I find rage that I don't, what, just automatically go digging deep into project pages for every single new thing announced, just in case whatever it is might turn out to be interesting?
Everyone has a lot of demands on their time and attention. A person writing an announcement is necessarily trying to communicate and engage. Concealing the topic sabotages the effort, right out of the gate.
https://docs.unrealengine.com/en-US/Support/Builds/ReleaseNo...
https://docs.unrealengine.com/en-US/Support/Builds/ReleaseNo...
Game engines this size often add many new features with every release, and the target audience (programmers and artists) want to know about all of them.
It's just one click on the logo to go their home page that says it's a game engine with some big features like being open source.
Being mysterious must provide some other benefit, to someone, if it has such vehement defenders. I know better than to ask what or who.
I don't know what axe you have to grind but what you're doing is basically the equivalent of looking at the fifth page of a bus schedule and then getting angry at not knowing what a bus is even though it is clearly written on page one.
If you want an introduction to a product then go on the home page [0], the features site [1], the Wikipedia site [2], anywhere except the darn release notes. People are getting angry because there are huge big fat eye catching buttons in the header that point to these pages and you're purposefully ignoring them to the point that you're basically trolling.
[0] https://godotengine.org/ [1] https://godotengine.org/features [2] https://en.wikipedia.org/wiki/Godot_(game_engine)
Really, what is so difficult about this?