-
Notifications
You must be signed in to change notification settings - Fork 17
Make OGMS ontology release
jie zheng edited this page Sep 8, 2021
·
1 revision
-
Make OGMS ontology release file
- git clone ogms repository, `git clone https://github.com/OGMS/ogms.git'
- Run "Makefile" in the ogms repository by command
make
, it will generate the release file, ogms.owl and ogms.obo, in the same directory as "Makefile".
-
Review ogms.owl
- Review ogms.owl and fix issues in the development version if there are any. Rerun Makefile if any changes made in the development version.
- An issue report file, report.tsv, will be generated under build directory
- Removed temporary directory and files generated during the release process by command
make clean
-
Go through Github release process
- Click 'Releases' at right side bar at OGMS/ogms page (https://github.com/OGMS/ogms) or go to page: https://github.com/OGMS/ogms/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 (v: version, yyyy: year in 4 digits, mm: month in 2 digits, and dd: days in 2 digits)
- 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. Then click "Publish release"
- When we decide to make the official release, go to the release page and uncheck "This is a pre-release". Then click "Publish release"
-
Add new release PURL
- Go to OGMS ontology purl configuration file on oboFoundry purl repository: https://github.com/OBOFoundry/purl.obolibrary.org/blob/master/config/ogms.yml
- Click the edit button to make the following two changes:
- Point ogms.owl and ogms.obo to the locations of the latest release file under "products:" section
- Add the new version IRI to the latest release file under "entries:" section
- Create a pull request after making the changes and wait for automatic validation and administrator approval of the changes
-
The latest release will be uploaded automatically to ontoBee and Bioportal
- The ontobee server will load the new ontology version over the weekend
- Bioportal will index the new ontology version. Generally, it will take about 1 week to make a new ontology version ready to show on the site.