Duration: 17 sprints long (mid Sprint 187 - mod Sprint 203) - 16.5 development sprints + 0.5 sprint for modules releases
| Table of Contents |
|---|
...
| Sprint | Dates | Dates | Name | Description | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Sprint 198 |
| Notify community regarding sharing information of new modules | Include module to FOLIO Module/JIRA project-Team-PO-Dev Lead responsibility matrix | |||||||||||||
| Sprint 199 |
| Deadline for requests to add new modules to the reference environments | Create Jira ticket at FOLIO Jira project ex.
| |||||||||||||
| Sprint 200 |
| Sunflower R1 2025 release scope composition deadline | Lead PO prepared list of features for Sunflower R1 2025 release and input from SIGs | |||||||||||||
| Sprint 201 |
| 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 2024 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 2024 period. Separate release branch has to be created after feature freeze date. All R2 2024 bug fixed have to be applied to both release and Master branches. Next R1 2025 release period feature development is expected on Master branch. | ||||||||||||||
| Features test cases preparation deadline | To start test case automation for Poppy Ramsons features test cases need to be prepared. | |||||||||||||||
| Deadline for acceptance of new modules by Technical Council at Ramsons (R2 2024) | New Module Technical Evaluations - Technical Council - FOLIO Wiki | |||||||||||||||
| Sprint 202 | - | 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 | |||||||||||||||
-20 Sep | Sunflower release scope decomposition and estimation | |||||||||||||||
23 Sep | Sunflower R1 2025 release scope refinement deadline | POs prepare list of UXPROD features aligned with Sunflower R1 2025 team capacity. PO present prepared scope at next PO Weekly meeting at <TBD> | ||||||||||||||
| Major interface version provided to be updated | ||||||||||||||||
| 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 2024 | Feature development freeze for R2 2024 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 2024 period. Separate release branch has to be created after feature freeze date. All R2 2024 bug fixed have to be applied to both release and Master branches. Next R1 2025 release period feature development is expected on Master branch. | |||||||||||||||
| Ramsons R2 2024 features acceptance deadline | ||||||||||||||||
Sprint 203 | - | Schema upgrade testing | Major modules versions should be released. Schema upgrade have to be released and tested locally by each team. | |||||||||||||
- | Teams modules releases | |||||||||||||||
(Thursday) | 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 Poppy Ramsons 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 have R1 2024-compatible releases by this date | |||||||||||||||
| Finalize release notes for Poppy Ramsons features/applications/modules | Release notes have to be updated | |||||||||||||||
04 | Contact with Kitfox/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 Kitfox/FSE team | ||||||||||||||
| Deployment to Ramsons bugfest env is completed. Data set is ready | |||||||||||||||
- | Sanity testing at Poppy Ramsons bugfest env | |||||||||||||||
Sprint 204-205 | Sunflower R1 2025 RFC Consideration | tech-council/NEW_MODULE_TECH_EVAL.MD at master · folio-org/tech-council · GitHub | ||||||||||||||
- | R2 2024 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-2024 platform complete release branch | TBD | |||||||||||||||
| Bugfix releases deadline | |||||||||||||||
Sprint 206 | - | Final Smoke testing | ||||||||||||||
| Release is public | |||||||||||||||
...