Table of Contents |
---|
Roadmap
EPICS
Release preparation
Jira Legacy server System JiraJIRA columnIds issuekey,summary,issuetype,duedate,status columns key,summary,type,due,status maximumIssues 20 jqlQuery project = Folrel and type=epic and summary ~ "R2 2022" and summary !~ "release" order by key serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
Modules release
Jira Legacy server System JiraJIRA columnIds issuekey,summary,issuetype,duedate,status columns key,summary,type,due,status maximumIssues 20 jqlQuery project = Folrel and type=epic and summary ~ "R2 2022" and summary ~ "release" Order by key serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
...
Sprint | Dates | Dates | Name | Description | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Sprint 137 |
| Notify community regarding sharing information of new modules | Include module to Team vs module FOLIO Module/JIRA project-Team-PO-Dev Lead responsibility matrix | |||||||||||||
Sprint 138 |
| Deadline for requests to add new modules to the reference environments | Create Jira ticket at FOLIO Jira project ex.
| |||||||||||||
Sprint 139 |
| Nolana R3 2022 release scope composition deadline | Lead PO prepared list of features for Nolana R2 2022 release and get approval from PC | |||||||||||||
Sprint 140 |
| 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 R2 2022 release period. No new feature can not be added after this date. DoD for features has been met. Only defects are expected tie to R2 2022 period. Separate release branch has to be created after feature freeze date. All R2 2022 bug fixed have to be applied to both release and Master branches. Next R3 2022 release period feature development is expected on Master branch. | ||||||||||||||
Features test cases preparation deadline | To start test case automation for Morning Glory features test cases need to be prepared. | |||||||||||||||
Deadline for acceptance of new modules by Technical Council | New Module Technical Evaluations - Technical Council - FOLIO Wiki | |||||||||||||||
Sprint 141 | - | 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 jira tickets in Kitfox backlog Review list of new modules Review data cleanup Review new data | |||||||||||||||
Prepare vagrant box with Lotus codebase | ||||||||||||||||
| Major interface version provided to be updated | |||||||||||||||
Modules feature development freeze R2 2022 - Platform core modules | Feature development freeze for R2 2022 release period. No new feature can not be added after this date. DoD for features has been met. Only defects are expected tie to R2 2022 period. Separate release branch has to be created after feature freeze date. All R2 2022 bug fixed have to be applied to both release and Master branches. Next R3 2022 release period feature development is expected on Master branch. | |||||||||||||||
- | Nolana release scope decomposition and estimation | |||||||||||||||
- | Schema upgrade testing week (BE core modules) | |||||||||||||||
| Nolana R3 2022 release scope refinement deadline | POs prepare list of UXPROD features aligned with Nolana R3 2022 team capacity. PO present prepared scope at next PO Weekly meeting at <TBD> | ||||||||||||||
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 R2 2022 - Platform complete modules | Feature development freeze for R2 2022 release period. No new feature can not be added after this date. DoD for features has been met. Only defects are expected tie to R2 2022 period. Separate release branch has to be created after feature freeze date. All R2 2022 bug fixed have to be applied to both release and Master branches. Next R3 2022 release period feature development is expected on Master branch. | |||||||||||||||
Sprint 142 | - | Teams upgrade to the RMB v 34 | ||||||||||||||
Sprint 143 | - | 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 | |||||||||||||||
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 Lotus 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 R2 2022-compatible releases by this date | |||||||||||||||
Sprint 144 |
| Contact with Kitfox devops | Review release information. Up to date versions should be set | |||||||||||||
- | Release integration week | Bugfest environment preparation, testing of schema and data migration by Kitfox team | ||||||||||||||
| Deployment to Lotus bugfest env is completed. Data set is ready | |||||||||||||||
- | Sanity testing at Lotus bugfest env | |||||||||||||||
Sprint 144 - Sprint 148 | - | R2 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 | ||||||||||||||
Create R2-2022 platform complete release branch | John Malconian /Kitfox | |||||||||||||||
| Bugfix releases deadline | |||||||||||||||
Sprint 148 - Sprint 149 | - | Morning Glory Stabilization Testing & Smoke Testing | ||||||||||||||
Sprint 149 |
| Release is public |
...
Main release 8 July 2022
Jira Legacy | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Hot Fix #1
Modules release deadline -
GA Date -
Jira Legacy | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...