CDAT / cdat

Community Data Analysis Tools
Other
175 stars 68 forks source link

Remove/update deprecated files #788

Closed durack1 closed 8 years ago

durack1 commented 10 years ago

I've just pulled down the 2.0.0 source and noted the files TODO.txt and Changes.txt which don't appear to be relevant to the latest master repo - should these be removed/updated?

durack1 commented 10 years ago

Same goes for the tests directory, it appears to contain cdat tests which are replicated in the testing subdir?

durack1 commented 10 years ago

Is the libcdms directory also obsolete - has this source migrated into the Packages subdir?

aashish24 commented 10 years ago
durack1 commented 10 years ago

The docs directory also contains a bunch of stuff that looks about 5+ years old.. The release notes nicely document some changes with cdat 4.3..!

durack1 commented 10 years ago

I noted that a "release notes" link appeared (and has now disappeared) against the 2.0.0 tag under the releases page - is there a way to get github to autogenerate this from commits?

durack1 commented 10 years ago

@doutriaux1 @aashish24 can you mark this as a 2.2 milestone please?

durack1 commented 9 years ago

As noted in https://github.com/PCMDI/pcmdi_metrics/issues/161 here is a more specific listing of files/dirs to cleanup:

durack1 commented 9 years ago

@doutriaux1 you should probably push this to a 2.3 milestone..

durack1 commented 9 years ago

This issue is related to #1353 - @doutriaux1 will need to complete the merging of images and resources subdirs and their install locations..

durack1 commented 9 years ago

@doutriaux1 @aashish24 it seems my PR #1341 was closed, so this should no longer be a 2.4.0 milestone - I've amended this to 3.0 it would be nice to get this cleanup underway..

doutriaux1 commented 9 years ago

@durack1 I will produce a fresh new PR when I do this.

durack1 commented 8 years ago

@doutriaux1 2.6 would be a good time to get this cleanup complete..

doutriaux1 commented 8 years ago

I think this is irrelevent with conda

durack1 commented 8 years ago

@doutriaux1 I don't.. if it's dead, then kill it and clean things up so that redundant and many year old rubbish isn't polluting a clean repo..

doutriaux1 commented 8 years ago

@durack1 it's kind of my point when I switch to the conda build, all this is going to didsappear from the repo

durack1 commented 8 years ago

@doutriaux1 that is the conda variants.. But not the source, by which some folks will still persistently try to build from..

aashish24 commented 8 years ago

I agree with @durack1. Build system and this issue is orthogonal things. In my rst_docs branch I took care of the docs folder but we still lot of files un-used and not maintained. I strongly suggest we remove them or update them.

durack1 commented 8 years ago

@doutriaux1 @aashish24 FYI there is a closed PR that I submitted many moons ago (a year ago) https://github.com/UV-CDAT/uvcdat/pull/1341 - it was closed without merging

doutriaux1 commented 8 years ago

@aashish24 when updating fully to conda that will imply doing the cleaning. No worries. Should be done before 2.6, which is when we officially switch to conda for releasing.

aashish24 commented 8 years ago

@doutriaux1 I think we are mixing issues here. Conda or not conda should be a different issue. We should not solve every problem with one bullet :smile:. These two issues are orthogonal and it would be better if we have two separate PR's for them.

doutriaux1 commented 8 years ago

not really, lots of these files are not necessary really but are used by the insane install.py.in that will go away with conda build.

durack1 commented 8 years ago

@doutriaux1 @aashish24 I see overlap with these standing issues:

788 - this issue

1353 - Merge contents of images and resources subdirs (this is closed, but shouldn't really be)

1354 - Update license/legal info

durack1 commented 8 years ago

@doutriaux1 you have sorted this by migrating to conda, closing