Help testing against edge resque

[steveklabnik]

Hey there!

I'm gearing up to work on Resque 2.0, and I'd like to coordinate better with plugin authors to make sure stuff doesn't break.

I'd like to know a few things:

1. Can I do something to help get you testing against edge Resque?
2. Are you monkey-patching anything in Resque currently? Can 2.0 expose an API to help you not have to do that any more?
3. Do you need any help in bringing your plugin up-to-date with the latest Resque?

Thanks!

Related: https://github.com/defunkt/resque/issues/880

[jrgifford]

1. jrgifford/delayed_paperclip is now upstream.
2. Not sure, I'll be looking into this soon.
3. Don't think so. I'll check.
4. I'll have to try with latest first, then get back to you. :-)

James Gifford
2162238574
On Mar 19, 2013 7:11 PM, "Steve Klabnik" notifications@github.com wrote:

Hey there!

I'm gearing up to work on Resque 2.0, and I'd like to coordinate better
with plugin authors to make sure stuff doesn't break.

I'd like to know a few things:

1. Can I do something to help get you testing against edge Resque?
2. Are you monkey-patching anything in Resque currently? Can 2.0
   expose an API to help you not have to do that any more?
3. Do you need any help in bringing your plugin up-to-date with the
   latest Resque?

Thanks!

Related: defunkt/resque#880 https://github.com/defunkt/resque/issues/880

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/76
.

[steveklabnik]

Oh hello! I'll re-open this there, then.

[steveklabnik]

Also, I corrected to the new upstream in our wiki page.

[jrgifford]

Cool. 👍

James Gifford
2162238574
On Mar 19, 2013 7:37 PM, "Steve Klabnik" notifications@github.com wrote:

Also, I corrected to the new upstream in our wiki page.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/76#issuecomment-15150566
.