New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Please improve release process #46
Comments
Note that the ontology file does have the ontology version:
|
I've had a stab at automating the build process: https://gitlab.desy.de/paul.millar/panet-build/-/tree/main This is work-in-progress, as there are non-trivial differences between the generated |
I've started writing documentation on how to do a release and, in fact, all aspects of managing the PaNET ontology: https://docs.google.com/document/d/1ydLMZnHqu2Btg_QruZwokzXGeZ6UQjmeZOmrKEufdSs/edit?usp=sharing |
There's a number of points:
releases/latest-release
is poorly defined. Nothing says which version this is: neither the file nor the ontology contains version information.releases/latest-release/PaNET.owl
is newer than the latest tag (v1.0.0), why is there no v1.0.1 tag?releases/
directory is missing the v1.0.0 release.releases/
directory seems sub-optimal. The contents are normal files. Any commit can modify their contents. This can lead to inconsistencies where a file inreleases/
directory that claims to be v1.0.0 (at the HEAD ofmaster
branch) yields different contents from the filesource/PaNET.owl
tagged with v1.0.0.Review process and release
. However, this does not describe the release process, only how to handle a pull/merge request.My suggestions:
This is more than just accepting changes to
master
(accepting pull-requests), but rather identifying a specific point-in-time that may be referred to unambiguously.It may be worth considering the frequency in which releases will take place (how often do you expect services to update?). It may also be worth considering how updates and releases will take place once ExPaNDS ends.
So, I think it would be worth documenting the answers to:
I've seen that there's already a
v1.0.0
tag, which is good. However, this version has been outdated since 2021-06-18. More than six months later there is nov1.0.1
tag.Putting releases in a
releases/
directory really isn't good. You could try to come up with a github-only solution, but please consider publishing to Zenodo. They already solves this problem. Plus you get a DOI for the ontology.For comparison, ROR publish to Zenodo: see "ROR data dump" here https://ror.org/facts/
The text was updated successfully, but these errors were encountered: