Orchid (R1 2023)
Bugfest environments
Main tenant https://bugfest-orchid.int.aws.folio.org/
Tenant #2 https://bugfest-orchid-plus.int.aws.folio.org/
Tenant #3 https://bugfest-orchid-aqa.int.aws.folio.org/
Roadmap
EPICS
Release preparation
Modules release
Timeline
Sprint | Dates | Dates | Name | Description |
|---|---|---|---|---|
Sprint 154 | Dec 9, 2022 | Notify community regarding sharing information of new modules | Include module to FOLIO Module/JIRA project-Team-PO-Dev Lead responsibility matrix | |
Sprint 155 | Dec 23, 2022 | Deadline for requests to add new modules to the reference environments | Create Jira ticket at FOLIO Jira project ex. | |
Sprint 156 | Jan 13, 2023 | Poppy R2 2023 release scope composition deadline? | Lead PO prepared list of features for Poppy R2 2023 release with input from appropriate SIGs | |
Sprint 157 | Jan 23, 2023 | 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 | |
Jan 27, 2023 | 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 2023 release period. No new feature can not be added after this date. DoD for features has been met. Only defects are expected tie to R3 2022 period. Separate release branch has to be created after feature freeze date. All R1 2023 bug fixed have to be applied to both release and Master branches. Next R2 2023 release period feature development is expected on Master branch. | ||
Features test cases preparation deadline | To start test case automation for Orchid features test cases need to be prepared. | |||
Deadline for acceptance of new modules by Technical Council at Orchid (R1 2023) | New Module Technical Evaluations - Technical Council - FOLIO Wiki | |||
Sprint 158 | Jan 30, 2023 - Feb 10, 2023 | Teams upgrade to the platform components | Teams upgrade to the platform components versions that were released. | |
Jan 30, 2023 | 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 | ||
Jan 30, 2023 | Prepare vagrant box with Nolana codebase | |||
Feb 3, 2023 | Major interface version provided to be updated |
| ||
Modules feature development freeze R1 2023 - Platform core modules | Feature development freeze for R1 2023 release period. No new feature can not be added after this date. DoD for features has been met. Only defects are expected tie to R1 2023 period. Separate release branch has to be created after feature freeze date. All R1 2023 bug fixed have to be applied to both release and Master branches. Next R2 2023 release period feature development is expected on Master branch. | |||
Feb 2, 2023 -Feb 3, 2023 | Poppy release scope decomposition and estimation |
| ||
Feb 6, 2023 -Feb 10, 2023 | Schema upgrade testing week (BE core modules) |
| ||
Feb 17, 2023 | Poppy R2 2023 release scope refinement deadline | POs prepare list of UXPROD features aligned with Poppy R2 2023 team capacity. PO present prepared scope at next PO Weekly meeting at <TBD> | ||
Feb 10, 2023 | 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 2023 - Platform complete modules | Feature development freeze for R1 2023 release period. No new feature can not be added after this date. DoD for features has been met. Only defects are expected tie to R1 2023 period. Separate release branch has to be created after feature freeze date. All R1 2023 bug fixed have to be applied to both release and Master branches. Next R2 2023 release period feature development is expected on Master branch. | |||
Orchid R1 2023 features acceptance deadline |
| |||
Sprint 159 | Feb 13, 2023 - Feb 17, 2023 | Schema upgrade testing week | Major modules versions should be released. Schema upgrade have to be released and tested locally by each team. | |
Feb 13, 2023 - Feb 24, 2023 | Teams modules releases |
| ||
Feb 20, 2023 (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 | ||
Feb 21, 2023 | New blank Lotus bugfest environment is prepared |
| ||
Feb 23, 2023 | Scripts are ready for new modules deployment |
| ||
Feb 24, 2023 | 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. | ||
Feb 24, 2023
| 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 R3 2022-compatible releases by this date | |||
Sprint 160
| Feb 27, 2023 | Contact with Kitfox devops | Review release information. Up to date versions should be set | |
Feb 27, 2023 - Mar 3, 2023 | Release integration week | Bugfest environment preparation, testing of schema and data migration by Kitfox team | ||
Mar 1, 2023 | Deployment to Orchid bugfest env is completed. Data set is ready |
| ||
Mar 2, 2023 - Mar 3, 2023 | Sanity testing at Orchid bugfest env |
| ||
Sprint 160 - Sprint 162
| Mar 6, 2023 - Mar 31, 2023 | R1 2023 Release testing and hardening period |
| |
| Mar 6, 2023 - Mar 17, 2023 | Functional testing (Bug Fest) | Execute all TestRail test cases | |
| Mar 6, 2023 - Mar 17, 2023 | Performance testing |
| |
| Mar 20, 2023 - Mar 31, 2023 | Ongoing triage and bug fixing of bugs begins immediately |
| |
Mar 28, 2023
| 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 R1-2023 platform complete release branch | TBD | |||
Mar 31, 2023 | Bugfix releases deadline |
| ||
Apr 4, 2023 - Apr 6, 2023 | Final Smoke testing |
| ||
Sprint 163 | Apr 10, 2023 | Release is public |
| |