Versions Compared

Key

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

Table of Contents

0 Project and board

New Jira project - https://issuesfolio-org.folioatlassian.orgnet/browse/FOLREL is created to manage release related activities

Release board - https://issuesfolio-org.folioatlassian.orgnet/secure/RapidBoard.jspa?rapidView=157

This board automatically fetches release/RMB/Stripes stories created in corresponding Jira projects by different teams to visualize overall progress on the release. Processing of Release/RMB/Stripes stories is done by the teams using their Scrum Boards.

1 Tracking interfaces versions

All interfaces provided by Folio modules are ordered under following epic 

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyFOLREL-1
and managed by the team responsible for corresponding modules.

Image Removed

1.1 Updating Interface Versions

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

All teams are responsible to update Interface Versions Provided by their modules prior release deadline as per release timeline.

New item for actual Interface Version Provided should be created in Interfaces epic, while the item representing an outdated Interface Version Provided should be Closed.

For example:

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

...

1

...

Previous ticket for eholdings 2.0 should be closed.

New ticket in Interfaces epic eholdings 2.1 should be created.

...

Tracking RMB versions

All interfaces are ordered under following epic - 

Jira Legacy
serverSystem JiraJIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyFOLREL-205

...

1.1 Releasing new RMB version

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

...

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

...

2 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://issuesfolio-org.folioatlassian.orgnet/browse/FOLREL-341 has been created. Please create a tickets familiar to https://issuesfolio-org.folioatlassian.orgnet/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://issuesfolio-org.folioatlassian.orgnet/browse/FOLREL-342 has been created. Please create a tickets familiar to https://issuesfolio-org.folioatlassian.orgnet/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 

...

3 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

...

3.1 Fix version

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

...

3.2 Release epic providing

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

Required epic could be found at release page.

Example:

See Q2 2020 modules release epics.

Spitfire team is going to release mod-kb-ebscojava at main Q2 2020 release.

Following story 

Jira Legacy
serverSystem JiraJIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyMODKBEKBJ-440
 is created to track mod-kb-ebscojava release actions and main release epic is provided 
Jira Legacy
serverSystem JiraJIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyFOLREL-340

4.3 Final interface version provided

Interfaces that are provided by module should be specified at 

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyFOLREL-1
 epic and lined to release ticket via is defined by link type

Image Removed

4.4 Final interface version required

Interfaces that are required to module could be found at 

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyFOLREL-1
 epic and lined to release ticket via requires link type

Image Removed

4.5 Used RMB version

RMB version that are required to module could be found at 

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyFOLREL-205
 epic and lined to release ticket via relates to link type

Image Removed

...


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

...

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

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
serverSystem JiraJIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyFOLREL-1
 and 
Jira Legacy
serverSystem JiraJIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
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

Can the bugfix release epic reopened and reused if a second bugfix release is needed, or should we create a second bugfix epic?Julian LadischBugFix Release epic be active till BugFix deadline. After that we could use HotFix epic to track release tickets



...