...
- Strategy for publishing the 1.13.0 release
- Completion of PRs reviewing and Merging PRs
- Removing spring dependency - https://github.com/vivo-project/VIVO/pull/3697
- 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
- Fixing Deploy GitHub action - https://github.com/vivo-project/VIVO/pull/3700
- Named graph export name - https://github.com/vivo-project/Vitro/pull/291
- 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
- To create a GitHub repository
- https://github.com/vivo-project/Vitro-angular
- Initial commit
- what should be there?
- how to generate that (angular CLI, universal starter, etc.)
- good practices - the initial commit from other repositories (https://github.com/DSpace/dspace-angular/commit/a5735569633c9f7b947ed33d11540c39d8b0e077)
- Branches
- GitHub Actions
- Initial commit
- Can some generator of Angular client based on the OpenAPI specification be useful? How?
- https://github.com/vivo-project/Vitro-angular
- To rename the branch for dynamic api
- Converting vitro-dynamic-api.owl to vitro-dynamic-api.n3
- To create a GitHub repository
Notes
- Dragan: hope to create release candidate this weekend (before sprint) for testing (using Google forms) during the sprint period
- VIVO PR 3700 merged; should fix automated build errors.
- Brian will try to review https://github.com/vivo-project/Vitro/pull/213,https://github.com/vivo-project/Vitro-languages/pull/44 (bulk-deleting individuals) tomorrow so it can get included in the release
- Benjamin to test https://github.com/vivo-project/Vitro/pull/288,https://github.com/vivo-project/VIVO/pull/3689
- https://github.com/vivo-project/VIVO/pull/3694 is merged
- Brian to test https://github.com/vivo-project/Vitro/pull/289
- https://github.com/vivo-project/Vitro/pull/291 is now merged
- Release candidate should be announced via Slack and mailing lists; Dragan will also check with Michele about directly contacting active VIVO sites
- Next sprint has six registered members. Input from others always welcome.
- Use non-date-based branch name?
- Optional steps in dynamic API?
- Does OpenAPI spec support default values?
- Conditionals cannot return to previously-defined steps
...