Versions Compared

Old Version 14

changes.mady.by.user Oleksii Petrenko

Saved on

compared with

New Version 15

changes.mady.by.user Oleksii Petrenko

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents

...

All interfaces provided by Folio modules are ordered under following epic 

Jira Legacy
serverSystem JiraFOLIO Issue Tracker
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId01505d016ccf3fe4-b8533301-3c2e368a-90f1983e-ee9b165564fc20c466b11a49
keyFOLREL-1
and managed by the team responsible for corresponding modules.

...

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 - 

Jira Legacy
serverSystem JiraFOLIO Issue Tracker
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId01505d016ccf3fe4-b8533301-3c2e368a-90f1983e-ee9b165564fc20c466b11a49
keyFOLREL-205

2.1 Releasing new RMB version

...

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.

...

  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

Fix version of Jira ticket should be named according to github module release number

4.2 Release epic providing

Release epic should be noted according to appropriate module release phase.

...

Following story 

Jira Legacy
serverSystem JiraFOLIO Issue Tracker
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId01505d016ccf3fe4-b8533301-3c2e368a-90f1983e-ee9b165564fc20c466b11a49
keyMODKBEKBJ-440
 is created to track mod-kb-ebscojava release actions and main release epic is provided 
Jira Legacy
serverSystem JiraFOLIO Issue Tracker
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId01505d016ccf3fe4-b8533301-3c2e368a-90f1983e-ee9b165564fc20c466b11a49
keyFOLREL-340

4.3 Final interface version provided

Interfaces that are provided by module should be specified at 

Jira Legacy
server
System Jira
FOLIO Issue Tracker
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId
01505d01
6ccf3fe4-
b853
3301-
3c2e
368a-
90f1
983e-
ee9b165564fc
20c466b11a49
keyFOLREL-1
 epic and lined to release ticket via is defined by link type

Image Modified

4.4 Final interface version required

Interfaces that are required to module could be found at 

Jira Legacy
server
System Jira
FOLIO Issue Tracker
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId
01505d01
6ccf3fe4-
b853
3301-
3c2e
368a-
90f1
983e-
ee9b165564fc
20c466b11a49
keyFOLREL-1
 epic and lined to release ticket via requires link type

Image Modified

4.5 Used RMB version

RMB version that are required to module could be found at 

Jira Legacy
server
System Jira
FOLIO Issue Tracker
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId
01505d01
6ccf3fe4-
b853
3301-
3c2e
368a-
90f1
983e-
ee9b165564fc
20c466b11a49
keyFOLREL-205
 epic and lined to release ticket via relates to link type

Image Modified

All information relates to additional notes, github link and docker hub link should be specified at Description field

FAQ

QuestionReporterAnswer
Should I link all interfaces that are required/defined each time when module is gonna be released?

Oleksii Petrenko

To avoid routine work please look for ticket from previous release and clone it.

Once new ticket is created, please observe linkage section outdated interface versions will be in close state.

Then walk though 

Jira Legacy
serverFOLIO Issue Tracker
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyFOLREL-1
 and 
Jira Legacy
serverFOLIO Issue Tracker
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyFOLREL-205
 to observe updated versions.

Then proceed with upgrading (if required) of module with updated interfaces and link used versions of interfaces to release ticket before releasing if upgrading is required