Edit - Software Engineering Stack Exchange

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

1

I don't understand how this applies to web apps. The user generally has no choice about which version to use anyway, so you're not giving them any actionable information by telling them that the new version has big changes from the old version. They need some identifier to provide the help desk so the help desk can check for browser cache issues, etc., but encoding semantic information in it doesn't help with that and has a non-zero cost...so don't do that. There are enough real problems to spend time on.

user3067860
– user3067860

2023-10-26 15:04:09 +00:00
Commented Oct 26, 2023 at 15:04

Add a comment |

Correct minor typos or mistakes
Clarify meaning without changing it
Add related resources or links
Always respect the author’s intent
Don’t use edits to reply to the author

create code fences with backticks ` or tildes ~
```
like so
```
add language identifier to highlight code
```python
def function(foo):
print(foo)
```
put returns between paragraphs
for linebreak add 2 spaces at end
_italic_ or **bold**
indent code by 4 spaces
backtick escapes `like _so_`
quote by placing > at start of line
to make links (use https whenever possible)

<https://example.com>

[example](https://example.com)

<a href="https://example.com">example</a>

formatting help »
answering help »