Over at the MIxS-DwC mapping group, we're encountering the need to reliably track the release version of each specification, and be able to reliably detect new releases.
DwC uses GitHub's release process and tags, which makes it quite easy to write triggers.
Could we use the same feature for future MIxS releases? Coupling this to a Zenodo DOI generation routine would be even better, as this would be more sustainably archived.
Over at the MIxS-DwC mapping group, we're encountering the need to reliably track the release version of each specification, and be able to reliably detect new releases.
DwC uses GitHub's release process and tags, which makes it quite easy to write triggers.
Could we use the same feature for future MIxS releases? Coupling this to a Zenodo DOI generation routine would be even better, as this would be more sustainably archived.