Page Comparison

...

• R/W CICO - Development: Vega   -

  Jira Legacy
  server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key CIRC-1777

  • Implementation:

    Jira Legacy
    server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key CIRC-1788

...

• R/W Data import : Folijet 

  Jira Legacy
  server System JiraJIRA columnIds issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key MODSOURMAN-966

   

...

• R/W Acquisitions 
  • Implementation:
    • mod-invoice-storage //waiting verification from PTF team
    • mod-organization-storage //waiting verification from PTF team
    • mod-orders //waiting verification from PTF team
    • mod-orders-storage //waiting verification from PTF team
    • mod-finance-storage

      Jira Legacy
      server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key MODFISTO-402

      (separate feature created

      Jira Legacy
      server System JIRA columnIds issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key UXPROD-4321

      XXL size, PO decided to move to Q release as it's too risky to implement it in Poppy)
  • Team Testing - enable R/W  MODFISTO
    • Enable RW split on Orchid bugfest -

      Jira Legacy
      server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key BF-496

       
      • Execute Katare test before and after enabling
      • Execute E2E test after enabling
    • Manual QA and AQA smoke testing 
    • PO smoke testing
    • PTF testing  
      •  mod-invoice-storage
      •  mod-organization-storage
      •  mod-orders
      •  mod-orders-storage
      •  mod-finance-storage

• Challenges
  
  • Teams cannot do unit testing until

    Jira Legacy
    server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key RMB-938

     

...

•  Kitfox: add possibility to test RW split on Rancher env

• • Jira Legacy
    server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key RANCHER-765

  • Jira Legacy
    server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key RANCHER-764

  • Jira Legacy
    server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key RANCHER-766

•  Martin to discuss R/W to Folijet and Vega dev leads and determine work required
•  Vega and Folijet dev leads need to create user stories. 
•  Vega review 

  Jira Legacy
  server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key CIRC-1666

  and possibly re-open issue. Will be done under

  Jira Legacy
  server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key CIRC-1788

•  Martin/Oleksii/Sasha B. define a test plan (including environments) for for - Planned be ready for review at 30 Jun 2023 
  •  Development/QA
  •  PO 
  •  PTF
•  Martin to define technical definition of done 
•  Khalilah to discuss with Steph and Ann-Marie that this work maybe included in Poppy based on technical discussion and creation of requirements
•  Martin to create a UXPROD feature for Poppy 

...

Q Poppy2 Release and beyond

Next steps

•  Martin to create a UXPROD feature/epic to describe the business value of this change. 

• • Jira Legacy
    server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key FOLIO-3753

•  Martin to link already created stories to UXPROD feature/epic 
•  Martin to discuss with key stakeholders need to implement feature/epic and recommended completion date 
  •  Oleksii to schedule call with Mark, Lee, Yogesh, Sobha, Vince, Olamide, Vijay 
•  Based on key stakeholders, release manager/PO lead/PM  will work with Martin to outline an implementation plan (if necessary) 
•  Martin will discuss feature with dev leads
•  Testing plan must be discussed
•  PO lead will coordinate a meeting to discuss with POs
•  Oleksii/Denis?  will monitor implementation status 

...

• OAI-PMH (Poppy)

  • Jira Legacy
    server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key MODOAIPMH-457

  • Jira Legacy
    server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key MODOAIPMH-445

...

• All storage modules 

  • Jira Legacy
    server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key MODINVSTOR-960

  • Jira Legacy
    server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key CIRCSTORE-359

  • Jira Legacy
    server System JIRA columnIds issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key UXPROD-4321

...

Miscellaneous

Questions

1. What about spring modules? [grab from TC document]
   1. Discuss with SpringForce team → Oleksii Petrenko
2. How can we test earlier? 
   1. We can. Implemented support on Rancher
   2. Steve implemented RMB-938 to execute unit tests
3. How to make sure this is enabled in bugfest environment?
   1. Include RW enable step to Poppy bugfest environment preparation plan → Oleksii Petrenko 
4. How is this tested to determine performance improvements before any code changes are made? 
   1. Include to RW split testing strategy (baseline, functional aspect) → Oleksandr Bashtynskyi 
   2. Define scope of workflows for modules that support RW Split → Martin Tran 

To Do: 

• Get a recording (TC)