Talk:Release management

message: Quixi (talk) 17:46, 11 November 2008 (UTC)
thread_title:  Merging 

message: 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)
thread_title:  Not copyvio after all 

message: 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)
thread_title:  Update 

message: 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)
thread_title:  Conflict with ITIL language 

message: 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)
thread_title:  Vote for merger with Release Management Method 

message: One or more portions of this article duplicated other source(s).  Infringing material has been rewritten or removed and must not be restored, unless it is duly released under a compatible license. (For more information, please see "using copyrighted works from others" if you are not the copyright holder of this material, or "donating copyrighted materials" if you are.) For legal reasons, we cannot accept copyrighted text or images borrowed from other web sites or published material; such additions will be deleted. Contributors may use copyrighted publications as a source of information, but not as a source of sentences or phrases. Accordingly, the material may be rewritten, but only if it does not infringe on the copyright of the original or plagiarize from that source. Please see our guideline on non-free text for how to properly implement limited quotations of copyrighted text. Wikipedia takes copyright violations very seriously, and persistent violators will be blocked from editing. While we appreciate contributions, we must require all contributors to understand and comply with these policies. Thank you.  MLauba (Talk) 11:02, 14 April 2010 (UTC)
thread_title:  Copyright problem removed 

message: Perhaps the definition of 'release' is a prerequisite to release management.  — Preceding unsigned comment added by Agile-enthusiast (talk • contribs) 01:48, 31 August 2020 (UTC)
thread_title:  Definition of 'release' is not available anywhere 

message: The depicted scheme is currently not in english language. 89.245.155.54 (talk) 08:00, 12 April 2024 (UTC)
replies: text: Yeah, I noticed that…  (Or at least, not _wholly_ in English.)  Most terms are similar enough to be fairly understandable, but at least one stands out and needs explanation — or, preferably, translation!  Is there any reason not to replace the (I assume) Swedish scheme with an English one? Gidds (talk) 11:22, 11 May 2024 (UTC)
thread_title:  Depicted scheme currently not in english language