PROC25
Jump to navigation
Jump to search
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:
- 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
Steps
Responsible | Action | Notes | |
---|---|---|---|
1 | Product team | submits a ggus ticket for the "EGI Software provisioning support" support unit with the following information
|
|
2 | Stage rollout manager | product release is injected in the EGI SW provisioning infrastructure
|
This action must be completed within 5 working days after step 1. |
3 | |||