| Table of Contents |
|---|
...
Release preparation
Jira Legacy server FOLIO Issue TrackerSystem Jira columnIds issuekey,summary,issuetype,duedate,status columns key,summary,type,due,status maximumIssues 20 jqlQuery project = Folrel and type=epic and summary ~ "R1 2021" and summary !~ "release" order by key serverId 6ccf3fe401505d01-3301b853-368a3c2e-983e90f1-20c466b11a49ee9b165564fc
Modules release
Jira Legacy server FOLIO Issue TrackerSystem Jira columnIds issuekey,summary,issuetype,duedate,status columns key,summary,type,due,status maximumIssues 20 jqlQuery project = Folrel and type=epic and summary ~ "R1 2021" and summary ~ "release" Order by key serverId 6ccf3fe401505d01-3301b853-368a3c2e-983e90f1-20c466b11a49ee9b165564fc
Timeline
| Sprint | Dates | Dates | Name | Description |
|---|---|---|---|---|
| Sprint 107 |
| API freeze for platform (Okapi/Stripes/RMB) readiness review | RC review released platform components and facilitate meeting with unreleased components owners to discuss available impediments/issues/problems to understand when component could be released | |
| API freeze for platform (Okapi/Stripes/RMB) | API freeze for platform (Okapi/Stripes/RMB) and deadline for initial releases of platform components. No breaking changes to the platform after this date. Feature development freeze for R1 2021 release period. No new feature can not be added or changed after this date. Only defects are expected tie to R1 2021 period. Next R2 2021 release period feature development is expected at separate development branch and should not be merged to master before R1 2021 module release. | ||
| Sprint 107 - Sprint 109 | - | Teams upgrade to the platform components | Teams upgrade to the platform components versions that were released. | |
| Sprint 108 |
| Major interface version provided to be updated | ||
| Modules feature development freeze R1 2021 - Platform core modules | Feature development freeze for R1 2021 release period. It is not allowed to add or change features after this date. Only changes to address defects are allowed. Next R2 2021 release period feature development is expected on a separate development branch and these new features should not be merged to master before R1 2021 module release. | |||
| Sprint 109 | - | Schema upgrade testing week (BE core modules) | ||
| Review upgrade to platform components status. | RC review upgraded components and facilitate meeting with non-upgraded components owners to discuss available impediments/issues/problems to understand when component could be upgraded | |||
| Modules feature development freeze R1 2021 - Platform complete modules | Feature development freeze for R1 2021 release period. It is not allowed to add or change features after this date. Only changes to address defects are allowed. Next R2 2021 release period feature development is expected on a separate development branch and these new features should not be merged to master before R1 2021 module release. | |||
- | Schema upgrade testing week | Major modules versions should be released. Schema upgrade have to be released and tested locally by each team. | ||
- | Teams modules releases | |||
- | Platform Core Back End (Storage) modules releases | |||
- | Platform Core Back End (Business logic) modules releases | |||
- | Platform Core Front End modules releases | |||
| Platform Complete Back End (Storage) modules releases | ||||
Sprint 110 | - | Platform complete BE (Business logic) modules releases | ||
- | Platform complete Front End modules releases | |||
(Monday) | Modules release readiness review | RC review released modules and facilitate meeting with unreleased modules owners to discuss available impediments/issues/problems to understand when module could be released). Major interface version provided to be updated | ||
| Schema upgrade testing review | RC review upgraded modules and facilitate meeting with non-upgraded modules owners to discuss available impediments/issues/problems to understand when schema could be upgraded. | ||
| Final Review modules release readiness | RC review released modules and facilitate meeting with unreleased modules owners to discuss available impediments/issues/problems to understand when module could be released | ||
| Module release deadline | All modules must see R1-compatible releases by this date | |||
| Contact with devops | Review release information. Up to date versions should be set | ||
- | Release integration week | Bugfest environment preparation, testing of schema and data migration by EBSCO FSE team | ||
Sprint 111 | - | Q3 Release testing and hardening period | ||
- | Functional testing (Bug Fest) | Execute all TestRail test cases | ||
- | Performance testing | |||
| Sprint 112 | - | Ongoing triage and bug fixing of bugs begins immediately | ||
| Bugfix releases readiness | RC review bugfix dashboard and facilitate meeting with unresolved modules owners to discuss available impediments/issues/problems to understand when module could be released | ||
| Bugfix releases deadline | |||
| Sprint 113 |
| Release is public | ||
...
Modules planned for release
Release notes
Interfaces dependency matrices
...