VIVO-release-publisher

Before using scripts available in this project please check whether:

1. You have an account with commit access for the vivo-project on github. As a committer, you should already have this level of access.
2. You have an account with edit privileges on the lyrasis.org Confluence wiki.
3. You have an oss.sonatype.org account and have requested to be given permission to publish to the org.vivoweb groupId by adding a comment to the VIVO Sonatype Hosting Ticket
4. You have configured maven settings file in accordance with instructions available at - https://wiki.lyrasis.org/display/VIVO/VIVO+Release+Process

Configuration

Please, configure variables in defineVariables.sh. You can test publishing process over forked version of vivo-project repositories, in that case variable ORG is set up to your github account, while PERSONAL_ACCESS_TOKEN is set up to token configured for your github repositories.

Preparing release candidate

1. Open a bash (Git bash or Linux terminal)
2. Run ./prepareReleaseCandidate.sh
3. Check whether a new branch and new tag are created in both repositories (VIVO and Vitro)
4. Create a wiki page with release candidate testing instructions (you can copy this one)
5. Announce in the VIVO dissemination channels (mailing lists, Slack channels) that new release candidate is published, define deadline in the announcement for testing and providing feedback 1If some requests or important issues have been noticed since the moment of making announcement in the point 5 in the section above, consider with VIVO tech group fixing that and publishing the new release candidate (2, 3, 4, ...). If there is no, go to the next point.

Publishing a Vitro release

1. Run ./publishReleaseVitro.sh
2. Check new release in the Vitro GitHub repository
   1. https://github.com/vivo-project/Vitro/releases/
3. Complete publishing process via central sonatype repository
   1. Go to https://central.sonatype.com/ (Maven Central Repository)
   2. Click on Log In (Top Right Corner) and use your central sonatype id from your settings.xml file
   3. Click Publish in top right corner and click on Deployments
   4. Check whether everything looks ok  - war, pom, jar, md5, asc, etc.
   5. If everything is ok, Click on Publish (otherwise Click on Drop and fix the issue and start releasing process again) 
   6. In a couple of minutes, new artefacts will be available at https://repo1.maven.org/maven2/org/vivoweb.

Publishing a VIVO release

1. Wait until the Vitro release is available in the maven repository (http://repo1.maven.org/maven2/org/vivoweb). This make take several hours or one day.
2. Run ./publishReleaseVIVO.sh
3. Check new release in the VIVO GitHub repository
   1. https://github.com/vivo-project/VIVO/releases/
4. Complete publishing process via central sonatype repository
   1. Go to https://central.sonatype.com/ (Maven Central Repository)
   2. Click on Log In (Top Right Corner) and use your central sonatype id from your settings.xml file
   3. Click Publish in top right corner and click on Deployments
   4. Check whether everything looks ok  - war, pom, jar, md5, asc, etc.
   5. If everything is ok, Click on Publish (otherwise Click on Drop and fix the issue and start releasing process again) 
   6. In a couple of minutes, new artefacts will be available at https://repo1.maven.org/maven2/org/vivoweb.
5. Make release announcement and update technical documentation at wiki
6. Distribute the message that new release has been published

Push Release Branch to develop and Maintenance

1. Run ./pushToMaintenance.sh
2. Manually check the GitHub repositories branches and tags, as well as the main branch (pom.xml files should be updated to include new version number)