Alert.png The wiki is deprecated and due to be decommissioned by the end of September 2022.
The content is being migrated to other supports, new updates will be ignored and lost.
If needed you can get in touch with EGI SDIS team using operations @ egi.eu.

Difference between revisions of "PROC25"

From EGIWiki
Jump to navigation Jump to search
(Created page with "{{Template:Op menubar}} {{Template:Doc_menubar}} {{TOC_right}} {{Ops_procedures |Doc_title = Middleware release procedure |Doc_link = https://wiki.egi.eu/wiki/PROC25 |Version =...")
 
Line 12: Line 12:
|Procedure_statement = The procedure describes the process of adding a new produc release to the software provisioning process and releasing it in UMD/CMD.  
|Procedure_statement = The procedure describes the process of adding a new produc release to the software provisioning process and releasing it in UMD/CMD.  
}}
}}
= Overview  =
The procedure describes the process to add a new product, or a new release of an existing product to the UMD/CMD repositories.
= Definitions  =
Please refer to the [[Glossary|EGI Glossary]] for the definitions of the terms used in this procedure.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", “MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119.
= Entities involved in the procedure  =
* ''Product team'': The developer, or the team of developers, who is responsible for maintaining a software and producing the new releases.
= Requirements  =
The prerequesites are:
*The product team releasing the software has already provided the information to fill the product ID Card.
*Development team should follow [https://wiki.egi.eu/wiki/Instructions_for_Production_Tools_teams#Release_and_deployment_management https://wiki.egi.eu/wiki/Instructions_for_Production_Tools_teams#Release_and_deployment_management]
= Steps =
{| width="906" height="305" class="wikitable"
|-
! <br>
! Responsible
! Action
! Notes
|- valign="top"
|1
|Product team
|submits a ggus ticket for the "EGI Software provisioning support" support unit with the following information
* Product release and version number
* Link to the release notes
* Full list of packages that compose the release, and that need to be released in UMD
|
|-
|2
|Stage rollout manager
|product release is injected in the EGI SW provisioning infrastructure
* One or more RT tickets are created to track the progresses of the UMD software provisioning of the new product release
* Reply to the GGUS ticket with the link to the RT and close as 'solved' the GGUS ticket
* The RT ticket is then used to track the progress of the software in the release process
|This action must be completed within ''5 working days'' after step 1.
|-
|3
|
|
|
|-
|
|
|
|
|-
|
|
|
|
|-
|
|
|
|
|-
|
|
|
|
|-
|
|
|
|
|-
|
|
|
|
|-
|
|
|
|
|-

Revision as of 17:25, 21 July 2016

Main EGI.eu operations services Support Documentation Tools Activities Performance Technology Catch-all Services Resource Allocation Security


Documentation menu: Home • Manuals • Procedures • Training • Other • Contact ► For: VO managers • Administrators



Title Middleware release procedure
Document link https://wiki.egi.eu/wiki/PROC25
Last modified 0.1
Policy Group Acronym OMB
Policy Group Name Operations Management Board
Contact Group operations at egi.eu
Document Status DRAFT
Approved Date
Procedure Statement The procedure describes the process of adding a new produc release to the software provisioning process and releasing it in UMD/CMD.
Owner Owner of procedure


Overview

The procedure describes the process to add a new product, or a new release of an existing product to the UMD/CMD repositories.

Definitions

Please refer to the EGI Glossary for the definitions of the terms used in this procedure.

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", “MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119.

Entities involved in the procedure

  • Product team: The developer, or the team of developers, who is responsible for maintaining a software and producing the new releases.

Requirements

The prerequesites are:

Steps


 Responsible Action Notes
1 Product team submits a ggus ticket for the "EGI Software provisioning support" support unit with the following information
  • Product release and version number
  • Link to the release notes
  • Full list of packages that compose the release, and that need to be released in UMD
2 Stage rollout manager product release is injected in the EGI SW provisioning infrastructure
  • One or more RT tickets are created to track the progresses of the UMD software provisioning of the new product release
  • Reply to the GGUS ticket with the link to the RT and close as 'solved' the GGUS ticket
  • The RT ticket is then used to track the progress of the software in the release process
 This action must be completed within 5 working days after step 1.
3
Retrieved from "https://wiki.egi.eu/w/index.php?title=PROC25&oldid=88845"