...
- Publishing the VIVO 1.13.0 release
- Publishing a release candidate 2
- done
- Testing the release candidate
- Wiki page - Release Testing - 1.13.0
- deployment of VIVO and Vitro
- mvn clean install
- GoogleForms
- Standard tests - https://forms.gle/cqk3oK7UmJpDWGYt8
- Special focus on the new features - https://docs.google.com/forms/d/19FMslvvSzg_FK-Wmxg4t7EOP2UDft4FVdQvM4-2IO50/edit?usp=sharing
- Advanced tests - https://forms.gle/ZZLeVdBuDFMEMTGM
- https://vivo.tib.eu/vivo113rc
- deployment of VIVO and Vitro
- Wiki page - Release Testing - 1.13.0
- VIVO 1.13.0 Technical Documentation
- Wiki space - VIVODOC113x
- Adding of technical documentation for:
- Deletion of individuals
- Installing VIVO
- Release Notes
- done
- Publishing VIVO 1.13.0
- Publishing a release candidate 2
- Improvement of GitHub code management
- bug report template
- feature request template
- task definition template
- for upgrading dependencies, mitigation of security vulnerability
- is that a good practice?
- https://github.com/golang/go/issues/new/choose
- https://github.com/microsoft/repo-templates/blob/main/shared/SECURITY.md
- https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository
- https://github.com/DSpace/DSpace/issues/new/choose
- pull request template
- GitHub actions
- list of actions
- build.yml
- docker.yml
- label merge conflicts yml
- adding new issue to project board yml
- DSpace
- Issues should be added for instance in a dedicated VIVO backlogs project board for triage (similarly as DSpace Backlogs - https://github.com/orgs/DSpace/projects)
- DSpace
- codeQL analysis
- VIVO
- continues security analysis - LGTM
- labels
- Decoupling build and installation process
Notes
- Proxy editing: Issue with assigning profiles to account for editing, but account can edit everything
- Brian: Check role for username. Since it’s “editor”, that means that account can edit everything. Set to “self-editor” to turn off overall editing privileges and then check proxy editing
- Works as intended
- Dragan: Besides that, didn’t notice any issues. Performance also looks ok.
- Situation for being able to edit relationships to others
- Instead of being set to root, appropriate to set that at editor/self-editor level
- Update level: usually editor or self-editor instead of root
- Publish level: should be public as usual
- Dragan: Will try to make a pull request
- Benjamin (from chat):
- Language search issue discussed in dev call earlier
- Brian: Issue is with dynamically adding language with the necessary analyzers
- For different project, had three different document modifiers - processing for each language. Populate fields other than the default used for sorting - three different fields for languages. Then piped in the field based on locale.
- Appears to be an important issue prior to release. So good with intermediate solution with dynamic fields. Maybe language specific analyzers in next release.
- Deadline for testing? Not getting feedback.
- Not a lot of new features. Mostly bug fixes. Could reach out individually to whoever submitted the issue and ask them to confirm the fix works. That’s mostly committers though.
Actions
- Dragan Ivanovic to make a PR for fixing privileges for adding grant collaborators
- Brian Lowe to make a PR for fixing ordering of instances with multilingual properties
- Georgy Litvinov will investigate the problem of searching instances with multilingual properties
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
- 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
- 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
...