Page Comparison

• Java 17
  • From Java 11 to Java 17 
    • Taras: it should go smoothly 
• Springboot 3.0 migration/upgrade need to do by May 2023
  • Applies to spring based modules 
  • Unknown when the new release will be available (November 2022?) 
  • Taras: Some major changes but we do not expect a lot of effort from developers But there maybe some unknown. 
  • Testing > Sprint Testing
• RMB/vertX updates? 
  • Oleksii TBD – need to discuss with Core Platform - He will have answer by next meeting. 
    • Need to know the risk/impact of this update
  • Taras: Maybe unnecessary since Java11 will be supported for awhile in regards to RMB/vertX. We have to do the upgrade for spring modules because the Spring community requires Java 17. 
• Logging improvements
  • Only applies to Java based modules
  • All modules that EPAM teams are responsible for should do it BUT we encourage all teams to consider this work. 
  • Taras: Will meet with Tech Leads to discuss approach as depending on module this work could take a significant amount of effort. 
• stripes 

Key Stats to review:

• 1916 Open Features
• 1 Draft Features
• 1 Refinement/Analysis Complete Features
• 28 35 In Progress Features

NOTE: Only one sprint left for new development. Please update status, release, and/or split feature. If a feature is a MUST for Nolana and it is at-risk, please add the label nolana-at-risk to the feature. If your new feature will not be ready for the start of Bugfest then add the label nolana-at-risk to the feature.

Nolana - no change in release date (December 12)

1. 1. Sprint 149: September 30 - Deadline for TC to accept new modules. 
   2. Sprint 150 (In Progress)
      1. New Development Freeze  - Core (October 7) 
      2. New Development Freeze  - Complete (October 14)  
      3. Sprint 150-152 
         1. Nolana release hardening (initial) 
   3. Sprint 152 - Bugfest

Ways to help manage wrapping up new development for release

• Dennis
  • Visuals 
  • Wiki pages with test cases 
  • More collaborative discussions with team to identify edge cases 

Every release does not need to include new and major functionality. Sometimes you need to let the app/module breathe and focus on correcting bugs/defects, add more tests, and improve performance (if applicable). 

1. Sprint 150: Orchid scope finalized (proposed date October 10)
   
   1. Features defined and reviewed with team 
   2. Development estimates complete
2. Sprint 152: Orchid new development officially begins [October 31 (based on module release deadline)]... but can start before...

Next steps:

1. Next week: POs will start to review features with development team.

2. KG will ask Oleksii to change scope finalization date to October 17. 

Action item: Ask PC - about community prioritizationAnother note: Deactivating the codex app includes all backend and fronted modules. 

Action item: KG to inform folio-implementers channel (Suggested by ErinN.) 

• Julie's PO recruitment slack message: https://folio-project.slack.com/archives/G9FUXCJDD/p1665387643883419
• RA SIG Exercise: Gathering requirements collaboratively  - 2022-09-19 Resource Access Meeting Notes