Re: [IMP-dev] So maybe let have the first IMP mini-release by next week?

[Daniel Russel <>]

Or to put it another way, I think the main improvement to aim for over the current system is that we have a stable branch where bugs can be and will be patched, but significant changes will not occur (as opposed to trying to create a particular stage that has significantly fewer bugs than normal, because we haven't had much luck with trying that as everyone always has too many other things to do). 

> For extra testing, I suggest that over the next week, people try to run their code against a current IMP and make sure it all works. I think for this process to work going forwards it has to be fairly light weight and not involve significant amounts of extra testing.
> 
> Does that make sense?
> 
> On Apr 10, 2013, at 6:46 PM, Barak.raveh <> wrote:
> 
>> How about two stages?
>> I. By April 20th - Anyone who wants to update and check in their code to the release, document further, etc - do so by end of next week. 
>> II. By April 30th - branching out of Apr 20th code, extensive testing, minor updates and mini release
>> 
>> On Apr 10, 2013, at 6:27 PM, Daniel Russel <> wrote:
>> 
>>> Given comments so far, it seems to me like a good idea to try. And now seems as good a time as any. So shall we have our first mini-release by next week? In practice, that would mean that we branch in git. I would then encourage people who only update IMP occasionally to update to that branch. Patches would be moved to the release branch on a more or less as-needed basis, or if it is something that is a simple bug to fix.
>>> 
>>> Sounds worth a try?
>>> 
>>> See <https://github.com/salilab/imp/issues/256> for more context.
>>> 
>>> 
>>> On Apr 10, 2013, at 7:15 AM, Daniel Russel <> wrote:
>>> 
>>>> <https://github.com/salilab/imp/issues/256>
>>> 
>>> 
>>> _______________________________________________
>>> IMP-dev mailing list
>>> 
>>> https://salilab.org/mailman/listinfo/imp-dev
>> 
>> _______________________________________________
>> IMP-dev mailing list
>> 
>> https://salilab.org/mailman/listinfo/imp-dev
>