...
- When and how to align codebase with codestyle?
- Sample data
- loading large sample data
- Decoupling build and deployment
- Vitro?
Notes
- Not yet ready to align codebase with codestyle, it might introduce a lot of merge conflicts in the community customizations/forks and branches (such as Dynamic api branch). Georgy suggested to be strict only with new files which should be aligned with codestyle.
- There is OutOfMemory issue with loading large sample data. openVIVO sample data might be loaded with a 4GB heap for tomcat, but can’t with 2GB. Splitting files into smaller ones is not resolving the issue.
- Practice of upgrading VIVO within the VIVO community is unclear, therefore it is hard to estimate how many cases https://github.com/vivo-project/Vitro/pull/370 is covering. Anyway, it is a step forward, it decouples the building and deployment process and we should adopt that as a solution after reviewing and testing.
- Dragan will prepare VIVO 1.14.0 release candidate number 2, after the testing of release candidate number 1. RC 2 will at least include fixes for some bugs in RC 1 already fixed by Georgy, plus it will include Kevin's contribution for adding a flag for disabling MapOfScience if that is needed for some VIVO adopters.
...