[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"detail-sidebar-cat-0-en-105":3,"doc-seo-292597-105":59,"doc-detail-292597-en":130},{"code":4,"msg":5,"data":6},0,"success",[7,13,18,23,28,33,38,43,48,51,55],{"id":8,"doc_module":4,"doc_module_name":9,"category_name":10,"show_sort_weight":11,"slug":12},1,"Document","Story & Novel",90,"story-novel",{"id":14,"doc_module":4,"doc_module_name":9,"category_name":15,"show_sort_weight":16,"slug":17},2,"Literature",80,"literature",{"id":19,"doc_module":4,"doc_module_name":9,"category_name":20,"show_sort_weight":21,"slug":22},4,"Exam",70,"exam",{"id":24,"doc_module":4,"doc_module_name":9,"category_name":25,"show_sort_weight":26,"slug":27},5,"Comic",60,"comic",{"id":29,"doc_module":4,"doc_module_name":9,"category_name":30,"show_sort_weight":31,"slug":32},6,"Technology",50,"technology",{"id":34,"doc_module":4,"doc_module_name":9,"category_name":35,"show_sort_weight":36,"slug":37},7,"Healthcare",40,"healthcare",{"id":39,"doc_module":4,"doc_module_name":9,"category_name":40,"show_sort_weight":41,"slug":42},8,"Research & Report",30,"research-report",{"id":44,"doc_module":4,"doc_module_name":9,"category_name":45,"show_sort_weight":46,"slug":47},9,"Religion & Spirituality",20,"religion-spirituality",{"id":46,"doc_module":4,"doc_module_name":9,"category_name":49,"show_sort_weight":46,"slug":50},"World Cup","world-cup",{"id":52,"doc_module":4,"doc_module_name":9,"category_name":53,"show_sort_weight":52,"slug":54},10,"Lifestyle","lifestyle",{"id":56,"doc_module":4,"doc_module_name":9,"category_name":57,"show_sort_weight":24,"slug":58},19,"General","general",{"code":4,"msg":60,"data":61},"ok",{"site_id":62,"language":63,"slug":64,"title":65,"keywords":66,"description":67,"schema_data":68,"social_meta":123,"head_meta":125,"extra_data":127,"updated_unix":129},105,"en","release-management-plan-api-version-preparing-for-v120","Release Management Plan - API Version Preparing for v12.0","","Release Management Plan for IRWIN defines how versioned releases move through TEST, OAT, and Production. It describes the promotion gates tied to testing and acceptance, plus the purpose of stable root and the next folder used to expose under-development software before integration testing. The plan outlines release workflows for PATCH/HOTFIX and upcoming v12.0 readiness, including notification to the community and a 48-hour testing window after promotion. It also covers procedures for terms, personnel, tools, quality assurance, testing types, contingency planning, and release documentation, with revision history and target timeline.",{"@graph":69,"@context":122},[70,84,105],{"@type":71,"itemListElement":72},"BreadcrumbList",[73,77,79,82],{"item":74,"name":75,"@type":76,"position":8},"https://docshare.wps.com","Home","ListItem",{"item":78,"name":9,"@type":76,"position":14},"https://docshare.wps.com/document/",{"item":80,"name":40,"@type":76,"position":81},"https://docshare.wps.com/document/research-report/",3,{"item":83,"name":65,"@type":76,"position":19},"https://docshare.wps.com/document/release-management-plan-api-version-preparing-for-v120/292597/",{"url":83,"name":65,"@type":85,"image":86,"author":91,"headline":65,"publisher":94,"fileFormat":97,"inLanguage":63,"description":67,"dateModified":98,"datePublished":99,"encodingFormat":97,"isAccessibleForFree":100,"interactionStatistic":101},"DigitalDocument",{"url":87,"@type":88,"width":89,"height":90},"https://docshare.wps.com/thumbnails/release-management-plan-api-version-preparing-for-v120/292597.png","ImageObject",300,407,{"name":92,"@type":93},"\tCallum ","Person",{"url":74,"name":95,"@type":96},"DocShare","Organization","application/pdf","2026-11-04","2026-09-17",true,{"@type":102,"interactionType":103,"userInteractionCount":39},"InteractionCounter",{"@type":104},"ViewAction",{"@type":106,"mainEntity":107},"FAQPage",[108,114,118],{"name":109,"@type":110,"acceptedAnswer":111},"What are the three IRWIN API environments and how are release packages promoted?","Question",{"text":112,"@type":113},"IRWIN uses TEST, OAT (Operational Acceptance Testing), and Production. During a release, the package is promoted TEST → OAT → Production only after appropriate testing and acceptance.","Answer",{"name":115,"@type":110,"acceptedAnswer":116},"What is the difference between the stable root and the next folder?",{"text":117,"@type":113},"The stable root holds currently released software for Production deployments. The next folder contains under-development software so it can be exposed ahead of integration testing while still maintaining released software.",{"name":119,"@type":110,"acceptedAnswer":120},"How does the workflow handle PATCH or HOTFIX deployments?",{"text":121,"@type":113},"Released software receiving a PATCH/HOTFIX is sent to TEST, where the IRWIN Core Team performs unit tests. After passing, it is promoted to OAT, then Extended Systems testing occurs, and the release is finally promoted to Production after successful OAT results.","https://schema.org",{"og:url":83,"og:type":124,"og:title":65,"og:site_name":95,"og:description":67},"article",{"robots":126,"canonical":83},"index,follow",{"doc_id":128,"site_id":62},292597,1789653048,{"code":4,"msg":5,"data":131},{"doc_id":128,"user_id":132,"nickname":92,"user_avatar":133,"doc_module":4,"category_id":39,"category_name":40,"doc_title":65,"doc_description":67,"doc_content":134,"file_id":135,"file_url":136,"file_type":137,"file_size":138,"view_count":39,"is_deleted":4,"is_public":8,"is_downloadable":8,"audit_status":8,"page_count":44,"language":139,"language_code":63,"site_id":62,"html_lang":63,"table_of_contents":140,"faqs":141,"seo_title":142,"seo_description":67,"update_tm":129,"read_time":143,"preview_page_count":4},137451211410,"https://ap-avatar.wpscdn.com/avatar/2000bb0a9246f588df?x-image-process=image/resize,m_fixed,w_180,h_180&k=1786362646172706240","Release Management Plan  \nPrepared By: IRWIN Core Team Last Modification Date: 5/29/2026  \nAPI Version: Preparing for v12.0  \nDocument Revisions  \n\n| Publish Date | Description | Person Responsible |\n| --- | --- | --- |\n| 6/5/13 | Initial Draft of Plan | Craig Morgan |\n| 3/15/16 | Revised Release Management Plan | Alex Laughton |\n| 6/8/16 | Update Plan to align with current V4 Goals and Objectives | Jaymee Fojtik / Craig Morgan |\n| 10/15/16 | Update Milestones | Craig Morgan |\n| 6/23/2017 | Update Plan to align with current V5 Goals and Objectives | Jaymee Fojtik / Ryan Perkl |\n| 11/2/2018 | Update plan to address v5.1 and v6 release plan. | Luci Coleman |\n| 5/23/2019 | Update plan for v6 release plan. | Luci Coleman |\n| 6/18/2019 | Final plan for v6 . | Luci Coleman |\n| 10/28/2020 | Update plan for v7 release. | Mary Koran |\n| 11/13/2020 | Final plan for v7 . | Mary Koran |\n| 10/20/2021 | Update plan for v7.1 release. | Mary Koran |\n| 12/17/2021 | Final plan for v7.1 . | Mary Koran |\n| 09/30/2022 | Update plan for v8.0 release. | Mary Koran |\n| 10/14/2022 | Final plan for v8.0 . | Mary Koran |\n| 09/18/2023 | Update plan for v9.0 release. | Mary Koran |\n| 04/23/2024 | Update plan for v10.0 release. | Mary Koran |\n| 04/26/2024 | Final plan for v10.0 . | Mary Koran |\n| 04/21/2025 | Update plan for v11.0 release. | Mary Koran |\n| 04/25/2025 | Final plan for v11.0 . | Mary Koran |\n| 05/18/2026 | Update plan for v12.0 release. | Mary Koran |\n\nContents  \n1 Introduction................................................................................................................................ 4  \n1.1 IRWIN API Environments ....................................................................................................................4  \n1.2 Release Workflows ............................................................................................................................ 4  \n1.2.1 root .......................................................................................................................................... 4  \n1.2.2 next ...........................................................................................................................................5  \n2 Target Release Timeline............................................................................................................... 5  \n3 Release Management Procedures ................................................................................................. 6  \n3.1 Terms ............................................................................................................................................... 6  \n3.2 Personnel .......................................................................................................................................... 7  \n3.3 Tools ................................................................................................................................................ 8  \n3.4 Quality Assurance ............................................................................................................................. 8  \n3.4.1 Types of Testing........................................................................................................................ 8  \n3.4.2 Contingency Planning ............................................................................................................... 9  \n3.4.3 Release Documentation ............................................................................................................ 9  \n1 Introduction  \n1.1 IRWIN API Environments  \nIRWIN has three API environments: TEST, Operational Acceptance Testing (OAT), and Production. During any release, the release package is promoted from TEST to OAT to Production. Each promotion only occurs after appropriate testing and acceptance.  \nIn October 2018, the IRWIN Core Team introduced a next folder into the TEST and OAT environments in an effort to expose under-development software ","cbCaif2SZZ6wpm82","https://ap.wps.com/l/cbCaif2SZZ6wpm82","pdf",457217,"English","# Introduction\n## IRWIN API Environments\n## Release Workflows\n### root\n### next\n# Target Release Timeline\n# Release Management Procedures\n## Terms\n## Personnel\n## Tools\n## Quality Assurance\n### Types of Testing\n### Contingency Planning\n### Release Documentation","[{\"question\":\"What are the three IRWIN API environments and how are release packages promoted?\",\"answer\":\"IRWIN uses TEST, OAT (Operational Acceptance Testing), and Production. During a release, the package is promoted TEST → OAT → Production only after appropriate testing and acceptance.\"},{\"question\":\"What is the difference between the stable root and the next folder?\",\"answer\":\"The stable root holds currently released software for Production deployments. The next folder contains under-development software so it can be exposed ahead of integration testing while still maintaining released software.\"},{\"question\":\"How does the workflow handle PATCH or HOTFIX deployments?\",\"answer\":\"Released software receiving a PATCH/HOTFIX is sent to TEST, where the IRWIN Core Team performs unit tests. After passing, it is promoted to OAT, then Extended Systems testing occurs, and the release is finally promoted to Production after successful OAT results.\"}]","Release Management Plan - API Version Preparing for v12.0 | PDF",23]