Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

new stable release #124

Open
eventhorizonpl opened this issue Mar 18, 2015 · 12 comments
Open

new stable release #124

eventhorizonpl opened this issue Mar 18, 2015 · 12 comments

Comments

@eventhorizonpl
Copy link

Hi,

Is it possible to get new stable release in the near future?

Best regards,
Michal

@basdenooijer
Copy link

I would really like this too, to get rid of 'dev-master' in Composer

@exi
Copy link

exi commented Apr 1, 2015

We would like this too, dev-master dependencies are unusable for us.

@s7anley
Copy link

s7anley commented Apr 6, 2015

👍

@fatganz
Copy link

fatganz commented May 20, 2015

👍 We can't rely on dev-master and fallback to most recent old version which is 1.1.7 from Jun 4, 2013.
Would be nice to hear something from maintainers :) .

@ruudk
Copy link
Collaborator

ruudk commented May 20, 2015

I can understand that you don't like the dev-master dependencies but the problem is much more with php-resque than with this bundle.

php-resque isn't actively developed anymore and has 144 commits since the last release from 2012. The master branch from BCCResqueBundle has a dependency on the dev-master from php-resque.

I personally have given up on Resque and BccResqueBundle and am moving over to RabbitMQ. So my best advice would just be to stick to a commit by using dev-master#commit-hash as a version number.

@eventhorizonpl
Copy link
Author

@ruudk

Thanks for the information.

@wesnick

You should be aware of this.

@fatganz
Copy link

fatganz commented May 20, 2015

I do agree that RabbitMQ is robust and good solution but at same time it's not an option for many. For example for my current project it'll be overkill for service few hundreds jobs a day and Resque solves all it's needs without extra server and maintenance needs.

> php-resque isn't actively developed anymore
there's https://github.com/kamisama/php-resque-ex which is fork from original php-resque which opens possibility to renew work on this project.

And yes @ruudk, thanks for supporting it so long with others, we do really appreciate your contributions guys!

@ruudk
Copy link
Collaborator

ruudk commented May 20, 2015

I wasn't aware of https://github.com/kamisama/php-resque-ex. Maybe it would be better if some would fork this bundle too and move it over to php-resque-ex?

@danhunsaker
Copy link

-ex has been officially abandoned. It wouldn't actually help any to move
to it.

On Wed, May 20, 2015, 02:19 Ruud Kamphuis [email protected] wrote:

I wasn't aware of https://github.com/kamisama/php-resque-ex. Maybe it
would be better if some would fork this bundle too and move it over to
php-resque-ex?


Reply to this email directly or view it on GitHub
#124 (comment)
.

@ruudk
Copy link
Collaborator

ruudk commented May 20, 2015

@danhunsaker How can that be, last commit 5 days ago, and last release in january?

@danhunsaker
Copy link

Odd. Kamisama had said it was abandoned the last time we proposed
integrating the changes there upstream... Must have changed their mind.

On Wed, May 20, 2015, 02:40 Ruud Kamphuis [email protected] wrote:

@danhunsaker https://github.com/danhunsaker How can that be, last
commit 5 days ago, and last release in january?


Reply to this email directly or view it on GitHub
#124 (comment)
.

@mpclarkson
Copy link

As it is clear that this bundle is no longer being actively maintained, I have taken it upon myself to maintain a fork here https://github.com/mpclarkson/resque-bundle. I have updated the admin twig templates to Bootstrap3, fixed some autoload issues, added a few basic tests, integrated with Scrutiniser and Travis, and made some other tweaks. I am keen for contributors and suggestions. Repo stars would be appreciated too to help encourage contributions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants