Closed jvendetti closed 1 year ago
Hi @jvendetti , thanks for this detailed PR. I merged it (even if it needs the updated API code also to work)
I wanted to create a release in this repo, but do you think that we should start again from v1.0.0 or use the latest version of Bioportal v6.10.5.
Personally, I think v6.10.5 (Bioportal version) is better
Hi @syphax-bouazzouni. Apologies about the ontologies_api_client gem - I should have submitted a pull request for that one at the same time. I'll take care of it in the next couple of business days (we're off on Monday for the Memorial Day holiday).
With regard to the versioning, I didn't understand which you preferred. Starting again from v1.0.0?
I think v6.10.5 (Bioportal version) is better. (sorry my English is still not to that good)
I like your English. 😄
I'm not sure what to say about the tag names. Initially I thought it would be good for OntoPortal to have it's own versioning scheme that's independent of BioPortal. However, I'm interested in your point of view about why you think the other way is better. I don't think I feel strongly either way.
And - there's the issue of the Rails Gemfile pointing to an ncbo tag, which isn't so nice:
Will vote for staying with the tags from BioPortal (6.8 and so forth OR only the last one 6.10.5).... otherwise we are going to loose the historical relation with BioPortal's code. Considering the OntoPortal repo only contains code (master brnach) from BioPortal ... its ok to keep the same tags. We will see in the future if they evolve differently.
The purpose of this pull request is to merge BioPortal's master branch with OntoPortal's master branch to bring OntoPortal up-to-date with the latest code from the last several BioPortal releases (versions 6.8.2 through 6.10.5).
To follow are slightly abbreviated release notes for the above-mentioned release range.
6.8.2
6.9.0
6.10.0
6.10.1
6.10.2
6.10.3
6.10.4
6.10.5