Duration: 8 Sprints (mid Sprint 203 - mid Sprint 211) = 7.5 development sprint + 0.5 for modules releases
...
Sprint | Dates | Dates | Name | Description | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
Sprint 206 |
| Notify community regarding sharing information of new modules | Include module to FOLIO Module/JIRA project-Team-PO-Dev Lead responsibility matrix | |||||||||
Sprint 207 |
| Deadline for requests to add new modules to the reference environments | Create Jira ticket at FOLIO Jira project ex.
| |||||||||
Sprint 208 |
| Trillium R2 2025 release scope composition deadline | Lead PO prepared list of features for Sunflower R1 2025 release and input from SIGs | |||||||||
Sprint 209 |
| API freeze for platform (Okapi/Stripes/RMB/Spring/Eureka) 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 2025 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 2025 period. Separate release branch has to be created after feature freeze date. All R1 2025 bug fixed have to be applied to both release and Master branches. Next R2 2025 release period feature development is expected on Master branch. | ||||||||||
Features test cases preparation deadline | To start test case automation for Poppy features test cases need to be prepared. | |||||||||||
Deadline for acceptance of new modules by Technical Council at Sunflower (R1 20242025) | New Module Technical Evaluations - Technical Council - FOLIO Wiki | |||||||||||
Sprint 210 | - | 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 | |||||||||||
- | Trillium release scope decomposition and estimation | |||||||||||
| Trillium R2 2025 release scope refinement deadline | POs prepare list of UXPROD features aligned with Trillium R2 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 R1 2025 | Feature development freeze for R1 2025 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 2025 period. Separate release branch has to be created after feature freeze date. All R1 2025 bug fixed have to be applied to both release and Master branches. Next R2 2025 release period feature development is expected on Master branch. | |||||||||||
Sunflower R1 2025 features acceptance deadline | ||||||||||||
Sprint 211 | - | 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 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 Ramsons features/applications/modules | Release notes have to be updated | |||||||||||
| 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 Ramsons bugfest env | |||||||||||
Sprint 212-213 |
| Trillium R2 2025 RFC Consideration | tech-council/NEW_MODULE_TECH_EVAL.MD at master · folio-org/tech-council · GitHub | |||||||||
- | R1 2025 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 R1-2025 platform complete release branch | TBD | |||||||||||
| Bugfix releases deadline | |||||||||||
Sprint 214 | - | Final Smoke testing | ||||||||||
| Release is public | |||||||||||
...