Repository redesign about dagmc

[zwelchWI]

I have an MCNP repo made at $CNERG_ROOT/git which has branches for each version and as best I can tell accurately preserves the development history from the svn repo. I'm not sure if the dagmc folder needs to stay in here or be moved to the github DAGMC repo, but it should be relatively easy to remove if necessary.

Should the DAG-MCNP tests be in separate, version-specific folders in master or would you rather each have its own branch like the MCNP repo?

[gonuke]

Thanks - looks pretty good. Does it have the vendor version of the code in it? Is that just the root version of each branch? Maybe we can tag that in each branch?

Regarding where to but tests: We'll want a single common set of input files and (potentially) version specific output files. Do have any thoughts on how to configure that?

[gonuke]

I tagged the vendor commits. I think this is ready to go - we'll keep the SVN around for a while though. Please communicate to users via the CNERG list and make the SVN repo unwriteable so that we don't get some strange divergence.

[gonuke]

@zwelchWI Can you add an email hook to the CAE-hosted MCNP repo? It should go to the same folks as the SVN hooks went to.

[zwelchWI]

Sorry, things got screwed up changing the name from DAG-MCNP to MCNP and I forgot to edit the email list. Should be fixed now

[gonuke]

@zwelchWI I thought we had already put the DAGMC tests in the new repo? Can you remind me the status on this?

[zwelchWI]

I did most of the converting at the time but it looks like I never finished putting everything together and pushing to github. Everything should be updated now