Versions Compared

Old Version 1

changes.mady.by.user Dragan Ivanovic

Saved on

compared with

New Version Current

changes.mady.by.user Dragan Ivanovic

Saved on

Key

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

...

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

Agenda

...

  1. JIRA filters for old JIRA repository
  2. Repository for angular components
  3. Release candidate 5 (VIVO 1.14.0)
    1. Release Testing - VIVO 1.14.0

    2. New Features Tests (response summary) : these tests exercise new functionality in version 1.14.0. 

    3. Standard UI Tests (response summary) : these tests exercise standard functionality in the VIVO user interface.

      4. Advanced Tests (response summary) : these tests are intended for software developers.Release Announcement
      1. https://repo1.maven.org/maven2/org/vivoweb/
      2. https://mvnrepository.com/artifact/org.vivoweb
    4. 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
    5. 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
    6. Release process
      1. VIVO Release Process
        1. decoupling scripts for publishing Vitro release from VIVO release??
        2. removing tags and branches ??
  4. VIVO 1.15.0
      features
      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
    1. Release Notes
      1. We might use the Vitro-angular repository as a repository of angular generic components. At the beginning the building and packing component into VIVO application might be a manual process, later we can do automatisation. It would be nice to have guidelines for development of components. 
      2. It looks like we are ready for releasing VIVO 1.14.0. Dragan will wait for a confirmation from Milos Popovic that loading and removing models are working properly, and if everything is ok will start with publishing the release.
      3. Dragan would like to start with reviewing and testing VIVO 1.15.0 RC 1 in September. The upgrade to Jena 4 (or even Jena 5) might be postponed for VIVO 1.16.0. PR for improving build and deployment process should be tested with a tomcat server with multiple instances of VIVO. Code style improvements will be done incrementally. The build GitHub action will fail if any new class is not aligned with code style. Moreover, in the case of some significant refactoring of some classes PR reviewers might require an additional commit with code reformatting for those classes. 
      4. The committers’ meetings will be organized weekly during the summer period.   
        5. We should try to encourage VIVO developers / adopters to be more involved in Tech meetings. We need their voices and reporting the issues they are struggling with
        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

      •   Dragan Ivanovic to clean up RC tags and branches
      •  Dragan Ivanovic to open a ticket for CodeQL GitHub action issue and to create PR for fixing that.

      Previous actions 

      Previous actions 

      ...