Date

Call-in Information

Time: 10:00 am, Eastern Time

Attendees

(star)  Indicating note-taker

  1. Dragan Ivanovic 
  2. William Welling 
  3. Brian Lowe  
  4. Georgy Litvinov (star)  

Agenda

  1. VIVO 1.14.0
    1. VIVO 1.14.0 Release Announcement
      1. https://repo1.maven.org/maven2/org/vivoweb/
      2. https://mvnrepository.com/artifact/org.vivoweb
    2. Sonatype Lift reports
      1. VIVO - https://sbom.lift.sonatype.com/report/T1-118f0f57da8c6b3097cc-5c65f36277df-1688553698-5e77ced0b59241b2b152ad8f4b1f27fd
      2. Vitro - https://sbom.lift.sonatype.com/report/T1-118f0f57da8c6b3097cc-5c65f36277df-1688553504-100eac36d1c041d0add87254fa18fd07
    3. CodeQL analysis
      1. https://github.com/vivo-project/VIVO/actions/runs/5472056043
      2. https://github.blog/changelog/2023-01-18-code-scanning-codeql-action-v1-is-now-deprecated/#what-do-i-need-to-change-in-my-workflow
      3. https://github.com/vivo-project/VIVO/blob/main/.github/workflows/codeql-analysis.yml
    4. Release process
      1. VIVO Release Process
        1. decoupling scripts for publishing Vitro release from VIVO release??
        2. removing tags and branches ??
  2. VIVO 1.15.0
    1.  features
      • REST API (person, org unit, research)
      • Search filters (extended search)
      • Audit module (change tracking)
    2. Improvements
      • Advanced role management system (ABAC) 
      • Jena 4
      • Improved build and deployment process
      • Code style improvements
  3. Release Notes
    1. JIRA filters for old JIRA repository

Notes

Dragan briefly presented sonetype lift reports, there is no any critical issue, although there are some vulnerabilities with some dependencies which might be upgraded. 

CodeQL GitHub action is failing. Dragan will create an issue and PR for fixing this. 

We agreed Vitro and VIVO releasing processes should be decoupled. The goal is to release Vitro, and then in the process of releasing VIVO to download Vitro from the maven repository, instead of building Vitro from the source. Dragan will try to implement this before the next release.

Release candidates tags and branches should be removed after publishing release. There should be only the branch rel-1.X.X-maint in the case some patch should be published. 

We should work on the plan of merging existing PRs which should be part of the next release. Not sure that Jena 4 upgrade will be ready, and also it looks as Jena 5 is close to being published, maybe we should upgrade from Jena 3 to Jena 5 directly in VIVO 1.16.0 or later.

Draft notes on Google Drive

Actions

Previous actions 

  • No labels

All content on the LYRASIS Wiki is licensed under the CC BY (Attribution) license, unless otherwise noted.