...
...
- Registration for the Slack channel
- Strategy for publishing April release
- Completion of PRs reviewing and Merging PRs
- Removing spring dependency - https://github.com/vivo-project/VIVO/issues/3686
- Deletion of individuals - https://github.com/vivo-project/Vitro/pull/213, https://github.com/vivo-project/Vitro-languages/pull/44
- Upgrade of the orcid-api-client - https://github.com/vivo-project/VIVO/pull/3694
- Prevent copying pom file to home directory - https://github.com/vivo-project/Vitro/pull/288, https://github.com/vivo-project/VIVO/pull/3689
- I18n regression fix - https://github.com/vivo-project/Vitro/pull/289
- Update license - https://github.com/vivo-project/Vitro/pull/290, https://github.com/vivo-project/VIVO/pull/3691, https://github.com/vivo-project/VIVO/issues/3692
- Publishing a release candidate
- 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
- 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:
- Uploading files associated with individuals
- In review
- Configuration of email SMTP server - Minimum Configuration
- In review
- online localization editor - Developing a New Interface Language for VIVO
- In review
- SPARQL Update API
- Done
- Release Notes
- Installing VIVO
- Uploading files associated with individuals
- Publishing VIVO 1.13.0
- Completion of PRs reviewing and Merging PRs
- Dynamic API Sprint
- Requirements for JS and CSS framework selection - https://docs.google.com/spreadsheets/d/1p-86FdqQR2SpFIsK5Xa-k6Dgm5ORg6Lrc7eeOEetm8g/edit?usp=sharing
- 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 -
- Decoupling build and installation process
...