...
Agenda
...
- Repository for angular components
- Release candidate 5 (VIVO 1.14.0)
- Release Testing - VIVO 1.14.0
New Features Tests (response summary) : these tests exercise new functionality in version 1.14.0.
Standard UI Tests (response summary) : these tests exercise standard functionality in the VIVO user interface.
Advanced Tests (response summary) : these tests are intended for software developers.Release Announcement
- Sonatype Lift reports
- CodeQL analysis
- Release process
- VIVO Release Process
- decoupling scripts for publishing Vitro release from VIVO release??
- removing tags and branches ??
- VIVO Release Process
- features
- REST API (person, org unit, research)
- Search filters (extended search)
- Audit module (change tracking)
- Improvements
- Advanced role management system (ABAC)
- Jena 4
- Improved build and deployment process
- Code style improvements
- 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.
- 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.
- 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.
- The committers’ meetings will be organized weekly during the summer period.
- 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.
- JIRA filters for old JIRA repository
Notes
Actions
Previous actions
- Dragan Ivanovic to prepare VIVO 1.14.0 release
Previous actions
- Dragan Ivanovic to prepare release candidate 4
- Georgy Litvinov to align https://vivo.tib.eu/vivorc/ with release candidate 4
- Dragan Ivanovic to respond to slack messages
- Dragan Ivanovic will try to collect wiki pages where strategy, vision and roadmap for development of VIVO were discussed in the past
- Georgy Litvinov will try to address the issue https://github.com/vivo-project/VIVO/issues/3871
- Dragan Ivanovic will ask Michael to open a GitHub ticket for the issue about UF performance during login (https://vivo-project.slack.com/archives/C8RL9L98A/p1684174222986709), Brian Lowe and others can continue discussion about this issue once a ticket is open
- Dragan Ivanovic will ask Rodrigo to open a GitHub ticket for the issue about custom theme and VIVO Docker (https://vivo-project.slack.com/archives/C8RL9L98A/p1684962021101889), William Welling and others can continue discussion about this issue once a ticket is open
- Brian Lowe to open a GitHub issue for index page exception
- https://github.com/vivo-project/VIVO/issues/3867
- add sample (minimal RDF to reproduce the issue)
- Miloš Popović or Ivan Mrsulja to review (https://github.com/vivo-project/VIVO/issues/3862)
- Georgy Litvinov to review (https://github.com/vivo-project/VIVO/issues/3847)
- Review (https://github.com/vivo-project/VIVO/issues/3865)
- Review (https://github.com/vivo-project/VIVO/issues/3864)
- Review (https://github.com/vivo-project/VIVO/issues/3858)
- Review (https://github.com/vivo-project/VIVO/issues/3859)
- Review (https://github.com/vivo-project/VIVO/issues/3855)
- Review (https://github.com/vivo-project/VIVO/security/dependabot/3)
...