...

1. Strategy for publishing the 1.13.0 release 
   
   1. Completion of PRs reviewing and Merging PRs
      
      1. fix: process string and untyped literals differently - https://github.com/vivo-project/Vitro/pull/296
   2. Publishing a release candidate 2
   3. Testing the release candidate
      1. Wiki page - Release Testing - 1.13.0 
         1. deployment of VIVO and Vitro
            1. mvn clean install
         2. GoogleForms
            1. Standard tests - https://forms.gle/cqk3oK7UmJpDWGYt8
            2. Special focus on the new features - https://docs.google.com/forms/d/19FMslvvSzg_FK-Wmxg4t7EOP2UDft4FVdQvM4-2IO50/edit?usp=sharing
            3. Advanced tests - https://forms.gle/ZZLeVdBuDFMEMTGM
   4. VIVO 1.13.0 Technical Documentation
      1. Wiki space - VIVODOC113x
      2. Adding of technical documentation for:
         1. Deletion of individuals 
         2. Installing VIVO
   5. Publishing VIVO 1.13.0 
2. Jena issue

Notes

• Publishing 1.13. One PRGeorgy: There is a regression with new PR that creates a regression in editing of labels with string data types. We need to resolve the regression.

Brian: We might not have enough time to test it one more time https://vivo-project.atlassian.net/browse/VIVO-1983

Georgy: We need more testing

• Deletion needs more documentation
• Jena issue. We need to create a ticket for Jena.
• Sprint planning 
• August or September? 
• Running into following sprint if we choose September. Dragan is available for both.
• Topic for next sprint?
• Who can participate? We’ll follow up in the next couple weeks.
• Work over summer
• Regular meetings over July, then biweekly meetings?
• Or biweekly for July and August
• Issue posted to vivo-tech
• https://groups.google.com/g/vivo-tech/c/0fyz7yRnJ9Y
• Why are they using v1.9?

Draft notes on Google Drive

Actions

•  Georgy Litvinov to open a Jena ticket 

Previous actions 

•  Ralph O'Flinn to help with Preparing Documentation for Release by coping space VIVO 1.12.x Documentation to the space VIVO 1.13.x Documentation (or to grant Dragan Ivanovic permissions to do that)
•  Dragan Ivanovic to work on documenting new features for VIVO 1.13.x Documentation
•  Dragan Ivanovic to create the third one google form for reporting the testing results, that form should be used for testing new features introduced in VIVO 1.13.0
  •  New Features: https://docs.google.com/forms/d/19FMslvvSzg_FK-Wmxg4t7EOP2UDft4FVdQvM4-2IO50/edit?usp=sharing
•  Everyone to review https://docs.google.com/forms/d/13W2vynR6OmavoV2Px_kJ-k-dlQDv3ERWG0PnXX7ekQA/edit?usp=sharing and https://docs.google.com/forms/d/1dks3b3sJsmM7Q33bwHW_1iVem5VRjg3fqpx8UTFKIfI/edit?usp=sharing
  •  and to review https://docs.google.com/forms/d/19FMslvvSzg_FK-Wmxg4t7EOP2UDft4FVdQvM4-2IO50/edit?usp=sharing
•  Brian Lowe to work on removing spring dependencies (https://github.com/vivo-project/VIVO/issues/3686)
•  Georgy Litvinov to work on PR for merging back a lost fix he noticed
•  Everyone to review spreadsheet for defining requirements for JS and CSS framework selection - https://docs.google.com/spreadsheets/d/1p-86FdqQR2SpFIsK5Xa-k6Dgm5ORg6Lrc7eeOEetm8g/edit?usp=sharing

...