Date 21 Apr 2022
Call-in Information Time: 10:00 am, Eastern Time (New York, GMT-04:00)
Attendees Indicating note-taker
Brian Lowe Georgy Litvinov Dragan Ivanovic Huda Khan William Welling Benjamin Gross Ralph O'Flinn Agenda Strategy for publishing April release Completion of PRs reviewing and Merging PRs https://github.com/vivo-project/VIVO/issues/3686 Publishing a release candidate Testing the release candidate Wiki page - Release Testing - 1.13.0 deployment of VIVO and Vitromvn clean install main functionalitieshttps://forms.gle/cqk3oK7UmJpDWGYt8 and special focus on new featuresnew interface translations, online translation feature, upload of files https://docs.google.com/forms/d/1XDmpCa9fLk_-opx7i0aCRCUYZhrnZ0FJZG6-0tx-Orc/viewform Advanced tests for software developershttps://forms.gle/ZZLeVdBuDFMEMTGM7 GoogleFormsStandard tests - https://forms.gle/cqk3oK7UmJpDWGYt8 To add a question about i18n Special focus on the new features - to be defined Advanced tests - https://forms.gle/ZZLeVdBuDFMEMTGM7 Deadline for responses - May 5th VIVO 1.13.0 Technical DocumentationNew space should be added to wiki https://wiki.lyrasis.org/spacedirectory/view.action , and then page should be copied including children Adding of technical documentation for:Uploading files Configuration of email SMTP server online localization editor Deadline April 21st Publishing VIVO 1.13.0 Deadline May 12th Dynamic API SprintRequirements 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 VIVO DSpace feature request template VIVO DSpace pull request template VIVO DSpace GitHub actions list of actions VIVO DSpace build.yml VIVO DSpace docker.yml VIVO DSpace label merge conflicts yml DSpace adding new issue to project board yml DSpace codeQL analysis VIVO labels list of labels VIVO DSpace assignment of labels to issuesVIVO DSpace Notes Dragan: Serbian language PRs merged Dragan: Will have to check if known vulnerabilities are resolved in Jackson, Jena ARQ, and swagger core Maven Repository: com.fasterxml.jackson.core » jackson-databind » 2.13.2.2 (mvnrepository.com) Maven Repository: org.apache.jena » jena-arq » 4.4.0 (mvnrepository.com) Maven Repository: io.swagger.core.v3 » swagger-core » 2.1.13 (mvnrepository.com) Dragan: Should update orcid client version Dragan: Wait for issues in progress for next minor release Brian working on removing spring dependency Georgy working on issue Dragan: Release testing form Standard: https://docs.google.com/forms/d/13W2vynR6OmavoV2Px_kJ-k-dlQDv3ERWG0PnXX7ekQA/edit?usp=sharing Advanced: https://docs.google.com/forms/d/1dks3b3sJsmM7Q33bwHW_1iVem5VRjg3fqpx8UTFKIfI/edit?usp=sharing New Features: https://docs.google.com/forms/d/19FMslvvSzg_FK-Wmxg4t7EOP2UDft4FVdQvM4-2IO50/edit?usp=sharing Performance testing? General issue with inconsistency and concern from minor changes impacting releases performance Brian: should have ability to backport fixes to previous minor releases Ralph: requires discipline in isolated commits for only the fix Benjamin: Don from CU has made requests in the past Dragan: important to have test coverage to ensure patches work for past versions Ralph: good ideas but should be future focus Dragan: how to afford requests for back porting? Brian: implementers not aware or monitoring security vulnerabilities may rely on the community Draft notes on Google Drive
Actions Previous actions