Core: Platform Sync Up

Core: Platform Sync Up

Action Items

Action Item 

JIRA

Assignee 

Status

Action Item 

JIRA

Assignee 

Status

Add tickets for the performance testing and probably some integration tasting and speak to guys to organize it after the  code frieze 

 

Jakub

 

Create tickets for RMB-777

We have decided not to address RMB-777 but instead address https://folio-org.atlassian.net/browse/MODINVSTOR-656

Jakub

DONE

Create confl page and document approach for breaking up large tickets and helping avoid (or at least reduce)  spillovers. 

Creating preparation (Clean up tasks) for feature. As this work is not related with a story itself but  need to be done to implement feature. 

Dealing with spillovers

Jakub

Initial guidance published

Create ticket for updating schemas (RMB-777)

 

Jakub

 

Investigate if there is something really critical in  pac4j-4.4.0. Create ticket to Julian to bring to security team

 

Jakub

 

Have karate tests demo (Steve to demo)

 

Jakub

 

Jira tickets to highlight 

Jira Ticket

Question/Highlight

PO decision/response 

Jira Ticket

Question/Highlight

PO decision/response 

https://folio-org.atlassian.net/browse/RMB-601 

https://folio-org.atlassian.net/browse/RMB-602

https://folio-org.atlassian.net/browse/RMB-783

From @Julian Ladisch

We should not migrate more modules to Vert.x 4 before we have futurized RMB. Please create a futurisation Jira for each module that we already have migrated to Vert.x 4 so that we can migrate them to the RMB futurisation after RMB-601, RMB-602 and RMB-783 have released.

 

 

 

 

 

 

 

Core: Platform Agile Board:

Scrum: https://folio-org.atlassian.net/secure/RapidBoard.jspa?rapidView=80
Kanban: https://folio-org.atlassian.net/secure/RapidBoard.jspa?rapidView=183

R1/R2 planning:

R1/R2 planning google doc

Next Grooming

PlanITpoker room: https://www.planitpoker.com/board/#/room/2ba248faecdf46f399bf2a248c5c750f