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

Off topic here I know.. but do you have a recommendation for said book relating to release management?

Simon Whitehead
– Simon Whitehead

2013-09-05 13:59:02 +00:00
Commented Sep 5, 2013 at 13:59
+1, this is a great answer, much better than mine!

Doc Brown
– Doc Brown

2013-09-05 14:27:43 +00:00
Commented Sep 5, 2013 at 14:27
@SimonWhitehead: Probably the best high-level book I've read is Continuous Delivery by Humble and Farley. It can be a little on the dry and general side, but seeing all of the disparate concepts put together so neatly really turned my perception of release management on its head. Note, I'm working in a capital-A Agile organization and we do gated (QA-approved, sysadmin-deployed) releases of a highly-available, sorta-high-traffic website, so YMMV of course. Before that, I used to work on a 2-man team with no QA and developer-run deployments, and wouldn't have bothered with a lot of this.

Aaronaught
– Aaronaught

2013-09-05 15:10:43 +00:00
Commented Sep 5, 2013 at 15:10
@Aaronaught, thanks for the response. It is quite informative. I realized after some discussions that the number of files that will be changed during the feature development will be just a few. So, we see that 3 is most apt option as of now. And yes, I shouldn't have called it refactoring.

venkrao
– venkrao

2013-09-05 16:25:49 +00:00
Commented Sep 5, 2013 at 16:25
@venkrao: Up to you, but FWIW, note that #3 (build dependencies) is the only option I didn't recommend under any circumstances. It's never less effort than alternatives and almost always harder to maintain and track.

Aaronaught
– Aaronaught

2013-09-05 18:18:28 +00:00
Commented Sep 5, 2013 at 18:18

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 »