Lotus (R1 2022)
Roadmap
EPICS
Release preparation
Modules release
Timeline
| Sprint | Dates | Dates | Name | Description |
|---|---|---|---|---|
| Sprint 128 |
| Notify community regarding sharing information of new modules | Include module to FOLIO Module/JIRA project-Team-PO-Dev Lead responsibility matrix | |
| Sprint 129 |
| Deadline for requests to add new modules to the reference environments | Create Jira ticket at FOLIO Jira project ex. FOLIO-3255 - Getting issue details... STATUS | |
| Sprint 131 |
| API freeze for platform (Okapi/Stripes/RMB/Spring) 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/Spring) | Okapi/Stripes/RMB/SpringWay freeze and deadline for initial releases of platform components. No breaking changes to the platform after this date. Feature development freeze for R1 2022 release period. No new feature can be added after this date. DoD for features has been met. Only defects are expected tie to R1 2022 period. Separate release branch has to be created after feature freeze date. All R1 2022 bug fixed have to be applied to both release and Master branches. Next R2 2022 release period feature development is expected on Master branch. | ||
| Sprint 132 | - | Teams upgrade to the platform components | Teams upgrade to the platform components versions that were released. | |
| Bugfest environment preparation kick-off | Conduct meeting for review Bugfest preparation plan Create appropriate Rally tickets in EBSCO FSE backlog Review list of new modules Review data cleanup Review new data | |||
| Sprint 133 |
| Major interface version provided to be updated | ||
| Modules feature development freeze R1 2022 - Platform core modules/ New modules prerelease | Feature development freeze for R1 2022 release period. No new feature can be added after this date. DoD for features has been met. Only defects are expected tie to R1 2022 period. Separate release branch has to be created after feature freeze date. All R1 2022 bug fixed have to be applied to both release and Master branches. Next R2 2022 release period feature development is expected on Master branch. | |||
- | Schema upgrade testing week (BE core modules) | |||
| Morning Glory R2 2022 release scope composition deadline | POs prepare list of UXPROD features aligned with Morning Glory R2 2022 team capacity. PO present prepared scope at next PO Weekly meeting at | ||
| 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 2022 - Platform complete modules/ New modules prerelease | Feature development freeze for R1 2022 release period. No new feature can be added after this date. DoD for features has been met. Only defects are expected tie to R1 2022 period. Separate release branch has to be created after feature freeze date. All R1 2022 bug fixed have to be applied to both release and Master branches. Next R2 2022 release period feature development is expected on Master branch. | |||
Sprint 134 | - | 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 | ||||
- | 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 | ||
| New blank Kiwi bugfest environment is prepared | |||
| Scripts are ready for new modules deployment | |||
| 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 2022-compatible releases by this date | |||
Sprint 135 |
| Contact with FSE 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 | ||
| Deployment to Lotus bugfest env is completed. Data set is ready | |||
- | Sanity testing at Lotus bugfest env | |||
Sprint 135 - Sprint 137 | - | R1 2022 Release testing and hardening period | ||
- | Functional testing (Bug Fest) | Execute all TestRail test cases | ||
- | Performance testing | |||
- | 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 | |||
| Create R1-2022 platform complete release branch | John Malconian | |||
- | Smoke testing | |||
| Sprint 138 | () | Release is public | ||
Interface dependency matrixes
2022_R1_InterfacesDependencyMatrix-MastervsMaster
2022_R1_InterfacesDependencyMatrix-2021R3vsMaster
Modules planned for release
Main release 4 March 2022
Hot Fix #1
Approval deadline -
Modules release deadline -
GA Date -
Hot Fix #2
GA Date -
Hot Fix #3
Modules release deadline -
GA Date -