-
Notifications
You must be signed in to change notification settings - Fork 111
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
[Proposal] RSpec support policy #158
Comments
LGTM 🍖 |
I vote your your proposal, Latest version, Previous version and 2.14.x version. |
Keeping compatibility with many versions is difficult. People still using Rspec 2.14 can also keep using an older version of turnip which supports 2.14 imo. :) E.g. if it were up to me I'd drop support for 2.x and make a new major release. And then only support 3.x or even 3.2+ |
E.g.
|
Make it 2.x as dropping support for a version is considered breaking and hence justifies a major version bump in semver. Good time to maybe make some other breaking changes :) Thank you btw. for maintaining, I love turnip and over time feared it had gone unmaintained. Good to see that this is not the case 👍 |
While we're talking breaking changes, we'd love to get our rutabaga gem incorporated... It allows you to call features straight out of rspec (inverts the control). https://github.com/simplybusiness/rutabaga. Rutabaga is a lot closer to how CucumberJVM works, I think. |
Hi @lukaso
What's mean? "Rutabaga feature is provided as a built-in of Turnip" ? |
@lukaso I believe this should rather be discussed in a separate issue :) Aside from that I believe that extra gems for extra/changed functionality are a good thing :) |
Agreed as separate issue: #159
|
Thank you for comment 🍕 When RSpec 3.4.0 is released, I will release Turnip 2.0.0.
If want to use RSpec 2, please use |
👍 |
RSpec 3.4.0 was released 🎉 |
Motivation
Now,
jnicklas/turnip
supports multiple version of RSpec (See: .travis.yml):I think there are too many.
Proposed changes for support version
Ideally, latest version only.
But, I think everyone is not able to use the latest version.
And, many developers are using
2.14.x
yet (maybe..).Therefore, We propose the following policy:
Example:
In the future
When
RSpec 4
was released, will stop support forRSpec 2.14.x
.The text was updated successfully, but these errors were encountered: