OHMI release process

1. Make OHMI ontology release file

• git clone https://github.com/OHMI-ontology/OHMI.git (OHMI-ontology/OHMI repository)

• Run "Makefile" in the OHMI-ontology/OHMI repository, it will generate the release file, ohmi.owl, in the same directory as "Makefile".

• The command of running Makefile is: make

2. Review ohmi.owl

• Review ohmi.owl and fix issues in the development version if there are any.
• Rerun Makefile if any changes made in the development version.

3. Go through Github release process

• Click 'releases' at top menu bar at OHMI-ontology/OHMI page or go to page: https://github.com/https://github.com/OHMI-ontology/OHMI/releases
• Click 'draft a new release' button on the release page
• Fill the release associated information in the form
  • Provide the release date in the format vYYYY-MM-DD as tag version (year(YYYY), month(MM) and day(DD) when the release file generated)
  • Provide release title
  • Provide release notes (can be edited later)
• Check "This is a pre-release" when we consider it is a release candidate for review
• Click "Publish release"
• When we decide to make the official release, go to the release page and uncheck "This is a pre-release".

4. Add PURL for new release

• Go to OHMI purl configuration file on oboFoundry purl repository: https://github.com/OBOFoundry/purl.obolibrary.org/blob/master/config/ohmi.yml
• Point ohmi.owl to location of the latest release file
• Add version IRI to the latest release file

5. The latest release will be uploaded automatically to the ontoBee and Bioportal

• The ontobee server loads new version of ontology every weekend
• The bioportal will add index to the new ontology. Generally, it will take about 1 week for making a new ontology ready to show on the site.