Here you will find the procedures describing how Release and Deployment Management occurs for the EGI Central services.

RDM Policies

TitleStatementPolicy statusOwnerApproval status
Release PolicyThe goal of Release Management is to plan and oversee the implementation of approved Changes into production.

FINALISED

Catalin Condurache

APPROVED

RDM Procedures

TitleStatementProcedure statusOwnerApproval status
RDM1 Emergency release process

An emergency release consists in the releasing of one product, or a set of products, with the targeted goal of solving a specific problem that affects the EGI infrastructure. To qualify for an emergency release the problem should be classified in at least one of the following categories:

  • A critical security patch
  • A critical bug affecting multiple resource centres

Emergency releases are deployed by the services providers and apply to the services listed in the EGI Service Portfolios that are owned by the EGI Foundation.

FINALISED

Catalin Condurache

APPROVED

RDM2 Regular release process

This procedure applies to regular releases of the centrally-provided production services that need to be fully built, tested and deployed.

This may be either:

  • a high risk/impact change needing careful testing
  • a set of linked changes to test and deploy together
  • lower priority changes bundled together to reduce downtime.

FINALISED

Catalin Condurache

APPROVED

RDM3 Lightweight release process

This lightweight procedure applies to individual low risk/impact change and provides steps for service updates and releases of the centrally-provided production services.

FINALISED

Catalin Condurache

APPROVED