-
Notifications
You must be signed in to change notification settings - Fork 27
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
Release 0.1.3 gem #28
Comments
Sounds good. I'll try to get it out this week. |
I have two commits in my fork that I'd like to include, but I want to make sure they don't break things for you. I updated to let the r20 tools include libraries correctly. @nuclearsandwich , could you try out master from https://github.com/abscondment/pindah and let me know if there's any issue? If not, I'll merge those in for 0.13.0 |
Hah, I had an incoming PR with a similar but.lesser change.. I have another that tweaks the templates a bit. I'll push as soon as school wifi allows. |
Just submitted PR #29 which makes minor template changes. Running
However, I'm able to remove the manually specified |
Hmm, yeah. AFAICT, this is happening when On Thu, Oct 11, 2012 at 1:09 PM, Steven! Ragnarök
|
I think the problem might be the Otoh, I could try making mirah attempt to build itself on gem install when it's installed from git. |
I vote for using a release. A lot less duplication of effort thay way. |
I agree. I pinned it on 0.0.12, but I now see super weird rake issues:
I get this even if I comment out all of the tests. Not sure what that means. |
Ok, I'm looking at this again. Only 4 months late :) I'm currently waiting to hear back on #33 and #37, but I'm confident that these issues are all related to combining certain versions of Mirah and JRuby. Once I nail those down, I plan to update the README with known good versions and release 0.13. Yay. |
Alright, guys 'n gals, now that I've agreed to help Phil and Brendan with the managerial duties, I'd like to close out some of these stale issues and cut this 0.1.3 release we have been talking about for more than a year now. In an effort to provide some clarity and direction, I've taken some time to clean up the issue tracker by adding several new tags and milestones, and I've tagged all but one open issue with the appropriate metadata to help us prioritize the work. In the spirit of reviving this project and just getting stuff done, I propose we get this next release out the door as leanly and quickly as possible. If necessary, we can always add an incremental 0.1.4 release to the roadmap before shooting for the stars with the 1.0.0 release. What say y'all? :-) |
That sounds great.
|
I had issues with the currently released gem but master works.
What say we cut a release?
The text was updated successfully, but these errors were encountered: