Versions Compared

Key

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

Table of Contents

...

Action Item JIRAAssignee 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

Jira Legacy
serverSystem Jira
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyMODINVSTOR-656

JakubDONE

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. 

JakubInitial 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

Jira tickets to highlight 

Jira TicketQuestion/HighlightPO decision/response 

Jira Legacy
serverSystem Jira
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyRMB-601
 

Jira Legacy
serverSystem Jira
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyRMB-602

Jira Legacy
serverSystem Jira
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyRMB-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:

...