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.

Thanks for responding @Ewan, appreciated. Ok, I think I understand... so version held in version.py file would be patch bumped on each release branch and not merged back to trunk. On the trunk, version.py would be bumped for major/minor changes. Trying to understand the cherry-picking issue though....what happens if fix needs to be available on trunk and future releases also?

dcs3spp
– dcs3spp

2019-04-12 10:22:32 +00:00
Commented Apr 12, 2019 at 10:22
you have to do it twice

Ewan
– Ewan

2019-04-12 10:36:41 +00:00
Commented Apr 12, 2019 at 10:36
Thanks @Ewan, will try out versioning approach and accept answer.....

dcs3spp
– dcs3spp

2019-04-12 11:14:06 +00:00
Commented Apr 12, 2019 at 11:14

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 »