Are you on a fork of Resque? I'd like to get you back on releases

[steveklabnik]

Hey there! So Resque hasn't gotten any updates in a long time, but I've been doing some work, trying to get ready for 1.26.0.

One thing that I would like to do is get people who are on forks back to master. Said forks are my fault for stepping away from Resque 😭

If you're one of those people, would you mind leaving a comment with

1. what stuff you've fixed in forks
2. if you're interested in moving those patches upstream
3. any other bugs that you consider high-priority.

Thanks!

[steveklabnik]

@rbroemeling sent in PR #1371

[steveklabnik]

Fixing #1074 is important.

[steveklabnik]

@dylanahsmith mentioned that Shopify is interested, and that @fw42 might be helping figure it out.

[steveklabnik]

#552 is at least one thing @github would need to get back on mainline, but it's a biggie. I'd still like to make it happen, though it might take till a 1.27.0 /cc @technoweenie

[fw42]

Just out of curiosity: Why are you going back to 1.x instead of continuing work on 2.x? What's wrong with 2.x?

[arthurnn]

i mentioned to @technoweenie that I am interested in helping with resque

[steveklabnik]

@fw42 I blogged about it http://words.steveklabnik.com/rescuing-resque-again

TL;DR: contributions have basically dropped off, I don't want to abandon users with back-incompat changes, and generally think that incremental improvement is better than trying to do a re-write these days.

@arthurnn that would be fantastic! Maybe a good first step is figuring out what @github needs here?

[steveklabnik]

Okay! I think that this is about all the response we're gonna get on this issue. I am still quite interested in this overall, and we've integrated a lot of Shopify's changes. 👍

Thanks everyone! And to future googlers, I am still interested in making this happen if you're on a fork. 😄