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 drussel@gmail.com 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 drussel@gmail.com wrote: > >> https://github.com/salilab/imp/issues/256 > > > _______________________________________________ > IMP-dev mailing list > IMP-dev@salilab.org > https://salilab.org/mailman/listinfo/imp-dev