more work but the professional way to go :)
On Fri, Apr 19, 2013 at 2:13 PM, Ben Webb ben@salilab.org wrote:
> On 4/19/13 2:09 PM, Yannick Spill wrote: > >> As far as ISD goes, I think that IMP/isd will go to the next release, >> while IMP/isd2 should go to the following one, e.g. stay in private >> development. Riccardo, Max, complain if you don't agree. >> > > I think what Daniel means is are you planning to make isd2 work with the > latest (nightly, develop) IMP, or only update it occasionally to work with > master? If the latter, then we wouldn't be able to include it in the > nightly builds (which build with IMP develop). > > Of course, there's no reason isd2 couldn't have a develop *and* a master > branch, where the develop branch is expected to work with latest IMP and > the master branch with the IMP release. But that's more work for you guys. > ;) > > Ben > -- > ben@salilab.org http://salilab.org/~ben/ > "It is a capital mistake to theorize before one has data." > - Sir Arthur Conan Doyle > > ______________________________**_________________ > IMP-dev mailing list > IMP-dev@salilab.org > https://salilab.org/mailman/**listinfo/imp-devhttps://salilab.org/mailman/listinfo/imp-dev >