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.
Le 19/04/13 20:30, Daniel Russel a écrit : > More importantly, a decision needs to be made for each module not in > the main IMP repository (eg isd2, multifit2) whether they will be > maintained against develop or master. That will then tie the people > using the module to one or the other. > > > On Apr 19, 2013, at 10:22 AM, Barak Raveh <barak.raveh@gmail.com > mailto:barak.raveh@gmail.com> wrote: > >> Dear all (Max, Riccardo, Natalia - this might be particularly >> important for you) >> >> As we approach the next release, it is *critical* that each person in >> the group will make a clear personal decision whether they want to >> work in the "develop" branch or the "master" branch (= release >> version) of IMP. Note that this has nothing to do with whether you >> are considered an IMP developer or not, it is just a technical >> personal decision. >> >> The *develop* branch is where we work on developing the next release. >> In 6 months, this will be the next IMP. It is less stable (but should >> be much much more stable than it used to as the testing system >> improves more and more). It contains the newest IMP features and >> updates. Also, you enjoy the daily testing system, so you can be >> assured your code will be compatible with the next IMP release. >> >> The *master* branch is the release version - it means you will be >> frozen with a relatively stable version of IMP, with minor bug >> updates from time to time, but will not get new features. All your >> code changes will be kept for you, and will not be easily shared with >> all other developers. Also, you will not enjoy the daily testing >> system (so you won't know if your code is stable for the next release). >> >> Feel free to ask questions or give feedback, this decision is totally >> up to you. You can switch in the middle, but it might be a bit of a >> mess as the two branches will diverge over time. >> >> >> _______________________________________________ >> IMP-dev mailing list >> IMP-dev@salilab.org mailto:IMP-dev@salilab.org >> https://salilab.org/mailman/listinfo/imp-dev > > > > _______________________________________________ > IMP-dev mailing list > IMP-dev@salilab.org > https://salilab.org/mailman/listinfo/imp-dev