Skip to end of banner
Go to start of banner

Release process in Jira

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 7 Next »

0 Project and board

New Jira project - https://issues.folio.org/browse/FOLREL is created to manage release related activities

Release board - https://issues.folio.org/secure/RapidBoard.jspa?rapidView=157

1 Tracking interfaces versions

All interfaces are ordered under following epic -  FOLREL-1 - Getting issue details... STATUS

1.1 Releasing new interface version

Once development team is decide to release new interface version than previous one have to be closed.

For example:

mod-kb-ebscojava module provides latest interface version - eholdings 2.0

During releasing new version of mod-kb-ebscojava new interface eholdings 2.1 has been provided.

Previous ticket for eholdings 2.0 should be closed.

New ticket in Interfaces epic eholdings 2.1 should be created.

2 Tracking RMB versions

All interfaces are ordered under following epic -  FOLREL-205 - Getting issue details... STATUS

2.1 Releasing new RMB version

Once RMB development team is decide to release new interface version than previous one have to be closed.

For example:

raml-module-builder provides latest interface version - "RMB v 29.4.0"

During releasing new version of raml-module-builder new version "RMB v 30.0.0" has been provided.

Previous ticket for RMB v 29.4.0 should be closed.

New ticket in RMB epic "RMB v 30.0.0" should be created

3 Release epics

For each release appropriate release epics should be created.

Following release checkpoints should be covered with separate epics:

  1. Release preparation - upgrading to platform components if new version is provided
    1. Stripes (example: to manage process of upgrading to Stripes v4 epic - https://issues.folio.org/browse/FOLREL-341 has been created. Please create a tickets familiar to https://issues.folio.org/browse/UIEH-891 to track your effort and set epic to FOLREL-341 if upgrade is not required -> jira ticket could not be created)
    2. RMB (example: to manage process of upgrading to RMB v30 epic - https://issues.folio.org/browse/FOLREL-342 has been created. Please create a tickets familiar to https://issues.folio.org/browse/UIEH-891 to track your effort and set epic to FOLREL-342 if upgrade is not required -> jira ticket could not be created)
    3. OKAPI
  2. Modules release
    1. Main release
    2. Bugfix release
    3. Hotfix release

As example see bunch of epics that are created for Q2 2020 

4 Tracking modules releases

Development team and PO should decide what responsible modules are going to be released.

When decision is agreed then separate ticket for module release should be created in specified Jira project.

Alignment of module and Jira project could be found at Team vs module responsibility matrix

4.1 Fix version


4.2 Release epic providing


4.3 Final interface version required


4.4 Final interface version provided


4.5 Used RMB version



  • No labels