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.

Sign up for GitHub

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

Jump to bottom

Support Ruby 3 #175

Open
Tracked by #22
danielpclark opened this issue Apr 6, 2023 · 5 comments
Open
Tracked by #22

Support Ruby 3 #175

danielpclark opened this issue Apr 6, 2023 · 5 comments
Assignees
@danielpclark
Labels
enhancement General or specific improvement feature Something new tracking Tracking other issues by category

Comments

@danielpclark
Copy link
Owner

I'm currently implementing GitHub Actions CI testing for the suite of OSes for Ruby 2. Ruby 2 will be maintained on version 0.8 of Rutie. Once CI testing implementation is complete enough I will split off a branch Stable-Ruby-2 and then master branch will become the target for Ruby 3. Once that is stable I plan on making a branch Stable-Ruby-3 that should merely be a mirror of master until I better decide the best policy for the difference between the two branches.

Tracking:
@danielpclark danielpclark added enhancement General or specific improvement tracking Tracking other issues by category feature Something new labels Apr 6, 2023
@danielpclark danielpclark self-assigned this Apr 6, 2023
@Zapotek
Copy link

Zapotek commented Apr 21, 2023

That would be great Daniel!

@Zapotek Zapotek mentioned this issue Apr 21, 2023
Closed
2 tasks
@coopergillan
Copy link

@danielpclark - any word on Ruby 3 support? We are also encountering seg faults when testing with Ruby 3.

@tsmartt
Copy link

tsmartt commented Oct 17, 2023

Same

@danielpclark
Copy link
Owner Author

My situation has suddenly provided me with more free time. I anticipate getting to this sooner rather than later.

@leeourand leeourand mentioned this issue Dec 5, 2023
Open
@Zapotek
Copy link

Zapotek commented Dec 28, 2023

@danielpclark is there any update on this? Up to date gems require Ruby >= 3 now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@danielpclark danielpclark

Labels
enhancement General or specific improvement feature Something new tracking Tracking other issues by category
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@danielpclark @Zapotek @coopergillan @tsmartt