4 ms·

Some meta discussion: "xyz reaches/releases version number 234234.324234" is entirely meaningless and the best way to ensure that nobody will care about your re

Some meta discussion: "xyz reaches/releases version number 234234.324234" is entirely meaningless and the best way to ensure that nobody will care about your release announcement. Your project may internally have a very well defined and entirely logical policy as to how exactly to change version numbers based on internal project changes, but from the outside this is 100% untrustable and invisible, meaning your 2.0 release could mean anything from "we rewrote the entire thing" or "a set amount of time went by" (see Firefox/Perl/probably others). If you actually care at all about your release announcement being read, include in the title line the actual benefit the new version provides to people.

paulbennett 11y ago
Arguably anyone following the project will be familiar with their version numbering policy. For those that are new to the project (including myself) a list of benefits in the title provides little information anyway as I have no background knowledge of the project before this release. Either way the best option is to read the announcement to find out more.
chris_wot 11y ago
I have to disagree. Announcing a major new release by version number is enough to be most people to click on the link. Now a lack of release notes and a major features/what's new document - that's a release promotion fail.
erikb 11y ago
Yeah or announcing other things that are actually valuabe to readers like "Game engine XYZ reached 1000 published games" or "Game engine ABC reached this new platform DEF".
tcfunk 11y ago
Yeah I would say the version number definitely has meaning, particularly in the case of a major version release. I could see something like "Godot reached 2.0.1" getting a little tiresome. I would agree that, for a minor release like that, wording the announcement as "Godot engine now supports xyz" would definitely be more helpful. But when they've got 20 or so major new features, there's not really a better way than to say "Godot 2.0 released" with a link to the changes.

paulbennett 11y ago

Arguably anyone following the project will be familiar with their version numbering policy. For those that are new to the project (including myself) a list of benefits in the title provides little information anyway as I have no background knowledge of the project before this release. Either way the best option is to read the announcement to find out more.

chris_wot 11y ago

I have to disagree. Announcing a major new release by version number is enough to be most people to click on the link. Now a lack of release notes and a major features/what's new document - that's a release promotion fail.

erikb 11y ago

Yeah or announcing other things that are actually valuabe to readers like "Game engine XYZ reached 1000 published games" or "Game engine ABC reached this new platform DEF".

tcfunk 11y ago

Yeah I would say the version number definitely has meaning, particularly in the case of a major version release. I could see something like "Godot reached 2.0.1" getting a little tiresome. I would agree that, for a minor release like that, wording the announcement as "Godot engine now supports xyz" would definitely be more helpful. But when they've got 20 or so major new features, there's not really a better way than to say "Godot 2.0 released" with a link to the changes.