search

evoinfo / cdao

Comparative Data Analysis Ontology - A formalization of concepts and relations relevant to evolutionary comparative analysis
Creative Commons Zero v1.0 Universal
9 stars 4 forks source link

Review of migration from SourceForge #1

Closed hlapp closed 7 years ago

hlapp commented 7 years ago

@balhoff @arlin @epontell @rvosa if you don't mind could you take a moment and check the state and files in this repo for whether it is a faithful migration of the CDAO repository on SourceForge?

hlapp commented 7 years ago

Note that I left the svn-id metadata in the commit messages on purpose. If left out (which is an option) then it'll be very difficult or impossible to resolve any previous references to particular versions in subversion.

hlapp commented 7 years ago

@balhoff as the CDAO maintainer currently on record, could you please take a look and indicate approval or provide comments on actual or potential issues?

balhoff commented 7 years ago

I think this looks good; I don't see any issues. We should update https://github.com/OBOFoundry/purl.obolibrary.org/blob/master/config/cdao.yml to point here.

balhoff commented 7 years ago

Actually I take it back, we're not quite ready to point the release here. The CDAO releases are housed in the OBO SVN here: http://svn.code.sf.net/p/obo/svn/ontologies/trunk/CDAO/

hlapp commented 7 years ago

The CDAO releases are housed in the OBO SVN here: http://svn.code.sf.net/p/obo/svn/ontologies/trunk/CDAO/

I was hoping we could use Github release tags for that. Can't we state the expansion of versioned releases differently from the unversioned ontology?

balhoff commented 7 years ago

Yes, we can use release tags. Here's an example: https://github.com/OBOFoundry/purl.obolibrary.org/blob/master/config/taxrank.yml

epontell commented 7 years ago

Looks ok to me.

Enrico

From: Hilmar Lapp notifications@github.com Reply-To: evoinfo/cdao reply@reply.github.com Date: Friday, May 5, 2017 at 11:11 AM To: evoinfo/cdao cdao@noreply.github.com Cc: Enrico Pontelli epontell@cs.nmsu.edu, Mention mention@noreply.github.com Subject: Re: [evoinfo/cdao] Review of migration from SourceForge (#1)

@balhoff as the CDAO maintainer currently on record, could you please take a look and indicate approval or provide comments on actual or potential issues?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

hlapp commented 7 years ago

The SourceForge repo actually has two version control repositories. The second (and older) one that isn't included in this migration is the CVS repository. Please see #3 for the results and discussion of that.

hlapp commented 7 years ago

See #4 for review of release tag porting.

hlapp commented 7 years ago

With the completion of #3 and #4 I think we can call this complete now, too. See #5 for the remaining task of updating the OBO metadata record.