Hello all,
I've been unable to work on God lately, and I understand that some of
you have some frustrations, so I'd like to more clearly specify how
issues and patches should be submitted.
It will be much easier for me (and the community as a whole) to track
issues if they are placed in the official God issue tracker at
http://github.com/mojombo/god/issues. So from now on, please catalog
any problems you have over there.
If you have a patch that you'd like applied to mainline, please also
create an issue on GitHub with a pointer to your repo and the branch
that the change is on. Having patches tracked there will make sure
they don't fall through the cracks, and that discussion can more
easily be made around them. It also allows everyone to see what
patches are pending.
As far as the memory leak goes, I spent a day a few weeks ago trying
to further track it down, and committed some changes that looked
promising, but it still starts leaking after an hour or so. The
strange thing is that on Engine Yard's Gentoo installation of Ruby,
God shows no leaks at all, which leads me to believe that there is
some compile option that prevents the leak or they've applied some non-
standard patches that mitigate the leaky behavior. Since I'll be
needing to use God on Debian very soon, I'm very keen to solve the
leaking problem once and for all. If you have any insight into the
leaks, please do respond on this thread and let me know what you've
discovered.
Thanks to everyone that has provided help on this mailing list and has
contributed in a positive way! I hope to be able to spend more time on
God and address some of the problems that have been reported.
Cheers,
Tom