發佈管理：修订间差异

删除的内容添加的内容

行内

2024年2月9日 (五) 01:38的最新版本

發布管理或作發行管理、釋出管理、上線管理，是透過不同階段和環境以管理、規劃、排程、和管制軟體構建的流程; 包括測試和部署軟體版本^[1]。

背景

發布管理是軟體工程領域一個相對較新但迅速發展的學科。隨著軟體系統、軟體開發過程、和資源變得越來越分散，它們總是變得更加專業化和複雜化。此外，軟體產品（尤其是網路應用程式）通常處於開發、測試、和發布的持續循環中，常常在日益複雜、不斷發展的平台上運行。這樣的系統需要專門的資源來監督開發、測試、部署、和支援的整合和流程。

與持續交付、DevOps、和敏捷軟體開發的關係

已經採用敏捷軟體開發的組織正在看到更多的版本。隨著敏捷開發的日益流行，被稱為持續交付的軟體版本的新方法，開始影響軟體如何從開發過渡到發布^[2]。持續交付和 DevOps 的一個目標是更快、更頻繁地發布更可靠的應用程式。應用程式從「構建」透過不同的環境移動到生產「發布」，是持續交付管道的一部分^[3]。發布經理開始利用諸如應用程式發布自動化和持續整合工具等工具來幫助推進持續交付流程，並通過自動執行任務來整合DevOps文化，從而使其可以更快、更可靠地完成，並且是可重複的。更多的軟體發布已經導致越來越依賴發布管理和自動化工具來執行這些複雜的應用程式發布流程^[4]。

與企業發布管理的關係

發布管理著重於從單一專案或相關專案集合從開發到測試和發布的過渡。企業發布管理（ERM）則側重於在較大型組織內協調各個發布。擁有多個應用程式開發群體的組織，可能需要經過數月或數年的高度協調的一系列發布，才能實現大規模系統。ERM 涉及多個發布經理協調一致的工作，在IT組合的背景下同步發布。

與ITIL/ITSM的關係

在使用資訊科技〈IT〉服務管理範式（特別是ITIL信息技術基礎架構庫框架）管理IT運營的組織中，將以ITIL概念和原則來指引發布管理。有幾個與發布管理相關的正式ITIL流程，主要是發布和部署管理流程（其目的是計劃、調度和、控制發佈到測試和生活環境的移動〉^[5]和變更管理流程^[6]。在ITIL組織中，發布的頻率往往低於敏捷開發環境。發布流程由IT運營團隊使用IT服務管理票務系統進行管理，而不太關注發布流程的自動化^[7]。

參見

參考文獻

^ Humble, Jez; Farley, David. Continuous Delivery: reliable software releases through build, test, and deployment automation. Pearson Education Inc. 2011: 110. ISBN 978-0-321-60191-9.
^ Ambler, Scott W. We need more Agile IT Now!. Dr. Dobb’s The world of software Development (San Francisco: UBM). 12 February 2014 [2017-11-28]. （原始内容存档于2020-10-20）.
^ Humble, Jez; Farley, David. Continuous Delivery: reliable software releases through build, test, and deployment automation. Pearson Education Inc. 2011: 255–257. ISBN 978-0-321-60191-9.
^ Best Practices in Change, Configuration and Release Management (报告). Gartner. 14 July 2010.
^ ITIL Release and Deployment Management. IT Process Maps (Germany: Stefan and Andrea Kempter). 15 May 2016 [2017-11-28]. （原始内容存档于2020-12-04）.
^ Murphy, Vawns. Change vs Release Management. The ITSM Review (UK: Enterprise Opinions Limited). 2 Feb 2016 [2017-11-28]. （原始内容存档于2019-04-16）.
^ ITIL/ITSM Release Management Practices. Release Management Wiki (USA: Electric Cloud). [2017-11-28]. （原始内容存档于2017-12-01）.

外部連結

[1] Humble, Jez; Farley, David. Continuous Delivery: reliable software releases through build, test, and deployment automation. Pearson Education Inc. 2011: 110. ISBN 978-0-321-60191-9.

[2] Ambler, Scott W. We need more Agile IT Now!. Dr. Dobb’s The world of software Development (San Francisco: UBM). 12 February 2014 [2017-11-28]. （原始内容存档于2020-10-20）.

[3] Humble, Jez; Farley, David. Continuous Delivery: reliable software releases through build, test, and deployment automation. Pearson Education Inc. 2011: 255–257. ISBN 978-0-321-60191-9.

