Page History

...

1. Publishing the VIVO 1.13.0 release 
   1. Publishing a release candidate 2
      1. done
   2. i18n issue with ordering and filtering by the first letter 
      1. https://github.com/vivo-project/Vitro/pull/321
      2. https://github.com/vivo-project/vivo-solr/pull/6
   3. use public description in data property template model
      1. https://github.com/vivo-project/Vitro/pull/322/files
   4. Privilages for editing grant contributors
      1. https://github.com/vivo-project/VIVO/pull/3734
   5. Publishing a release candidate 3
      1. to be done
   6. Testing the release candidate
      1. for release candidate only new fixes should be tested (1a, 1b, 1c) 
      2. Wiki page - Release Testing - 1.13.0 
         1. deployment of VIVO and Vitro
            1. mvn clean install
         2. GoogleForms
            1. Standard tests - https://forms.gle/cqk3oK7UmJpDWGYt8
            2. Special focus on the new features - https://docs.google.com/forms/d/19FMslvvSzg_FK-Wmxg4t7EOP2UDft4FVdQvM4-2IO50/edit?usp=sharing
            3. Advanced tests - https://forms.gle/ZZLeVdBuDFMEMTGM
         3. https://vivo.tib.eu/vivo113rc
   7. VIVO 1.13.0 Technical Documentation
      1. Wiki space - VIVODOC113x
      2. Adding of technical documentation for:
         1. Deletion of individuals 
         2. Installing VIVO
      3.  Release Notes
         1. doneto be updated
   8. Publishing VIVO 1.13.0 
2. Improvement of GitHub code management 
   1. bug report template
      1. VIVO
      2. DSpace
   2. feature request template
      1. VIVO
      2. DSpace
   3. task definition template
      1. for upgrading dependencies, mitigation of security vulnerability
      2. is that a good practice?
         1. https://github.com/golang/go/issues/new/choose
         2. https://github.com/microsoft/repo-templates/blob/main/shared/SECURITY.md
         3. https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository
         4. https://github.com/DSpace/DSpace/issues/new/choose
   4. pull request template
      1. VIVO
      2. DSpace
   5. GitHub actions
      1. list of actions
         1. VIVO
         2. DSpace
      2. build.yml
         1. VIVO
         2. DSpace
            1. codecov
               1. alternatives - codeclimate, etc.
            2. separation of unit and integration tests
      3. docker.yml
         1. VIVO
         2. DSpace
      4. label merge conflicts yml
         1. DSpace
      5. adding new issue to project board yml
         1. DSpace
            1. 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)
      6. codeQL analysis
         1. VIVO
         2. continues security analysis - LGTM
            1. https://lgtm.com/projects/g/vivo-project/Vitro/?mode=list
   6. labels
      1. list of labels
         1. VIVO
         2. DSpace
      2. assignment of labels to issues
         1. VIVO
         2. DSpace
3. Decoupling build and installation process 
   1. https://github.com/vivo-project/VIVO/issues/3034

...