Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents

...

SprintDatesDatesNameDescription
Sprint 182

 

Notify community regarding sharing information of new modulesInclude module to FOLIO Module/JIRA project-Team-PO-Dev Lead responsibility matrix
Sprint 183

 

Deadline for requests to add new modules to the reference environments

Create Jira ticket at FOLIO Jira project ex. 

Jira Legacy
serverSystem Jira
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyFOLIO-3255

Sprint 184

 

Ramsons R2 2024 release scope composition deadlineLead PO prepared list of features for Ramsons R2 2024 release and input from SIGs
Sprint 185

 

API freeze for platform (Okapi/Stripes/RMB/Spring) readiness reviewRC 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 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 R1 2024 period. Separate release branch has to be created after feature freeze date. All R1 2024 bug fixed have to be applied to both release and Master branches. Next R3 2023 release period feature development is expected on Master branch.

Features test cases preparation deadlineTo start test case automation for Quesnelia features test cases need to be prepared.
Deadline for acceptance of new modules by Technical Council at Quesnelia (R1 2024)New Module Technical Evaluations - Technical Council - FOLIO Wiki
Sprint 186

 

Teams upgrade to the platform componentsTeams 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

- 

Ramsons release scope decomposition and estimation

 

Ramsons R2 2024 release scope refinement deadline

POs prepare list of UXPROD features aligned with Ramsons R2 2024 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 2024Feature development freeze for R1 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 R1 2024 period. Separate release branch has to be created after feature freeze date. All R1 2024 bug fixed have to be applied to both release and Master branches. Next R1 2024 release period feature development is expected on Master branch.
Quesnelia R1 2024 features acceptance deadline

Sprint 187

 

Schema upgrade testingMajor modules versions should be released. Schema upgrade have to be released and tested locally by each team.

 

Teams modules releases

  (Thursday)

Modules release readiness reviewRC 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 bugfest environment is prepared 

 

Scripts are ready for new modules deployment

 

Schema upgrade testing reviewRC 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 deadlineAll modules must have R1 2024-compatible releases by this date
Finalize release notes for Poppy features/applications/modules Release notes have to be updated

 

Contact with Kitfox devopsReview release information. Up to date versions should be set

 

Release integration weekBugfest environment preparation, testing of schema and data migration by Kitfox team

 

Deployment to Quesnelia bugfest env is completed.

Data set is ready


 

Sanity testing at Quesnelia bugfest env

Sprint 188

 

R1 2024 Release testing and hardening period

 

Functional testing (Bug Fest)Execute all TestRail test cases

 

Performance testing
Sprint 189

 

Ongoing triage and bug fixing of bugs begins immediately

 


Bugfix releases readinessRC 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-2024 platform complete release branch

TBD

 

Bugfix releases deadline

Final Smoke testing
Sprint 190

 

Release is public

~ March 2025End of Life

Assuming the FOLIO support policy remains unchanged, Quesnelia will be supported with critical security and bug fixes until Sunflower (R1 2025) release (around March 2025).

Note that Quesnelia was actually released on 31-May-2024

...