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
Major version bump #50
Comments
To provide another data point: |
My thoughts at the moment are:
|
Sounds like we're in total agreement. |
I believe this can be closed now that 4.0.0 has been released right? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The
delayed_job
project, from which this codebase is derived, dates back to 2009. This particular gem was released in 2011 and has thousands of users running it in production.Quoting from the Semantic Versioning FAQ:
By this definition, this library should already be 1.0.0.
I have experimented with releasing 4.0.0.beta versions of this gem, to bring the versioning in line with
delayed_job
andrails
both of which are in 4.0.0.beta. That said, I'm not set on making the big jump to 4.0.0, especially if we're planning to maintain compatibility with earlier versions ofdelayed_job
andrails
, as we seem to have been able to achieve with #49.Is there any compelling reason to ship another patch (0.4.5) or minor (0.5.0) version before making the jump to 1.0.0 or 4.0.0?
My only hesitation is to wait until
delayed_job
andrails
release 4.0.0 versions, to ensure we are compatible with the final releases, not just the betas.The text was updated successfully, but these errors were encountered: