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.

Required fields*

Rev

0.0.0.4321 is lacking, as it doesn't have meta information as to which release it belong. The number will grow to thousands in few years. That's the reason why we don't want to use auto-incremented build number in the version anymore.

Sinatr
– Sinatr

2018-04-17 11:37:37 +00:00
Commented Apr 17, 2018 at 11:37
@Sinatr: I understand. I mostly wanted to have it mentioned as a possibility for others who stumble upon the question.

Bart van Ingen Schenau
– Bart van Ingen Schenau

2018-04-17 12:02:33 +00:00
Commented Apr 17, 2018 at 12:02
I like your second idea. Indeed: the new branch should not receive new number before it's stabilized. Though this solution has same issue as per @DocBrown answer: if trunk is 1.2.0.26, then branch will never become 1.2

Sinatr
– Sinatr

2018-04-17 12:36:40 +00:00
Commented Apr 17, 2018 at 12:36

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 »