obophenotype / obophenotype/ncbitaxon
Changing purls to GitHub and Release plan
Open
@cmungall is already working on this.
Since Apr 19, 2020.
- Dominant language
- Python
- Stars
- 31
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Description
We have now changed the primary release purls to github releases. However, I have no idea how to handle any old versions (in the OBO yaml config).. Should we create links to any old versions manually? If so, someone with access should provide a list of old version paths or, better yet, edit the ncbitaxon.yaml.
The second thing are the subsets; I just added them to the github release the same way I add the primary artefacts, hope that is ok.
Lastly, how often do we want ncbitaxon to be released properly? Monthly? Quarterly?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.