-
Notifications
You must be signed in to change notification settings - Fork 675
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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
New release #1002
Comments
you might want to follow up here. AFAIK this project is in limbo. |
The issue mentioned in the description about looking for maintainers (#803) is closed and there were some commits recently, so I assumed the project was active again. If that's not the case, I'm not sure then why the issue was closed. |
The issue was closed by the orignal owner of the project iirc, and I don't really know the reason. But in this chat you'll see that we agreed on a new CONTRIBUTING guide, which explains the process to become a maintainer. It's rather simple and if any of you makes a significant contribution, I'll happily add it to the team. As for the releases, there were a lot of changes made to transition to a new version but despite looking stable it never got properly tested, hence the very long beta. If we get one or two active contributors, I'd gladly release new versions. |
Can we get a new release? The latest version was released more than 7 years ago 馃槗
It would be nice to have a version that works with modern Ruby and gems versions. Let me know how can I help move this forward.
The text was updated successfully, but these errors were encountered: