[rabbitmq-discuss] rabbit disk_mode branch eating up all RAM, including swap, dying

tsuraan tsuraan at gmail.com
Tue Oct 6 16:31:06 BST 2009

> No, that's not really accurate. It's difficult to say whether a branch
> is "stable" or not. Our basic method is to develop on a branch, then the
> branch will go through QA which may well result in further changes to
> that branch - that may very well create a cluster of small commits over
> the code base as bugs are tracked down or refactorings occur. But at
> this point, the code is getting more stable and improving in quality.
> 21368 is the basic new persister - v2. This is being grown on a
> different branch into an altered design (v3) which does not use mnesia
> for reasons I've outlined before. 21444 is a set of manual controls that
> extend 21368. Thus from time to time I merge 21368 into 21444. All long
> standing branches get default merged into them from time to time so that
> recent fixes which have been merged into default get propogated out to
> branches. This also helps to ensure infrastructure remains working
> across all branches, and it makes the eventual merge back into default
> easier too.

Ok, thanks for the info.  Would it be possible to have a page where
the most active bug numbers are explained, or a blog entry or two on
lshift that explains them?  You guys are really responsive on this
list, but sometimes it would be cool to be able to find information
without just asking you :)

More information about the rabbitmq-discuss mailing list