Talk:Release management

From Wikipedia, the free encyclopedia
Jump to: navigation, search
WikiProject Software / Computing  (Rated Start-class)
WikiProject icon This article is within the scope of WikiProject Software, a collaborative effort to improve the coverage of software on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.
Start-Class article Start  This article has been rated as Start-Class on the project's quality scale.
 ???  This article has not yet received a rating on the project's importance scale.
Taskforce icon
This article is supported by WikiProject Computing.
 

Merging[edit]

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

Hello

I also share the opintion to NOT merge the two articles.

However I do understand that both articles are somewhat overlapping and should be re-written as follows:

- One article should focus specifically in Release Management within Software Engineering - The other article should focus on Release Mangement from an ITSM Point of view and should therefore also be renamed to "Release Management (ITSM) like a similar article exists e.g. for "Change Management (ITSM)"

This would clearly separate the two articles from each other, each providing the details for it's specific need.

This is basically nothing else than a short summary of the information below.

--May08pub (talk) 14:36, 6 August 2008 (UTC) Hello. I would concur on not merging. ==Vote not to merge==

Simply stated there are definite and distinguishing differences between Release Management and "a" Release Management Method.

Release Management is a discipline in a field of work such as Information Technology (IT) or Manufacturing etc.. which involves the use of Standards, Processed, Procedures, Frameworks and/or "Methods", whereas a method is:

  1. a procedure, technique, or way of doing something, esp. in accordance with a definite plan: There are three possible methods of repairing this motor.
  2. a manner or mode of procedure, esp. an orderly, logical, or systematic way of instruction, inquiry, investigation, experiment, presentation, etc.: the empirical method of inquiry.
  3. order or system in doing anything: to work with method.
  4. orderly or systematic arrangement, sequence, or the like.
  5. the Method. Also called Stanislavski Method, Stanislavski System. a theory and technique of acting in which the performer identifies with the character to be portrayed and renders the part in a naturalistic, nondeclamatory, and highly individualized manner.

Definition- Method

Release Management can involve the implementation and use of particular or specific methods, however; a method can not perform the roles & responsibilities associated with a Discipline as a method has no skills or competencies which it can exercise as it is not human. Release Management is the discipline Humans practice in thier respective fields of work employing Release Management methods - not the opposite way.

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




WikiProject Method engineering    (Inactive)
WikiProject icon This article is within the scope of WikiProject Method engineering, a project which is currently considered to be inactive.
 

Not copyvio after all[edit]

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)

Was not the copyright infringement angle already discussed and decided? Why is this marked as copyvio again? 173.50.233.227 (talk) 15:39, 7 April 2010 (UTC)

I believe User:Scoudi is the same person as Sudesh Oudi, one of the authors of the work which is referenced as possible copyvio source. You will notice the person also self-contributed extremely similar images under CC here as well. 173.50.233.227 (talk) 15:52, 7 April 2010 (UTC)

Vote decision[edit]

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?


Update[edit]

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)

Conflict with ITIL language[edit]

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)

Vote for merger with Release Management Method[edit]

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 (talkcontribs) 16:49, 1 April 2008 (UTC)

Software Release Management involves the process of Managing the Entire Release Process. In terms of Agile Release Manager is the Pig of Release Process. Hence it is imperative that this be dealt with a separate article exclusively rather than merging it. My vote is do not merge.--> — Preceding unsigned comment added by PuneetMathur (talkcontribs) 10:10, 14 September 2011 (UTC)

Copyright problem removed[edit]

One or more portions of this article duplicated other source(s). The material was copied from: http://www.itsmwatch.com/itil/article.php/11700_3680776_2. 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)