IMP Manual
for IMP version 2.14.0
|
In order to be shared with others as part of the IMP distribution, code needs to be of higher quality and more thoroughly vetted than typical research code. All code contributed to IMP
ctest
gcc
, clang++
and Visual C++
) without warningsctest
Once your code is ready to go, open a pull request to get the changes from your fork back into the main repository.
develop
branch. No development is done directly in the master
branch - it is updated for each release by merging from the develop
branch, as per the gitflow branching model. If your change is a bug fix that should also patch the last release, once your code is in develop
open an issue on GitHub assigned to benmwebb
and connected to the milestone for the next point release (e.g. a milestone with a name like IMP 2.0.1 point release
).