Talk:Release Management

What I'm missing here is some information on timeschedules. We're currently in a semi large project that has realy got difficultly with release management. Currently it's still under development and we're scheduled to our first release on 01 jan 2006. The daily practice is to release new changes into production (after testing in a deployement environment). This causes a lot of restlessness in the Production Environment and Developers and End-Users aren't realy able to focus on the bugs that are in the programs. A weekly delivery (let's say on Friday's) would take down the stress a lot and give End-Users and Developers/Analists a more predictable view on the process. I believe the article needs some more juice on this subject. It would help me a lot at least!

itil release management
I'm sure there are some interesting models that could/should go into this wikibook: like itil releasemanagement and it's 5 phases.

collecting pages into a book
Would it make sense to collect Release Management, Collected Real-life Experiences, Transwiki:Career domains in computer science (each of them, at the moment, a single-page "book") into a single book? --DavidCary (talk) 05:03, 2 February 2009 (UTC)

IF we are going to have a discussion, first we must define our terms.
Primarily this article focuses on what I have always called Build Management, carried out by the Build Engineer. When I think of Release Management I am looking for the ITIL definition of the subject as they seem to have co-opted the term if they did not invent it. I have never heard the term used except by ITIL or those using their principles. If I were an expert on the subject, I would provide some text along those lines, but if I was an expert on the subject I would not be reading a WikiBook.