...
On what timeline does the community make Eureka the official FOLIO architecture release?
On what timeline does the community stop supporting Okapi?
...
Quesnelia | Ramsons | Sunflower | Trillium | |
|---|---|---|---|---|
EBSCO Primary development platform | Okapi | Okapi | Eureka | Eureka |
EBSCO Bugfixing for | Okapi and Eureka | Okapi and Eureka | Eureka | Eureka |
Community Bugfixing for | Okapi and Eureka | Okapi and Eureka | Eureka | Eureka |
Community Testing (bugfest) - EBSCO hosted | Okapi and Eureka | Okapi and Eureka | Eureka | Eureka |
Community Testing (bugfest) - Community | NA | NA | NA | NA |
Support for CSPs (critical issues only) | Quesnelia/Okapi Poppy/Okapi | Ramsons/Okapi Quesnelia/Okapi | Sunflower/Eureka Ramsons/Okapi | Trillium/Eureka Sunflower/Eureka |
Option | Running Sunflower modules Ramsons and Okapi support |
...
Possible next steps for councils
...
to affirm the Sunflower timeframe
Technical council
Determine how to approve the large number of modules in time for Sunflower, or agree to approve as a package: https://folio-org.atlassian.net/wiki/spaces/TC/pages/518946885/0010-eureka#New-Components
Update module approval processes to account for application formalization
Affirm with the sysops SIG and others that the early adopter program for hosting providers is on track
Product council
Support SIGs and POs in implementation of application formalization
Ensure there is enough support for the user management SIG to allow implementers to effectively adopt the new permissions structure in Eureka
Work with end user early adopters to outline and document any other product/UX oriented changes from Eureka and evaluate whether that information can be prepared for the Sunflower deadline
Community council
Evaluate any budgetary needs for meeting the Sunflower deadline and whether or not they are feasible
Next steps for community dev ops
...