-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Migrate legacy_features into features directory #408
Comments
This confused me as well. I didn't even know about aruba before I read about it here. |
I just realised, working on #358, that |
I'm commiting this into master, even though I know it will break the build, because we should have had this running all along. We should not release code from master without checking each of these failures.
On Monday, May 6, 2013, Matt Wynne wrote:
P.S. if it was me please blame Oleg ;-P Aslak
|
@aslakhellesoy it's hard to use git blame for this as what we need to analyse is historical travis output - when it stopped doing both feature runs. Or I guess we could just bisect the git history. I suspect it might have something to do with #400 but I did some quick testing and couldn't really see why it would have caused it. I don't understand enough about Rake's API, but it seemed that the first task ( |
Done! Big thanks to @jimvm. |
So, should it be closed? ;) |
\o/ great work @jimvm |
Glad I could help! Somewhat related, what about the |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
This is confusing for contributors. There's no reason we can't get started now, but I want this to be on the checklist for 2.0
For context, the 'legacy' directory contains features that were written before aruba. Many of them will only require a small amount of work to port them to aruba, some will need more work, some should probably just be deleted.
The text was updated successfully, but these errors were encountered: