Talk:Release Management

From Wikipedia, the free encyclopedia

Steven Seim 17:33, 8 October 2007 (UTC)== Vote not to merge ==

Hello. I would suggest that the article stay as is and not be moved.

Bodies of knowledge such as ITIL, SMF, et al cover release management, but the application of the knowledge is dependent on the environment the release manager finds themselves in. This is amplified no small amount when globalization/localization is involved, and this is rarely covered as part of the release process.

Accounting for project scope is also a factor in relation to steps and process. Release managers handle very large projects to simple applets released to web. Not all suggested guidelines and steps are necessary.

If it can be accepted that the Hardware/Software/Service lifecycle boils down to a core of:

Envision
Develop
Release
Sustain
Retire [and/or] Replace

it can (or should) be accepted that release management varies in accordance to:

Company
Division
Unit
Team

This article in my opinion covers the core and should not be moved nor merged. If anything, amp up release topics that are more difficult to quantify and make explicit, such as relationship management, negotiation, et al. It may be worth noting that release managers working in a cross group environment need to know varying tool suites again in accordance to:

Division
Unit
Team

Thank you. Steven Seim




This article is related to Wikipedia:WikiProject Method engineering.
Please note that the use of Wikipedia to host this project has been questioned. Please read this discussion and, if you wish, contribute your thoughts there.


Contents

[edit] Not copyvio after all

Original author got back to me via email (in reply to my mail to the address on the original article, so I believe that this is a genuine release of the material under the GFDL). I'll try to NPOVify and re-structure it and comment on the VfD page. -Harmil 22:16, 18 July 2005 (UTC)

[edit] Vote decision

I see two votes for keep , one for cleanup and two votes for transwiki. http://en.wikipedia.org/wiki/Wikipedia:Votes_for_deletion/Release_Management So how come the decision was for transwiki?


[edit] Update

I went in and cleaned some things up, I think it's a little better now. How can we go about getting this untranswikied or whatever? - jlittle227 1 January 2006

How about adding it to category Software development process and ask whoever is active on that page? You have to be cautious to avoid it being wiped again. --15:50, 25 March 2006 (UTC)

[edit] Conflict with ITIL language

This page is about release management in the SDLC; however ITIL uses the term Release Management to mean something substantially different. The Quest Best Practices whitepaper linked is actually on that kind of release management. Is a disambiguation page the correct solution? To an non-computer/IT person, the distinction isn't going to be really obvious.

Henry Troup 23:59, 19 February 2007 (UTC)

[edit] Vote for merger with Release Management Method

I feel that there is much overlap between the two articles. As such, the concept of Release Management is a more central one and term is more widely accepted than Release Mangaement Method. In Software Engineering, one deals with the specific aspects given in the article of Release Management Method. Hence I would suggest that the articles are merged as one "Release Management" article for the benefit of the readers. —Preceding unsigned comment added by 196.12.53.9 (talk) 16:45, 1 April 2008 (UTC)

I had forgotten to sign this post.

Aditya Agrawal —Preceding unsigned comment added by Adimax24 (talk • contribs) 16:49, 1 April 2008 (UTC)