Knowledge Base Wiki

Search for LIMS content across all our Wiki Knowledge Bases.

Type a search term to find related articles by LIMS subject matter experts gathered from the most trusted and dynamic collaboration tools in the laboratory informatics industry.

Common names of versions during different stages in software development

Release management is the process of managing, planning, scheduling and controlling a software build through different stages and environments; it includes testing and deploying software releases.[1][2]

Relationship with processes

Organizations that have adopted agile software development are seeing much higher quantities of releases[citation needed]. With the increasing popularity of agile development a new approach to software releases known as continuous delivery is starting to influence how software transitions from development to a release.[3] One goal of continuous delivery and DevOps is to release more reliable applications faster and more frequently. The movement of the application from a "build" through different environments to production as a "release" is part of the continuous delivery pipeline.[4] Release managers are beginning to utilize tools such as application release automation and continuous integration tools to help advance the process of continuous delivery and incorporate a culture of DevOps by automating a task so that it can be done more quickly, reliably, and is repeatable. More software releases have led to increased reliance on release management and automation tools to execute these complex application release processes.[5]

Relationship with ITIL/ITSM

In organizations that manage IT operations using the IT service management paradigm, specifically the ITIL framework, release management will be guided by ITIL concepts and principles. There are several formal ITIL processes that are related to release management, primarily the release and deployment management process, which "aims to plan, schedule and control the movement of releases to test and live environments",[6] and the change enablement process.[7] In ITIL organizations, releases tend to be less frequent than in an agile development environment. Release processes are managed by IT operations teams using IT service management ticketing systems, with less focus on automation of release processes.[8]

References

  1. ^ Humble, Jez; Farley, David (2011). Continuous Delivery: reliable software releases through build, test, and deployment automation. Pearson Education Inc. p. 110. ISBN 978-0-321-60191-9.
  2. ^ Bays, Michael E. (1999). Software release methodology. Upper Saddle River, N.J.: Prentice Hall PTR. ISBN 0-13-636564-7. OCLC 41411901.
  3. ^ Ambler, Scott W. (12 February 2014). "We need more Agile IT Now!". Dr. Dobb's the World of Software Development. San Francisco: UBM.
  4. ^ Humble, Jez; Farley, David (2011). Continuous Delivery: reliable software releases through build, test, and deployment automation. Pearson Education Inc. pp. 255–257. ISBN 978-0-321-60191-9.
  5. ^ Best Practices in Change, Configuration and Release Management (Report). Gartner. 14 July 2010.
  6. ^ "ITIL Release and Deployment Management". IT Process Maps. Germany: Stefan and Andrea Kempter. 15 May 2016.
  7. ^ Karu, Kaimar (1 Dec 2023). "ITIL 4 Practitioner: Change Enablement – change with customer value in mind". Axelos Resource Hub. UK: Axelos.
  8. ^ "ITIL/ITSM Release Management Practices". Release Management Wiki. USA: Electric Cloud.
source: https://en.wikipedia.org/wiki/Release_management