Trillium (R1 2026)
Duration: 28 Sprints (mid Sprint 212 - mid Sprint 240) = 27.5 development sprint + 0.5 for module releases
Release status
Track | Status | Comments |
|
|
|---|---|---|---|---|
Features development | Green |
|
|
|
OST (Official supported technologies) | Green |
|
|
|
Integration testing | Green |
|
|
|
Release plan
EPICS
Release preparation
Modules and Applications release
Trillium Bugfest Dashboard
Timeline
Sprint | Dates | Name | Description | |
|---|---|---|---|---|
Sprint 235 | Feb 13, 2026 | Notify the community regarding sharing information of new modules | Include module to FOLIO Module/JIRA project-Team-PO-Dev Lead responsibility matrix | |
Sprint 236 | Feb 27, 2026 | Deadline for requests to add new modules to the reference environments | Create a Jira ticket at the FOLIO Jira project. | |
Sprint 237 | Mar 13, 2026 | Umbrellaleaf release scope composition deadline | Lead PO prepared a list of features for the Umbrellaleaf release, and input from SIGs | |
Sprint 238 | 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 components 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 be added after this date. DoD for features has been met. Only defects are expected tie to R1 2026 period. A separate release branch has to be created after the feature freeze date. All R1 2026 bug fixes have to be applied to both the release and the Master branches. Next release period feature development is expected on the 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 the new Eureka-application introduction |
| |||
Sprint 239 | 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 a meeting for review Bugfest preparation plan Create appropriate Jira tickets in the Kitfox backlog Review the 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 a list of UXPROD features aligned with the 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 the upgrade to the platform components status. | RC review upgraded components and facilitate a meeting with non-upgraded components owners to discuss available impediments/issues/problems to understand when the component could be upgraded | |||
Modules feature development freeze R1 2026 | Feature development freeze for R1 2026 release period. No new feature can be added after this date. DoD for features has been met. Only defects are expected tie to R1 2026 period. A separate release branch has to be created after the feature freeze date. All R1 2026 bug fixes have to be applied to both the release and Master branches. Next release period feature development is expected on the Master branch. | |||
Trillium R1 2026 features acceptance deadline |
| |||
Update modules configuration details | ||||
Sprint 240 | Apr 13, 2026 - Apr 16, 2026 | Schema upgrade testing | Major module versions should be released. The schema upgrade has 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 module owners to discuss available impediments/issues/problems to understand when the module could be released. The major interface version is to be updated | ||
Apr 13, 2026 | A 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 module 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 meetings with non-upgraded module owners to discuss available impediments/issues/problems to understand when the schema could be upgraded. | ||
Apr 17, 2026 | Final Review modules release readiness | RC review released modules and facilitate meeting with unreleased module owners to discuss available impediments/issues/problems to understand when the 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-application platform-lsp release branch creation | https://github.com/folio-org/platform-lsp must have R1 2026 compatible release branch | |||
Apr 24, 2026 | Eureka-applications release deadline | All applications must have R1 2026 compatible releases by this date | ||
Contact with Kitfox DevOps | Review release information. Up-to-date versions should be set | |||
Sprint 241 | Apr 27, 2026 - May 8, 2026 | Release integration sprint | Trillium testing environment preparation, testing of schema, and data migration by the Kitfox team | |
May 6, 2026 | Deployment to the Trillium testing env is completed. The data set is ready |
| ||
May 7, 2026 - May 8, 2026 | Sanity testing at Trillium testing env |
| ||
Sprint 242-243 | May 11, 2026 | Umbrellaleaf RFC Consideration | tech-council/NEW_MODULE_TECH_EVAL.MD at master · folio-org/tech-council · GitHub | |
May 11, 2026 - Jun 5, 2026 | Trillium R1 2026 Release testing and hardening period |
| ||
| May 11, 2026 - May 29, 2026 | Community Bug Fest | Execute all TestRail test cases | |
| Jun 1, 2026 - Jun 5, 2026 | Ongoing triage and bug fixing begin immediately |
| |
Jun 4, 2026 | Bugfix releases readiness | RC review bugfix dashboard and facilitate meeting with unresolved module owners to discuss available impediments/issues/problems to understand when the module could be released | ||
Create R1-2026 platform-lsp release branch |
| |||
Jun 5, 2026 | Bugfix releases deadline |
| ||
Trillium GO|!GO Meeting | RMS to decide | |||
Sprint 244 | Jun 8, 2026 | Release is public |
| |
Interface dependency matrices
2026_R1_InterfacesDependencyMatrix-MastervsMaster
2026_R1_InterfacesDependencyMatrix-2025R1vsMaster
Modules planned for release