Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Schema Upgrade Testing

RCA Group

None

Description

Process described on #releases channel here https://folio-project.slack.com/archives/CGPMHLX9B/p1590164280223800

wrote some documentation for doing this locally.

Ask if you have questions.

Also related to the MARC_BIB to MARC change. Take Iris release vagrant box->upgrade to R2->upgrade to PR for reverting these changes (from Spitfire-team).

In the scope of this ticket were tested these modules:

  1. mod-data-import

  2. mod-converter-storage

Note: mod-source-record-manager and mod-source-record-storage don't have any scripts in these PRs.

Environment

None

Potential Workaround

None

blocks

defines

has to be done after

Checklist

hide

TestRail: Results

Activity

Show:

Kateryna SenchenkoJune 24, 2021 at 11:06 AM

Hi ,

This testing is needed only for Juniper, and if any fixes are required they will be included in Juniper bugfixes.

Ann-Marie BreauxJune 23, 2021 at 4:33 PM

and If we find issues with the schema upgrade testing, will those fixes need to be 1) Iris hotfixes, 2) Juniper bugfixes, or both? cc:

Ann-Marie BreauxJune 11, 2021 at 2:45 PM

Hi Not a problem. and Any chance we can add to the current sprint before the rest of the MOD releases?

Khalilah GambrellJune 10, 2021 at 1:54 PM

, Spitfire has reviewed this story and we feel this should be done by Folijet.

Ann-Marie BreauxJune 9, 2021 at 1:32 PM

Grooming - this needs to be done before the releases, to determine if fixes are needed, or if anything needs to be reverted

Done

Details

Assignee

Reporter

Labels

Priority

Story Points

Sprint

Development Team

Folijet

Parent

Fix versions

Release

R2 2021 Bugfix

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs

Created June 9, 2021 at 8:32 AM
Updated June 26, 2021 at 7:43 AM
Resolved June 26, 2021 at 7:43 AM
TestRail: Cases
TestRail: Runs