[4] Best Practices in Change, Configuration and Release Management (报告). Gartner. 14 July 2010.

[5] ITIL Release and Deployment Management. IT Process Maps (Germany: Stefan and Andrea Kempter). 15 May 2016 [2017-11-28]. （原始内容存档于2020-12-04）.

[6] Murphy, Vawns. Change vs Release Management. The ITSM Review (UK: Enterprise Opinions Limited). 2 Feb 2016 [2017-11-28]. （原始内容存档于2019-04-16）.

[7] ITIL/ITSM Release Management Practices. Release Management Wiki (USA: Electric Cloud). [2017-11-28]. （原始内容存档于2017-12-01）.

[1]

[2]

[3]

[4]

[5]

[6]

[7]

@@ 第1行： / 第1行： @@
 {{noteTA|G1=IT}}
 {{cleanup-jargon|time=2017-11-28T06:40:58+00:00}}
-'''發布管理'''或作'''發行管理'''、'''釋出管理'''、'''上線管理'''，是透過不同階段和環境以管理、規劃、排程、和管制軟體構建的流程; 包括測試和部署[[軟體版本週期|軟體版本]]<ref>{{cite book |last=Humble |first=Jez |last2=Farley |first2=David |date=2011 |title=Continuous Delivery: reliable software releases through build, test, and deployment automation |publisher= Pearson Education Inc. |page=110 |isbn=978-0-321-60191-9}}</ref>。
+'''發布管理'''或作'''發行管理'''、'''釋出管理'''、'''上線管理'''，是透過不同階段和環境以管理、規劃、排程、和管制軟體構建的流程; 包括測試和部署[[軟體版本週期|軟體版本]]<ref>{{cite book |last=Humble |first=Jez |last2=Farley |first2=David |date=2011 |title=Continuous Delivery: reliable software releases through build, test, and deployment automation |url=https://archive.org/details/continuousdelive00humb |publisher= Pearson Education Inc. |page=[https://archive.org/details/continuousdelive00humb/page/n496 110] |isbn=978-0-321-60191-9}}</ref>。
 == 背景 ==
@@ 第9行： / 第9行： @@
 ==與持續交付、DevOps、和敏捷軟體開發的關係==
-已經採用[[敏捷軟體開發]]的組織正在看到更多的版本。隨著敏捷開發的日益流行，被稱為[[持續交付]]的軟體版本的新方法，開始影響軟體如何從開發過渡到發布<ref>{{cite journal |last= Ambler |first= Scott W. |date= 12 February 2014 |title= We need more Agile IT Now! |url= http://www.drdobbs.com/architecture-and-design/we-need-more-agile-it-now/240169361?queryText=Release%2Bmanagement  |journal= Dr. Dobb’s The world of software Development |location= San Francisco |publisher= UBM}}</ref>。持續交付和 [[DevOps]] 的一個目標是更快、更頻繁地發布更可靠的應用程式。應用程式從「構建」透過不同的環境移動到生產「發布」，是持續交付管道的一部分<ref>{{cite book |last=Humble |first=Jez |last2=Farley |first2=David |date=2011 |title=Continuous Delivery: reliable software releases through build, test, and deployment automation |publisher= Pearson Education Inc. |pages=255–257 |isbn=978-0-321-60191-9}}</ref>。發布經理開始利用諸如[[應用程式發布自動化]]和[[持續整合]]工具等工具來幫助推進持續交付流程，並通過自動執行任務來整合DevOps文化，從而使其可以更快、更可靠地完成，並且是可重複的。更多的軟體發布已經導致越來越依賴發布管理和自動化工具來執行這些複雜的應用程式發布流程<ref>{{cite report |title=Best Practices in Change, Configuration and Release Management  |publisher=Gartner |date=14 July 2010}}</ref>。
+已經採用[[敏捷軟體開發]]的組織正在看到更多的版本。隨著敏捷開發的日益流行，被稱為[[持續交付]]的軟體版本的新方法，開始影響軟體如何從開發過渡到發布<ref>{{cite journal |last= Ambler |first= Scott W. |date= 12 February 2014 |title= We need more Agile IT Now! |url= http://www.drdobbs.com/architecture-and-design/we-need-more-agile-it-now/240169361?queryText=Release%2Bmanagement |journal= Dr. Dobb’s The world of software Development |location= San Francisco |publisher= UBM |access-date= 2017-11-28 |archive-date= 2020-10-20 |archive-url= https://web.archive.org/web/20201020201213/https://www.drdobbs.com/architecture-and-design/we-need-more-agile-it-now/240169361?queryText=Release%2Bmanagement |dead-url= no }}</ref>。持續交付和 [[DevOps]] 的一個目標是更快、更頻繁地發布更可靠的應用程式。應用程式從「構建」透過不同的環境移動到生產「發布」，是持續交付管道的一部分<ref>{{cite book |last=Humble |first=Jez |last2=Farley |first2=David |date=2011 |title=Continuous Delivery: reliable software releases through build, test, and deployment automation |url=https://archive.org/details/continuousdelive0000humb |publisher= Pearson Education Inc. |pages=[https://archive.org/details/continuousdelive0000humb/page/255 255]–257 |isbn=978-0-321-60191-9}}</ref>。發布經理開始利用諸如[[應用程式發布自動化]]和[[持續整合]]工具等工具來幫助推進持續交付流程，並通過自動執行任務來整合DevOps文化，從而使其可以更快、更可靠地完成，並且是可重複的。更多的軟體發布已經導致越來越依賴發布管理和自動化工具來執行這些複雜的應用程式發布流程<ref>{{cite report |title=Best Practices in Change, Configuration and Release Management  |publisher=Gartner |date=14 July 2010}}</ref>。
 == 與企業發布管理的關係 ==
@@ 第17行： / 第17行： @@
 == 與ITIL/ITSM的關係 ==
-在使用[[資訊科技]]〈IT〉服務管理範式（特別是[[信息技術基礎架構庫|ITIL]]框架）管理IT運營的組織中，將以ITIL概念和原則來指引發布管理。有幾個與發布管理相關的正式ITIL流程，主要是發布和部署管理流程（其目的是計劃、調度和、控制發佈到測試和生活環境的移動〉<ref>{{cite journal |date= 15 May 2016 |title= ITIL Release and Deployment Management |url= http://wiki.en.it-processmaps.com/index.php/Release_and_Deployment_Management  |journal= IT Process Maps |location= Germany |publisher= Stefan and Andrea Kempter}}</ref>和變更管理流程<ref>{{cite journal |last=Murphy |first=Vawns |date= 2 Feb 2016 |title= Change vs Release Management |url= http://www.theitsmreview.com/2016/02/change-release-management/ |journal= The ITSM Review |location= UK |publisher= Enterprise Opinions Limited}}</ref>。在ITIL組織中，發布的頻率往往低於敏捷開發環境。發布流程由IT運營團隊使用IT服務管理票務系統進行管理，而不太關注發布流程的自動化<ref>{{cite journal |title= ITIL/ITSM Release Management Practices |url= http://electric-cloud.com/wiki/pages/viewpage.action?pageId=2293943 |journal= Release Management Wiki |location= USA |publisher= Electric Cloud}}</ref>。
+在使用[[資訊科技]]〈IT〉服務管理範式（特別是ITIL[[信息技術基礎架構庫]]框架）管理IT運營的組織中，將以ITIL概念和原則來指引發布管理。有幾個與發布管理相關的正式ITIL流程，主要是發布和部署管理流程（其目的是計劃、調度和、控制發佈到測試和生活環境的移動〉<ref>{{cite journal |date= 15 May 2016 |title= ITIL Release and Deployment Management |url= http://wiki.en.it-processmaps.com/index.php/Release_and_Deployment_Management |journal= IT Process Maps |location= Germany |publisher= Stefan and Andrea Kempter |access-date= 2017-11-28 |archive-date= 2020-12-04 |archive-url= https://web.archive.org/web/20201204012329/https://wiki.en.it-processmaps.com/index.php/Release_and_Deployment_Management |dead-url= no }}</ref>和變更管理流程<ref>{{cite journal |last= Murphy |first= Vawns |date= 2 Feb 2016 |title= Change vs Release Management |url= http://www.theitsmreview.com/2016/02/change-release-management/ |journal= The ITSM Review |location= UK |publisher= Enterprise Opinions Limited |access-date= 2017-11-28 |archive-date= 2019-04-16 |archive-url= https://web.archive.org/web/20190416073716/http://www.theitsmreview.com/2016/02/change-release-management/ |dead-url= yes }}</ref>。在ITIL組織中，發布的頻率往往低於敏捷開發環境。發布流程由IT運營團隊使用IT服務管理票務系統進行管理，而不太關注發布流程的自動化<ref>{{cite journal |title= ITIL/ITSM Release Management Practices |url= http://electric-cloud.com/wiki/pages/viewpage.action?pageId=2293943 |journal= Release Management Wiki |location= USA |publisher= Electric Cloud |author=  |access-date= 2017-11-28 |archive-url= https://web.archive.org/web/20171201034519/http://electric-cloud.com/wiki/pages/viewpage.action?pageId=2293943 |archive-date= 2017-12-01 |dead-url= yes }}</ref>。
 ==參見==
@@ 第36行： / 第36行： @@
 ==外部連結==
 {{wikibooks|發布管理}}
-*[https://books.google.com/books?id=BR9ppkdnIrQC&pg=PA193&lpg=PA193&dq=release+manager&source=web&ots=M-ejUHsZW6&sig=zwuyg_J60Xwcr77VXjReliQ5WEI&hl=en&sa=X&oi=book_result&resnum=9&ct=result Project Management: Best Practices for IT Professionals]
+*[https://books.google.com/books?id=BR9ppkdnIrQC&pg=PA193&lpg=PA193&dq=release+manager&source=web&ots=M-ejUHsZW6&sig=zwuyg_J60Xwcr77VXjReliQ5WEI&hl=en&sa=X&oi=book_result&resnum=9&ct=result Project Management: Best Practices for IT Professionals] {{Wayback|url=https://books.google.com/books?id=BR9ppkdnIrQC&pg=PA193&lpg=PA193&dq=release+manager&source=web&ots=M-ejUHsZW6&sig=zwuyg_J60Xwcr77VXjReliQ5WEI&hl=en&sa=X&oi=book_result&resnum=9&ct=result |date=20130528091437 }}
-*[http://www.itsmwatch.com/itil/article.php/3680776 Release Management - Where to Start?]
+*[http://www.itsmwatch.com/itil/article.php/3680776 Release Management - Where to Start?] {{Wayback|url=http://www.itsmwatch.com/itil/article.php/3680776 |date=20110929230139 }}
-*[http://wiki.en.it-processmaps.com/index.php/Release_and_Deployment_Management Release and Deployment Management in the ITIL Framework]
+*[http://wiki.en.it-processmaps.com/index.php/Release_and_Deployment_Management Release and Deployment Management in the ITIL Framework] {{Wayback|url=http://wiki.en.it-processmaps.com/index.php/Release_and_Deployment_Management |date=20201204012329 }}
-*[http://electric-cloud.com/wiki/display/releasemanagement/Release+Management Release Management Wiki - Compilation of Current Resources about All Aspects of Release Management]
+*[https://web.archive.org/web/20171129173023/http://electric-cloud.com/wiki/display/releasemanagement/Release+Management Release Management Wiki - Compilation of Current Resources about All Aspects of Release Management]
-*[https://books.google.com/books?id=zUTiHzyyDLwC&pg=PT273&lpg=PT273&dq=release+manager&source=web&ots=dJwEC7lz_Z&sig=PXBGdOj_4BURbb98N9RpNk1xf18&hl=en&sa=X&oi=book_result&resnum=1&ct=result Managing Software Projects By Frank F. Tsui]
+*[https://books.google.com/books?id=zUTiHzyyDLwC&pg=PT273&lpg=PT273&dq=release+manager&source=web&ots=dJwEC7lz_Z&sig=PXBGdOj_4BURbb98N9RpNk1xf18&hl=en&sa=X&oi=book_result&resnum=1&ct=result Managing Software Projects By Frank F. Tsui] {{Wayback|url=https://books.google.com/books?id=zUTiHzyyDLwC&pg=PT273&lpg=PT273&dq=release+manager&source=web&ots=dJwEC7lz_Z&sig=PXBGdOj_4BURbb98N9RpNk1xf18&hl=en&sa=X&oi=book_result&resnum=1&ct=result |date=20130528093337 }}
-*[https://www.swc.rwth-aachen.de/course/current-trends-in-release-engineering-2016/ "Current Trends in Release Engineering 2016" - Academic Course by Software Construction Research Group, RWTH Aachen, Germany]
+*[https://www.swc.rwth-aachen.de/course/current-trends-in-release-engineering-2016/ "Current Trends in Release Engineering 2016" - Academic Course by Software Construction Research Group, RWTH Aachen, Germany] {{Wayback|url=https://www.swc.rwth-aachen.de/course/current-trends-in-release-engineering-2016/ |date=20210127220628 }}
 [[Category:軟體專案管理]]