Trillium (R1 2026)
Duration: 29 Sprints (mid Sprint 212 - mid Sprint 241) = 28.5 development sprint + 0.5 for modules releases
Release status
Track | Status | Comments |
|
|
|---|---|---|---|---|
Features development | Green |
|
|
|
OST (Official supported technologies) | Green |
|
|
|
Integration testing | Green |
|
|
|
Roadmap
EPICS
Release preparation
Modules and Applications release
Trillium Bugfest Dashboard
Timeline
Sprint | Dates | Name | Description | |
|---|---|---|---|---|
Sprint 236 | Feb 13, 2026 | Notify community regarding sharing information of new modules | Include module to FOLIO Module/JIRA project-Team-PO-Dev Lead responsibility matrix | |
Sprint 237 | Feb 27, 2026 | Deadline for requests to add new modules to the reference environments | Create Jira ticket at FOLIO Jira project ex. | |
Sprint 238 | Mar 13, 2026 | Umbrellaleaf release scope composition deadline | Lead PO prepared list of features for Umbrellaleaf release and input from SIGs | |
Sprint 239 | Mar 23, 2026 | API freeze for platform (Eureka/Stripes/RMB/Vert.x/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 | |
Mar 27, 2026 | API freeze for platform (Eureka/Stripes/RMB/Vert.x/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 2026 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 2026 period. Separate release branch has to be created after feature freeze date. All R1 2026 bug fixed have to be applied to both release and Master branches. Next release period feature development is expected on Master branch. | ||
Features test cases preparation deadline | To start test case automation for Trillium features test cases need to be prepared. | |||
Deadline for acceptance of new modules by Technical Council at Trillium (R1 2026) | New Module Technical Evaluations - Technical Council - FOLIO Wiki | |||
Deadline for new Eureka-application introduction |
| |||
Sprint 240 | Mar 30, 2026 - Apr 10, 2026 | Teams upgrade to the platform components | Teams upgrade to the platform components versions that were released. | |
Mar 30, 2026 | 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 | ||
Apr 2, 2026- Apr 3, 2026 | Umbrellaleaf release scope decomposition and estimation |
| ||
Apr 6, 2026 | Umbrellaleaf release scope refinement deadline | POs prepare list of UXPROD features aligned with Umbrellaleaf team capacity. PO present prepared scope at next PO Weekly meeting at <TBD> | ||
Apr 10, 2026 | 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 2026 | Feature development freeze for R1 2026 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 2026 period. Separate release branch has to be created after feature freeze date. All R1 2026 bug fixed have to be applied to both release and Master branches. Next release period feature development is expected on Master branch. | |||
Trillium R1 2026 features acceptance deadline |
| |||
Update modules configuration details | ||||
Sprint 241 | Apr 13, 2026 - Apr 16, 2026 | Schema upgrade testing | Major modules versions should be released. Schema upgrade have to be released and tested locally by each team. | |
Apr 13, 2026 - Apr 17, 2026 | Teams modules & applications releases |
| ||
Apr 16, 2026 | 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 | ||
Apr 13, 2026 | New blank Trillium bugfest environment is prepared |
| ||
Apr 14, 2026
| Eureka-application app-platform-minimal release deadline | https://github.com/folio-org/app-platform-minimal must have R1 2026 compatible release/branch by this date | ||
Apr 15, 2026 | Scripts are ready for new modules deployment |
| ||
Eureka-application app-platform-complete release deadline | https://github.com/folio-org/app-platform-complete must have R1 2026 compatible release/branch by this date | |||
Apr 16, 2026 | 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. | ||
Apr 17, 2026 | 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 R2 2025 compatible releases by this date | |||
Finalize release notes for Trillium features/applications/modules | Release notes have to be updated | |||
Eureka-applications release deadline | All applications must have R1 2026 compatible releases by this date | |||
Eureka-application platform-lsp release branch creation | https://github.com/folio-org/platform-lsp must have R1 2026 compatible release branch | |||
Contact with EBSCO FSE devops | Review release information. Up to date versions should be set | |||
Apr 18, 2026 - Apr 24, 2026 | Release integration week | Bugfest environment preparation, testing of schema and data migration by EBSCO FSE team | ||
Apr 22, 2026 | Deployment to Trillium bugfest env is completed. Data set is ready |
| ||
Apr 23, 2026 - Apr 24, 2026 | Sanity testing at Trillium bugfest env |
| ||
Sprint 242-243 | Apr 27, 2026 | Umbrellaleaf RFC Consideration | tech-council/NEW_MODULE_TECH_EVAL.MD at master · folio-org/tech-council · GitHub | |
Apr 27, 2026 - May 22, 2026 | Trillium R1 2026 Release testing and hardening period |
| ||
| Apr 27, 2026 - May 15, 2026 | Functional testing (Bug Fest) | Execute all TestRail test cases | |
| Apr 13, 2026 - May 15, 2026 | Performance testing |
| |
| May 18, 2026 - May 22, 2026 | Ongoing triage and bug fixing of bugs begins immediately |
| |
May 21, 2026 | 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-2026 platform-lsp release branch |
| |||
May 22, 2026 | Bugfix releases deadline |
| ||
Sprint 244 | May 26, 2026 - May 28, 2026 | Final Smoke testing |
| |
May 29, 2026 | Release is public |
| ||
Interface dependency matrixes
Modules planned for release