...

1. Releases management
   1. How to simplify publishing releases? 

2. Moving forward reviewing PRs on VIVO and Vitro

   1. https://github.com/vivo-project/Vitro/pulls and https://github.com/vivo-project/VIVO/pulls
   2. Tiny and big PRs classification
   3. Assignment of reviewers
3. VIVO 2.0 architecture
   1. https://docs.google.com/document/d/1z51mkqlAopQ2rLkitHiQVwRojijnPM9pB8tQelW-lSA/edit?usp=sharing

Notes

1. Releases management
1. How to simplify publishing releases? 
2. Issue with pom file signing?
1. Ralph: Specific to ones in the installer. Artifact was created but signature was not. Because of that, they weren’t accepted by Sonatype. May have to do with the multiple pom files across the project.
2. Might have to do with changes that were made for .war deployment. 
3. Ralph was going to step back through changes to rectify difference in pom files
4. Brian: Changes to pom should predate 1.12.0.
5. Ralph: 1.12.0 didn’t work either. 
6. Brian: Presumably if the bigger bug in 1.12.0 release wasn’t there, we would have had same problem with signature. 
7. Brian: Had been thinking it was just Vitro that was having an issue deploying. But installer is only VIVO.
8. Snapshots don’t need signed. Those worked. Releases must be signed. That’s not happening.
9. https://oss.sonatype.org/#nexus-search;gav~org.vivoweb~vivo-installer~~~~kw,versionexpand to explore things on sonatype
10. Has the installer somehow become a dependency of another artifact at some point? Check - grab vivo installer and search all poms for the artifact ID… it shouldn’t be in any other pom. Installer home and installer webapp do have the installer as a dependency… but it’s under the installer so that’s to be expected. 
11. The installer was never published before. Never has a release in https://mvnrepository.com/artifact/org.vivoweb?p=2&sort=newest
    
    

    
    

    
    

12. 1.11.1 vs 1.12.1-RC VIVO/installer/pom.xml 
    Image Added Image Added

13. Ralph: Hoping to nuke 1.12.0 mentions everywhere

    Benjamin: Note it’s currently linked from vivoweb.org

    William: Any way to get messages into Maven central to tell people 1.12.0 isn’t functional? 

2. Looking forward. Could Lyrasis host their own sonatype repo? So we can deal with issues like this more easily.
1. How about releasing via GitHub? 
2. William: Argument against: Single point of failure 
3. Ralph: Could deploy to both sonatype and GitHub for awhile? 
4. William: I’ve used GitHub’s npm, but requires a personal access token to access. Which would be a setback if that’s required for java projects as well. 

Draft notes on Google Drive

Actions 

•   Ralph O'Flinn To investigate reversing publishing VIVO installer artifact to Sonatype 

Previous actions 

•   Ralph O'Flinn first pass through PRs and sending out an email to other committers
•  All to read and provide feedback for   VIVO 2.0 architecture https://docs.google.com/document/d/1z51mkqlAopQ2rLkitHiQVwRojijnPM9pB8tQelW-lSA/edit?usp=sharing
•