[Backgroundrb-devel] Restarting BackgrounDRb Means Restarting Mongrel?
tsanders at hiddenjester.com
Sun Jul 6 12:50:40 EDT 2008
Any update on this new tagged version? I need a new stable version
before I'll be allowed to deploy an update, and at the moment we've
got a whole set of things that are waiting for a stable version of
backgroundrb to deploy.
I understand that it's difficult to have a firm timeline, but it's
also been a couple of weeks since the last thing we've heard on
tagging a new version.
On Jun 18, 2008, at 1:31 PM, hemant wrote:
> On Thu, Jun 19, 2008 at 1:39 AM, Ian Lesperance
> <ian.lesperance at gmail.com> wrote:
>> I am hesitant to jump onto the edge, since this is being used in a
>> production application. Also, since I believe I've managed to
>> eliminate our
>> reason for needing to restart BackgrounDRb, it's more of an
>> inconvenience at
>> this point.
>> Do you have plans to tag a release anytime soon, be it through
>> Subversion or
> I am not committing a time line, but I intend to release new version
> this weekend if everything I planned goes well. Also, I hear from
> folks( and in my own experience), git version is a _lot_ more stable.
> If you don't want to change in production at least try in production.
> Backgroundrb-devel mailing list
> Backgroundrb-devel at rubyforge.org
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 4619 bytes
Desc: not available
More information about the Backgroundrb-devel