Page Comparison

• Orchid release: Breaking change to support authority control - See Slack message - https://folio-project.slack.com/archives/C210RP0T1/p1672757167354339
• It is a stripes issue....what project to create/move issue?
  • Create / Move issue to JIRA Project > https://folio-org.atlassian.net/projects/STRIPES/
  • Assign Development Team = stripes-force 
  • stripes-force team will triage issue and move to right project. 

• Bursar development: Team Bama
• Paul Kloppenborg will take on some features 
• Florian Ruckelshausen working on Reminder fees for German libraries with Sif team 
• UNAM > Who will be the PO? Only 1.5 FTE. Only assigned several features. 
• Orchid bugfest: Cornelia Awenius will triage fee/fines issues. One bugfest commitment.  Holly will revise test cases.
• Communicate plan to PC and RA SIG

• Questions
  • Prioritization 
  • Knowledge transfer 
    • Documentation
    • Videos
  • Features
    • Vetting with RA SIG 
• Who will replace Holly? No one has been assigned. It is a significant loss. 
  • Lead? 
  • New Functionality?
  • Triage issues?
  • SME?

Releases reminders

• Orchid (key milestones) - dashboard
• Poppy (key milestones) - dashboard

10 minutes

Orchid

• Current: Sprint 156 (three week sprint)  
  • Review release scope
    • 20 features (Not started) 
    • 6 features (Analysis complete)
    • 2 features (Blocked)
  • Write ARCH tickets for Poppy features ... sooner the better 
• Sprint 157/158 : 
  • • Recommendation: Conduct a UAT (User Acceptance Testing)
    • Write performance test  and/or load testing stories  (Types of tests)
    • Write accessibility compliance checking story (have your FE lead speak with John Coburn on automation)

Additional deadlines

• Jan 27: PC/TC acceptance of new modules
• Feb 10: Orchid dev freeze > Allocate time to discuss with team
  • Bugfest prep
  • Release prep Release Readiness Checklist - Orchid 
• Mar 6 - Mar 17: Bugfest 
• April 10: Go Live

Poppy upcoming deadline:

• Feb 17th - Poppy features defined and scoped